mrwood

Not sure how I crashed it, but a FREE upgrade to the latest version OS has me back up & running! Thanks Danioj for the links. I followed the process, transferred some of my old files & key, and server came up. Parity valid. Got a SMART status warning for one disk ('current pending sector'); this is a new feature for me, so I will have to do some research. Best news - wife happy, she can access her files & do the taxes!

Thanks - appreciate the input! I can access the USB files on another computer. I tried to find a current syslog file (no luck - all log files from last troubleshooting in 2012.....). Let me know if I should check some other files on USB stick. I am certainly open to upgrading software. Especially if that can get me a command prompt & enhance my troubleshooting!

Need some help getting my server back on line. Server has worked fine for years. I got a new router & moved the server, and now I can't bring my server online. This is an older unRAID OS (v 4.6?). I have the server on my workbench, not hooked up to my network. I can get to the boot screen where you select OS or memtest. The computer then auto boots into unRAID OS. Then I get some errors and no prompt. I can not produce a syslog file. FWIW, I did grab a screen shot (see attached). Sorry my unRAID skills are a little rusty! I would appreciate input on next steps for troubleshooting. I need some files from server for taxes!

Think I got this solved! I have rebuilt & checked parity = OK. I ended up replacing the hard drive. I tried working with the old one, but could not get parity to check. I switched cables, replaced a cooling fan, swapped out Norco units, no luck. Could not get the parity to check after a rebuild. Decided to replace the hard drive when I was running out of troubleshooting steps. The old one did not fail a smart check, but could not pass parity. I got a new drive, ran preclear twice, and parity is up & fixed. Thanks for all the help !

HA! my ace detective work has developed clue to my cooling concern. The fan is not working on my Norco unit.... The fans are working on the other Norco hot swap modules, but not this one. This unit is filled with my four WD drives. I am troubleshooting this now. I have switched some cables - no luck. I am going to try a replacement fan. Temps have always been higher for my WD drives. Now I know why... Rarely at 50C, but I did notice this temp after heavy usage (rebuit parity, then check parity). This usage can take >3 hrs. Once I get my cooling fixed, I will give parity another try.

Will do - but not sure how.... I have an open slot on my NORCO Hot Swap Rack. Could I just move the drive to one of the open bays? This would (kinda of) get me a new cable. Would UnRaid still recognize this as my parity drive?

Bump to the 1st page - I am still looking for some help ! Any input?

Thanks - good advice, and I still have problems ! You are correct - I did just rebuild parity, and did not perform a check. I now have ran a parity check and it failed. I got the same error message PARITY NOT VALID: DISK_DSBL, and my parity disk has been disabled. It seemed to be going well. I was able to refresh my screen periodically and saw that it was progressing without errors. Last I saw it was at 94%. Here is a link to an updated syslog https://docs.google.com/open?id=0B0PxQbEvxyY1V210dUdnZWZFaWc I powered down the array & restarted. I ran a smart test on the parity disk (see attached) smartctl -a -d ata /dev/sdc | todos >/boot/smart.txt The drive passed again, this time with no pending sectors - "Reallocated_Sector_Ct", the RAW_VALUE = 0 - "Current_Pending_Sector", the RAW_VALUE = 0 - "Temperature_Celsius" = 41 The temperatures have always been high with my WD drives - higher than my Seagates & Hitachi drives. The parity drive is a 2TB WD EARS-00M. I did notices the WD drives (cache, parity, storage) at ~50C during the parity check. I have wanted to review my cooliing, to make sure I have the fans correct for an efficient flow. Not sure if this is cause of my problems. Any thoughts on next steps? Try to rebuild parity again, then check again? smart2.txt

I am back in business - parity is valid ! Thank you for your assistance !

Thanks - I pressed start & now rebuilding parity. I will report back when done !

Thanks for the input - I did power down the array & checked for loose connections. I did not find any, but check/pushed in the applicable plugs. I power up the array & received this message: (UnRAID Main) Stopped. New parity disk installed. (MyMain) RECON_DISK, unRAID ARRAY is STOPPED 7 disks in array. PARITY NOT VALID: DISK_DSBL_NEW The parity disk is flagged as DSBL_NEW I ran a smart test on the parity disk (see attached) smartctl -a -d ata /dev/sdc | todos >/boot/smart.txt Looks like it passed - "Reallocated_Sector_Ct", the RAW_VALUE = 0 - "Current_Pending_Sector", the RAW_VALUE = 21 - "Temperature_Celsius" = 40 Any feedback on these results? It appears the 'current pending sector' value is not good news. My temperatures have been high, but primarily with the WD drives. Anything I should do? Run smart report monthly? Assuming the parity drive is Ok to return to service, what are my next steps? Press 'refresh' via UnRAID Main menu (the Start is disabled)? smart.txt

Hello - I need some help today ! I ran parity last night & it failed. Looks like my parity disk has been disabled. Here is an excerpt of my syslog - it is too big to attach (12MB). Dec 1 04:40:01 Tower syslogd 1.4.1: restart. Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Dec 1 04:40:04 Tower kernel: ata2: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 1 04:40:04 Tower kernel: ata2: status=0x41 { DriveReady Error } Dec 1 04:40:04 Tower kernel: ata2: error=0x04 { DriveStatusError } Here is a link to my complete syslog: https://docs.google.com/open?id=0B0PxQbEvxyY1T0xVbC1rN3liQ0U I am running version 4.7 I tried to run a smart test (short) on this disk and got this message: smartctl -t short -d ata /dev/sdc 2>&1 smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. It appears that when checking parity, there was a failure to write to the parity drive & it was disabled. I found these corrective actions, and I would like some confirmation/advice before I proceed: >>The reason for the "write" failure could be anything from a loose cable/bad cable (power or data) or a power supply unable to keep up to the total demands of the server, to a bad sector on the disk, or a bad disk. You need to try to get a smart report from the disk. Then, stop the array, power down, re-seat the cables, and see if it subsequently responds. Then, you'll need to re-construct the disabled drive (assuming it is good)

Thanks Joe - sounds right My syslog did imply that I had some flash drive problem

I think I did do proper shutdown ! Any other reason why it would trigger a parity check after a startup? I stopped the array from the unRAID Web Management page with the Stop button, then used the Power Down button. All the lights were off when I pressed the power button to reboot. My last parity check was 7 days ago with no errors. All appears to be working now (36% into parity check), but not sure why I lost UnMenu & then triggered a parity check.

Thanks - Ran chkdsk w/no errors. Flash drive looks OK. Today, I can access the server via the standard Web Management Utility using: //tower or http://tower/main.htm but could not access mymain not via my bookmark http://tower:8080/myMain I rebooted, and can now access unmenu. Not sure why I lost it, but I got it back now! (However, I should have tried to restart unmenu from the console. My tower is now going through a parity check - I did not know it would run a parity check after a reboot !) Thanks for your help !