August 19, 201015 yr Well I followed the directions to a T upgrading from 4.3.3 to 4.5.6 but I'm having issues. I can't even network to the unRAID server and when I type ifconfig on the server I get nothing... Where the heck do I begin troubleshooting?!?
August 19, 201015 yr Author I also can't seem to copy the system log from the unRAID server prompt... I just did an error check on the USB flash and it all seems fine...
August 19, 201015 yr Author I did a reboot and noticed an error that said something like 'usb high speed device reset something'
August 19, 201015 yr Start with a memory test. If it does not successfully pass nothing else can be trusted. You might also put the flash drive in a window's PC and run scandisk on it. You might not have safely ejected it. then, if your motherboard has more than one LAN chipset, and one was not originally supported, you might find the other one is now supported, and is the one unRAID selected for its use. Joe L.
August 19, 201015 yr Author Start with a memory test. If it does not successfully pass nothing else can be trusted. You might also put the flash drive in a window's PC and run scandisk on it. You might not have safely ejected it. then, if your motherboard has more than one LAN chipset, and one was not originally supported, you might find the other one is now supported, and is the one unRAID selected for its use. Joe L. Thank you for stopping in Joe! I am currently running the Memory Test now. I ran scandisk on the USB drive and had no errors found. I am using an ABIT Ab9 MOBO and it does have 2 ethernet ports, but I did try both of them... I will run Memory test and report back when that finishes. Thank you!
August 19, 201015 yr Author Should memtest be taking 3+ hours? It looks like it's about 40% complete with no errors after ~ 3 hours.... I had no idea it was long of a process!!
August 19, 201015 yr Author Well it passed memorytest... here are few photos I snapped of the errors I'm seeing when I boot the server: By null at 2010-08-19 By null at 2010-08-19
August 19, 201015 yr /dev/disk/by-label/UNRAID does not exist ... looks to be the problem. Some sort of issue with your USB drive. Doublecheck the label on it that it is exactly UNRAID (all uppercase) Is this the same USB you used with 4.3.3 ??
August 19, 201015 yr Author I don't get why the system log won't save onto the Flash Drive. I do the exact command 'cp /var/log/syslog /boot/syslog.txt and do the chmod a-x command. When I cd to /boot at the prompt I do see the syslog.txt, but when I plug the Flash into my PC I can't see it. I have 'show hidden files' selected... Anyone?
August 19, 201015 yr Author /dev/disk/by-label/UNRAID does not exist ... looks to be the problem. Some sort of issue with your USB drive. Doublecheck the label on it that it is exactly UNRAID (all uppercase) Is this the same USB you used with 4.3.3 ?? Yes, this is the same USB I used with 4.3.3. It without a question is named UNRAID Edit: THANK YOU for you suggestions.
August 19, 201015 yr I don't get why the system log won't save onto the Flash Drive. I do the exact command 'cp /var/log/syslog /boot/syslog.txt and do the chmod a-x command. When I cd to /boot at the prompt I do see the syslog.txt, but when I plug the Flash into my PC I can't see it. I have 'show hidden files' selected... Anyone? Just some guesses now. Sounds like it is in "READ ONLY" and from what I've read about when similiar issues with Data drives become READ ONLY that there might be file structure corruption? Beyond my knowledge at this point since I'm such an unRAID noob
August 19, 201015 yr Author Right... I have no idea and I'm waiting for help on how to proceed next.... At least I know my data is good and I took a screenshot of the Devices page....
August 19, 201015 yr Right... I have no idea and I'm waiting for help on how to proceed next.... At least I know my data is good and I took a screenshot of the Devices page.... You may have some corruption on the file-system of the flash drive, you can check it in your PC with scandisk of similar. (or right-click on the "drive" in my computer, and then click on the disk-repair in "properties->tools") We've seen flash drives that have acted like yours. For most, the solution was to replace the drive with a new one and write to lime-technology for a replacement "key" file. You could try re-loading the older version of unRAID by putting back the two old files. Odds are it will still fail to boot, but it would be nice if I'm proven wrong. The reason your syslog was not copied is because the flash drive was not mounted on the /boot mount point, because the "UNRAID" label was not detected. That is the root cause of your problems. The UNRAID label is not readable. Joe L.
August 19, 201015 yr Author Joe, I have a backup USB Flash drive from a previous array and I plugged it in and everything booted normally and I updated it to 4.5.6 OS. Obviously all the disks are in the wrong slots and/or are not shown. I know the next thing to do is Device > and update the slots with my screen shot that I took proior to upgrading, but I wanted to throw a curve call in here. I just purchased a new Supermicro PCIe card as I currently have 8 SATA's on PCIx card and it's terribly slow.... Should I do the smart thing here and just get the disks in the correct slots on the devices page, rebuild parity then go and deal with the new card? Or... should I get the new card installed and go from there? Thoughts? Edit: Is there something I should copy from my 4.3.3 Flash drive to the new Flash drive that would have my updated disk configuration?
August 19, 201015 yr As to the order in which to do things, get things working first, then deal with new hardware or changes. From the config directory, the important file is: super.dat It also shouldn't hurt to copy over the other files as well such as disk.cfg, flash.cfg, share.cfg, passwd, smbpasswd.
August 19, 201015 yr Joe, Edit: Is there something I should copy from my 4.3.3 Flash drive to the new Flash drive that would have my updated disk configuration? The entire "config" folder.
August 20, 201015 yr Author Well I'm back up and running... I installed the new Supermicro AOC-SASLP-MV8 and have all the drives working, except 1! It looks like one of the cables SATA connections is borked as when I moved it to another hard drive the new problem moved to that hard drive... UGH! This problem is closed: Problem USB Flash Drive had a corrupt file system and/or Flash drive is bad Solution: New Flash Drive
Archived
This topic is now archived and is closed to further replies.