gillman99

That was it. I only have 2G in the machine and not sure how much is being used. When I reduced the allocated amount to 512M it created the vm. Now that won't be enough so I'll have to expand. Can I expand the memory after the vm is created after I add another dimm?

I'm trying to create a HomeAssistant vm and it is giving me the error in the attached graphic. Any ideas on what the problem could be?

I have a drive that's being diagnosed as Faulty, but it still appears to work. I get the thumbs up in the Dashboard so not sure how to tell if this is a real issue or not. I've attached 2 screenshots of my GUI in addition to the SMART report. Any help is appreciated with letting me know if I should replace this drive. ST31000340AS_9QJ1X55Y-20151206-1042.txt

I had 9 drives in my array (1 parity, 8 data) and everything's working fine. I added a new 1 TB drive at the end of the array and did a pre_clear (this was my first time doing a pre_clear). Everything seemed to be successful but when I started the array with the new drive it said it was unmountable and asked me to check the format button to format the new drive which I did. That worked as well, but now I notice the new drive is xfs filesystem and not reiserfs. Is this a problem? If so, how do I resolve? A picture of my array is included for reference.

BRit, Can you tell me how to check for these parameters? Thanks, Mark

Thanks Johnnie Black. Hopefully they fix this soon.

I'm getting about 32MB/Sec.

Attached is the syslog syslog.txt

Here's the syslog so far. Currently 2.3% of the way through parity check. Jul 1 10:01:55 ss emhttp: shcmd (42): mkdir /mnt/user Jul 1 10:01:55 ss emhttp: shcmd (43): /usr/local/sbin/shfs /mnt/user -disks 510 -o noatime,big_writes,allow_other -o remember=0 |& logger Jul 1 10:01:55 ss emhttp: shcmd (44): rm -f /boot/config/plugins/dynamix/mover.cron Jul 1 10:01:55 ss emhttp: shcmd (45): /usr/local/sbin/update_cron &> /dev/null Jul 1 10:01:55 ss emhttp: shcmd (46): :>/etc/samba/smb-shares.conf Jul 1 10:01:55 ss emhttp: Restart SMB... Jul 1 10:01:55 ss emhttp: shcmd (47): killall -HUP smbd Jul 1 10:01:55 ss emhttp: shcmd (48): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Jul 1 10:01:55 ss emhttp: shcmd (49): pidof rpc.mountd &> /dev/null Jul 1 10:01:55 ss emhttp: shcmd (50): /etc/rc.d/rc.atalk status Jul 1 10:01:55 ss emhttp: Start AVAHI... Jul 1 10:01:55 ss emhttp: shcmd (51): /etc/rc.d/rc.avahidaemon start |& logger Jul 1 10:01:55 ss logger: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jul 1 10:01:55 ss avahi-daemon[1596]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jul 1 10:01:55 ss avahi-daemon[1596]: Successfully dropped root privileges. Jul 1 10:01:55 ss avahi-daemon[1596]: avahi-daemon 0.6.31 starting up. Jul 1 10:01:55 ss avahi-daemon[1596]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Jul 1 10:01:55 ss avahi-daemon[1596]: Successfully called chroot(). Jul 1 10:01:55 ss avahi-daemon[1596]: Successfully dropped remaining capabilities. Jul 1 10:01:55 ss avahi-daemon[1596]: Loading service file /services/sftp-ssh.service. Jul 1 10:01:55 ss avahi-daemon[1596]: Loading service file /services/smb.service. Jul 1 10:01:55 ss avahi-daemon[1596]: Loading service file /services/ssh.service. Jul 1 10:01:55 ss avahi-daemon[1596]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.130. Jul 1 10:01:55 ss avahi-daemon[1596]: New relevant interface eth0.IPv4 for mDNS. Jul 1 10:01:55 ss avahi-daemon[1596]: Network interface enumeration completed. Jul 1 10:01:55 ss avahi-daemon[1596]: Registering new address record for 192.168.0.130 on eth0.IPv4. Jul 1 10:01:55 ss avahi-daemon[1596]: Registering HINFO record with values 'X86_64'/'LINUX'. Jul 1 10:01:55 ss emhttp: shcmd (52): /etc/rc.d/rc.avahidnsconfd start |& logger Jul 1 10:01:55 ss logger: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jul 1 10:01:55 ss avahi-dnsconfd[1605]: Successfully connected to Avahi daemon. Jul 1 10:01:55 ss emhttp: Starting Docker... Jul 1 10:01:55 ss logger: /usr/bin/docker not enabled Jul 1 10:01:56 ss avahi-daemon[1596]: Server startup complete. Host name is ss.local. Local service cookie is 4200031360. Jul 1 10:01:57 ss avahi-daemon[1596]: Service "ss" (/services/ssh.service) successfully established. Jul 1 10:01:57 ss avahi-daemon[1596]: Service "ss" (/services/smb.service) successfully established. Jul 1 10:01:57 ss avahi-daemon[1596]: Service "ss" (/services/sftp-ssh.service) successfully established. Jul 1 10:03:21 ss kernel: mdcmd (47): check NOCORRECT Jul 1 10:03:21 ss kernel: md: recovery thread woken up ... Jul 1 10:03:21 ss kernel: md: recovery thread checking parity... Jul 1 10:03:21 ss kernel: md: using 1536k window, over a total of 1953514552 blocks.

I moved card to the upper slot and it now says 16 hours. So, here's where I'm at: Old Card: 8 Hours New Card in bottom slot: 24 hours New card in upper slot: 16 hours A little annoying, but I guess I could manage if this is as good as it can get. Any pointers on what else to configure to improve or look into would be appreciated.

I'm using ECS A885GM-A2 MB. I have no other cards in the MB, and have it inserted in the slot #21 as denoted in the manual. There are 2 PCIe Gen2 slots, but it doesn't say if it's slot 1 or 2.

I had an old x4 SATA controller card that was working great, but needed to expand. I replaced that card with the aoc-sas2lp-mv8 with everything else being exactly the same and now a parity check takes 24 hours vs 8 hours previously. Please note, I'm only checking, not correcting. I'm using v6 of unRaid, have 9 total drives (5 on MB, 4 on SuperMicro card), using forward cable to connect. Any ideas where to look to see what's causing the performance issue?

v4 was a purchaed version. Tom from Lime-Tech emailed me and answered my question.

I just purchased v6 and was able to boot my server. It's now asking me to include the link to the license file. How long does it take for Lime Tech to send me my license key after I purchased it?

I need to upgrade to v5 from v4.6 to support a new SATA card I purchased. I copied over the bzroot, bzimage, syslinux dir and moved the syslinux.cfg file to root. There wasn't very clear directions on this, so I just took a stab in the dark. I'm now getting this error message: SYSLINUX 3.63 2008-04-10 EBIOS Copyright © 1994-2008 H. Peter Anvind and then it just hangs. Any ideas? Does it cost money to upgrade to v5? Should I just go straight to v6?