December 30, 201015 yr ?I haven't made any changes to this server in weeks, but had trouble accessing certain files on it today. After which, i then tried to access the web page, but couldn't. Since it is run headless, I had originally added a script (from these forums) to run the shutdown script when the power btn is pushed once. SO I pressed power, and it appeared to access the flash drive for a while, and shut down gracefully. When I booted unraid back up, i saw the following webpages with DSBL_NEW, and a Blue Ball near the parity drive. Again, i have NOT changed any hardware. The zip file shows pre-shutdown and post-reboot syslogs. One was 134MB over 12 hours, both syslogs are showing some drive errors. My first instinct was to just hit "rebuild parity", but wasn't sure if this was the safest route. Is the parity drive still good? Thanks in advance for any ideas. Don [/img]C:\Users\d\Pictures\unraid_dsbl_docs\unraid drive blue ball disabled.jpg[/img]
December 30, 201015 yr Author attached is the edited pre shutdown log....before 6pm it appeared to be just neverending repeats of the same error message syslog_preshutdown_edited.zip
December 31, 201015 yr Author Update...I tried to do a NOCORRECT parity check, but it just fails since array isn't started. IS there a way to see if the parity drive has really failed? I feel like if i just force it to recalc parity, i'm trusting all the other drives to be right, when i still cant understand why unraid thinks the parity drive is new latest syslog attached showing my attempt with unknown errors repeating above it, syslog-2010-12-31.zip
December 31, 201015 yr Update...I tried to do a NOCORRECT parity check, but it just fails since array isn't started. IS there a way to see if the parity drive has really failed? I feel like if i just force it to recalc parity, i'm trusting all the other drives to be right, when i still cant understand why unraid thinks the parity drive is new latest syslog attached showing my attempt with unknown errors repeating above it, You can run smartctl -d ata -a /dev/sdX where sdX = the drive's device you can run hdparm -tT /dev/sdX If you have unMENU installed, both can be run from the disk-management page with a button click, even with the array stopped. Joe L.
December 31, 201015 yr Since it is run headless, I had originally added a script (from these forums) to run the shutdown script when the power btn is pushed once. This would be very handy to have....could you please point me in the right direction?
December 31, 201015 yr Author Since it is run headless, I had originally added a script (from these forums) to run the shutdown script when the power btn is pushed once. This would be very handy to have....could you please point me in the right direction? The reason i was a bit vague about which script did it, is that i don't exactly remember, b/c I installed a lot of things all at once, after I discovered the Package Manager tab in the latest unMenu. I believe the "clean powerdown" button on the screenshot below replaces the stock unraid pwrdn script with a less violent shutdown that won't induce a parity check every time. I have the BIOS power button action set to "pwr off after 4 secs"...which means the that you have to press the power button coninuously for 4 secs to do a hard shutdown. I beileve just pressing it once invokes the above script, perhaps by sending a CTRL-ALT-DEL, which is wha tthe script is designed to catch. Hope this helps! Don
December 31, 201015 yr Author Update...I tried to do a NOCORRECT parity check, but it just fails since array isn't started. IS there a way to see if the parity drive has really failed? I feel like if i just force it to recalc parity, i'm trusting all the other drives to be right, when i still cant understand why unraid thinks the parity drive is new latest syslog attached showing my attempt with unknown errors repeating above it, You can run smartctl -d ata -a /dev/sdX where sdX = the drive's device you can run hdparm -tT /dev/sdX If you have unMENU installed, both can be run from the disk-management page with a button click, even with the array stopped. Joe L. Hey Joe, I ran these, and all the smartctl said Passed and the HDPARM's said checksum passed...I dont know too much about the other numbers(i attched the putty.log below, for the curious) Strangely though, i get a "SMART health check Failed" in the smart history report, but just on the two hitachi drives, the 3 samsungs and 1 seagate seem ok...I'll attach the smart history report below smartctl.txt
December 31, 201015 yr Author Ok...i couldnt attach the whole smart history report for size reasons...but oddly now, when i re-ran the report to only print first three pages to pdf, only ONE of the two fails. The results dont seem consistent in smarthistory. I;ve attached the first three pages where only one hitachi drive fails the smart health check. And if i dont get back here today...happy new year to all! Tower_unRAID_Server_pp1-3.pdf
Archived
This topic is now archived and is closed to further replies.