July 4, 201115 yr This system has been up for the past 5 months since a USB failure, and about 4 months before that. Aside from the previous USB failure (it was a cheap memory stick, lesson learned) all has worked well. I began running uprime on the system about a week ago to utilize all those otherwise unused CPU cycles and came home one day to find that it had shut itself off, and had been restarted by someone else in the house. It must have been an overheating or memory overrun issue since the system rarely gets a hard reboot and is protected by a UPS for power fluctuations. Unfortunately there is no surviving syslog of the event. The system normally runs headless, so after finding a monitor and powering up, it POST'ed fine and then hung at syslinux (before decompressing the bzroot kernel image). Unfortunately since it is so early in the boot process there is no way I know of to extract any additional helpful information. The best I can do is some basics on the setup: I am running Unraid server 4.7 with a plus license The USB I am using to boot from is a Kingston Data Traveler 4GB The motherboard is an ECS GF8200A Black Series 5 2TB Western Digital WD20EARS drives, and one old maxtor diamondmax 200gb drive that isn't part of the array My syslinux.cfg reads: default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot label Memtest86+ kernel memtest I have searched the forums and looked through the wiki, online manual, and FAQ and found only these two posts relating to this issue, neither of which led to a solution for me: http://lime-technology.com/forum/index.php?topic=1534.0 http://lime-technology.com/forum/index.php?topic=13596.msg128798#msg128798 Any thoughts on what steps to take next would be appreciated. Thanks! Dave
July 11, 201114 yr Author Run check disk on the flash drive in Windows. Thanks for the reply. I ran chkdsk on the drive and found that it had corrupted sectors. I 'recovered' them, but the info that was recovered was unusable. At this point it would be easiest to start over with a fresh install of unraid on the flash drive. Edit: After reformatting flash and doing a fresh install of unraid on it everything is up and working now. Although this method may not be a 'fix' as such, it is effective. For anyone else that runs into this issue, this is likely the easiest solution. Just remember to copy your key if you are running a Plus or Pro version before formatting!
Archived
This topic is now archived and is closed to further replies.