jlfranklin18

Wanted to update what I ended up with and say thanks for the help. First off I am really not sure how but I forgot that I had upgraded to the 5.0 line to support the 3TB drives a while back and I guess this is what I get for not being better at documenting my setup. I looked at the readme on the flash drive and it had 4.4.2 in it so I said that was the version I was running. That being said when I upgraded I only copied the files necessary leaving the readme untouched I was actually running 5.0-rc5 (not that never upgrading from an RC was a good idea either). I am still not clear if the bad disk was the reason for the hangup at the login but with the upgrade I am able to see everything and move forward. With this information and a bit more trust in the parity drive I, I am going to be attempting a rebuild as soon as my new drive arrives and as a bonus I am now on the latest version. Thanks again for the help

I was able to start the array with all disks as data disks and one showed as unmountable. I then did a new config and made that one the parity drive and now a different dis showed as unmountable. I am attaching the diagnostics download to see if that might provide some assistance. The first time the unmountable drive was serial number ST3000DM001-9YN166_Z1F11JBB - 3 TB (sdh) so I believe this is the parity drive. What are my options now though that it also appears that I have a corrupt drive in the array? tower-diagnostics-20151215-2012.zip

My Motherboard doesn't seem to like it I was able to format to FAT-16 from my Mac [i updated the original post with the instructions]. WIll post back with more info once I try the below suggestions to assign everything as a data drive to find the "unformatted" parity drive fortunately I didn't have a cache drive configured.

This info was great and pointed me in the right direction wanted to provide an update for any other Mac users that ran in to the same issue. There is a way to format the flashdrive to FAT-16 after letting the Mac erase the drive and create the single partition with the name you need. After using the Disk Util to erase the drive you can run the following commands to find the partition and then reformat it to FAT-16 from a terminal diskutil list =========== example output============================ /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *1.0 GB disk1 1: DOS_FAT_32 UNRAID 1.0 GB disk1s1 ================================================ once you identify the partition you can then run sudo newfs_msdos -F 16 -v UNRAID /dev/disk1s1 =========== example output============================ newfs_msdos: warning: /dev/disk1s1 is not a character device 512 bytes per physical sector /dev/disk1s1: 1957344 sectors in 61167 FAT16 clusters (16384 bytes/cluster) bps=512 spc=32 res=1 nft=2 rde=512 mid=0xf8 spf=239 spt=32 hds=128 hid=2 drv=0x80 bsec=1957886 ================================================ you can ignore the warning about not being a character device and even when you run diskutil list it will show as DOS_FAT_32 its actually FAT 16 and was able to get past the missing file.

I am pretty sure I ran the steps to create on a Mac correctly - it ran the shell script and it then copied the ldlinux.c32 from the syslinux folder to the root of the drive and created the ldlinux.sys also at the root. after searching some more I think this is my issue - https://lime-technology.com/forum/index.php?topic=38160.0 Guess it's now time to install virtualbox and get a windows image up and running to format the flash drive before installing

I am following the steps for upgrade with a clean install and now when it boots I get the following error message: Syslinux 6.0.3 CHS 2014-10-06 Copyright ..... "Failed to Load ldlinux.c32" Boot failed: please change disks and press a key to continue.

The upgrade instructions say I need to do a clean install, is there a way to see the config for the drives from the backup of the flash ? Will the new version identify the parity drive and rebuild the array without me identifying each drive? Thanks

Unraid Version 4.4.2 I am currently experiencing an issue where I can't get past the login prompt. The bzroot and bzimage seems to load fine, I can't catch all the output as it boots but it appears to see all 6 SATA drives load up but then when it gets to the login prompt it hangs. The keyboard num-lock light turns off and the cursor just blinks but I can't enter anything with the keyboard. The server appears to get as far as loading the network as I can ping the IP from another host but when I try to telnet it connects but it never gets to a shell and seems to just hang similar to the login: prompt directly on the server. I ran a memtest and also ran the flash through my MAC DiskUtility verify disk and no errors were reported.