JordanWr

I was finally able to get this figured out. You need to have the enable array autostart enabled in Settings>Disk Settings>Enable Auto Start = Yes. You must reboot unraid after changing this setting before it will take effect. If you don't have it enabled it doesn't look for the keyfile in /root/keyfile and just hangs on starting array. Also just for anyone else looking at this later the emcmd cmdStart=Start command only works on version 6.10 or later based on someone else's comment.

I have dual parity drives in my unraid system. I am getting a udma crc error every time the system is powered on. The error count only increases by 1 on each partiy drive and only when first powered on. I have tried replacing the sata cables with new, and all tests pass. The error count never increases if the system is left powered on. Any suggestions on what to do or why I would only be getting these errors when powered on. I don't want to disable notifications on it and miss it later if something is actually wrong.

I am trying to start an encrypted array from command line. I use a passphrase for decryption and using the GUI can enter it and start the array. I am currently tring to start the array via CLI using emcmd cmdStart=Start The only place I saw to place the passphrase was in /root/keyfile. I am doing so before trying to start the array using echo -n "passphrase here" > /root/keyfile This does not seem to work. What am I doing wrong? Is there a different place I need to put the keyfile or a different format?

I have been using Unraid for about a month. About once a week I lose WebUI and SSH. Restarting the machine does fix the issue for another week. When I plug a monitor in I get a monitor_nchan segmentation fault. When attempting to type 'diagnostics' it just says 'Bus error'. I checked /boot and do not see any log files saved to the flash drive. Any ideas on where to go from here to get more specific information?