February 1, 201511 yr I got this email notification from the tower today morning. One of the 10 disks (including parity) in my tower is showing an error (red dot) and is spundown. Can someone help with the code below and see if it the disk has failed or is it something else. Array is still running and the shares are working fine to the best of my knowledge. Any issues with that? This message is a status update for unRAID Tower ----------------------------------------------------------------- Server Name: Tower IP: 192.168.1.133 Status: The unRaid array needs attention. One or more disks are disabled or invalid. Date: Sun Feb 1 04:21:48 CST 2015 Disk Temperature Status ----------------------------------------------------------------- Parity Disk [sdb]: 37C (DiskId: ST3000DM001-9YN166_Z1F0GEMK) Disk 1 [sdc]: 36C (DiskId: ST3000DM001-9YN166_S1F0235Z) Disk 2 [sdd]: 38C (DiskId: ST3000DM001-9YN166_W1F0F7G2) Disk 3 [sde]: 35C (DiskId: ST3000DM001-9YN166_W1F0F71L) Disk 4 [sdg]: 34C (DiskId: ST3000DM001-9YN166_Z1F0FB6R) Disk 5 [sdf]: 38C (DiskId: Hitachi_HDS723030ALA640_MK0331YHGRPNLA) Disk 6 [sdl]: 34C (DiskId: ST3000DM001-1CH166_W1F14EBG) Disk 7 [sdh]: Not-Reported (DiskId: WDC_WD30EZRX-00MMMB0_WD-WCAWZ1092610) Disk 8 [sdj]: 42C (DiskId: ST3000DM001-9YN166_Z1F0FGH8) Disk 9 [sdi]: 33C (DiskId: ST2000DM001-9YN164_S2F01BQQ) Disk 10 [sdk1]: Not-Reported (DiskId: Samsung_SSD_840_EVO_250GB_S1DBNSADB02680H_) Disk SMART Health Status ----------------------------------------------------------------- Parity Disk PASSED (DiskId: ST3000DM001-9YN166_Z1F0GEMK) Disk 1 PASSED (DiskId: ST3000DM001-9YN166_S1F0235Z) Disk 2 PASSED (DiskId: ST3000DM001-9YN166_W1F0F7G2) Disk 3 PASSED (DiskId: ST3000DM001-9YN166_W1F0F71L) Disk 4 PASSED (DiskId: ST3000DM001-9YN166_Z1F0FB6R) Disk 5 PASSED (DiskId: Hitachi_HDS723030ALA640_MK0331YHGRPNLA) Disk 6 PASSED (DiskId: ST3000DM001-1CH166_W1F14EBG) Disk 7 Not-Reported (DiskId: WDC_WD30EZRX-00MMMB0_WD-WCAWZ1092610) Disk 8 PASSED (DiskId: ST3000DM001-9YN166_Z1F0FGH8) Disk 9 PASSED (DiskId: ST2000DM001-9YN164_S2F01BQQ) Disk 10 PASSED (DiskId: Samsung_SSD_840_EVO_250GB_S1DBNSADB02680H_) Output of /proc/mdcmd: ----------------------------------------------------------------- sbName=/boot/config/super.dat sbVersion=2.1.3 sbCreated=1337443651 sbUpdated=1422786087 sbEvents=424 sbState=0 sbNumDisks=10 sbSynced=1422628462 sbSyncErrs=0 mdVersion=2.2.0 mdState=STARTED mdNumProtected=10 mdNumDisabled=1 mdDisabledDisk=7 mdNumInvalid=1 mdInvalidDisk=7 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=0 mdResyncCorr=0 mdResyncPos=0 mdResyncDt=0 mdResyncDb=0 diskNumber.0=0 diskName.0= diskSize.0=2930266532 diskState.0=7 diskId.0=ST3000DM001-9YN166_Z1F0GEMK rdevNumber.0=0 rdevStatus.0=DISK_OK rdevName.0=sdb rdevSize.0=2930266532 rdevId.0=ST3000DM001-9YN166_Z1F0GEMK rdevNumErrors.0=0 rdevLastIO.0=1422786100 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=2930266532 diskState.1=7 diskId.1=ST3000DM001-9YN166_S1F0235Z rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sdc rdevSize.1=2930266532 rdevId.1=ST3000DM001-9YN166_S1F0235Z rdevNumErrors.1=0 rdevLastIO.1=1422786066 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=2930266532 diskState.2=7 diskId.2=ST3000DM001-9YN166_W1F0F7G2 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdd rdevSize.2=2930266532 rdevId.2=ST3000DM001-9YN166_W1F0F7G2 rdevNumErrors.2=0 rdevLastIO.2=1422786066 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=2930266532 diskState.3=7 diskId.3=ST3000DM001-9YN166_W1F0F71L rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sde rdevSize.3=2930266532 rdevId.3=ST3000DM001-9YN166_W1F0F71L rdevNumErrors.3=0 rdevLastIO.3=1422786066 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4=md4 diskSize.4=2930266532 diskState.4=7 diskId.4=ST3000DM001-9YN166_Z1F0FB6R rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdg rdevSize.4=2930266532 rdevId.4=ST3000DM001-9YN166_Z1F0FB6R rdevNumErrors.4=0 rdevLastIO.4=1422786066 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5=md5 diskSize.5=2930266532 diskState.5=7 diskId.5=Hitachi_HDS723030ALA640_MK0331YHGRPNLA rdevNumber.5=5 rdevStatus.5=DISK_OK rdevName.5=sdf rdevSize.5=2930266532 rdevId.5=Hitachi_HDS723030ALA640_MK0331YHGRPNLA rdevNumErrors.5=0 rdevLastIO.5=1422786066 rdevSpinupGroup.5=0 diskNumber.6=6 diskName.6=md6 diskSize.6=2930266532 diskState.6=7 diskId.6=ST3000DM001-1CH166_W1F14EBG rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=sdl rdevSize.6=2930266532 rdevId.6=ST3000DM001-1CH166_W1F14EBG rdevNumErrors.6=0 rdevLastIO.6=1422786100 rdevSpinupGroup.6=0 diskNumber.7=7 diskName.7=md7 diskSize.7=2930266532 diskState.7=4 diskId.7=WDC_WD30EZRX-00MMMB0_WD-WCAWZ1092610 rdevNumber.7=7 rdevStatus.7=DISK_DSBL rdevName.7=sdh rdevSize.7=2930266532 rdevId.7=WDC_WD30EZRX-00MMMB0_WD-WCAWZ1092610 rdevNumErrors.7=681 rdevLastIO.7=1422786087 rdevSpinupGroup.7=0 diskNumber.8=8 diskName.8=md8 diskSize.8=2930266532 diskState.8=7 diskId.8=ST3000DM001-9YN166_Z1F0FGH8 rdevNumber.8=8 rdevStatus.8=DISK_OK rdevName.8=sdj rdevSize.8=2930266532 rdevId.8=ST3000DM001-9YN166_Z1F0FGH8 rdevNumErrors.8=0 rdevLastIO.8=1422786066 rdevSpinupGroup.8=0 diskNumber.9=9 diskName.9=md9 diskSize.9=1953514552 diskState.9=7 diskId.9=ST2000DM001-9YN164_S2F01BQQ rdevNumber.9=9 rdevStatus.9=DISK_OK rdevName.9=sdi rdevSize.9=1953514552 rdevId.9=ST2000DM001-9YN164_S2F01BQQ rdevNumErrors.9=0 rdevLastIO.9=1422786066 rdevSpinupGroup.9=0 diskNumber.10=10 diskName.10= diskSize.10=0 diskState.10=0 diskId.10= rdevNumber.10=10 rdevStatus.10=DISK_NP rdevName.10= rdevSize.10=0 rdevId.10= rdevNumErrors.10=0 rdevLastIO.10=0 rdevSpinupGroup.10=0 diskNumber.11=11 diskName.11= diskSize.11=0 diskState.11=0 diskId.11= rdevNumber.11=11 rdevStatus.11=DISK_NP rdevName.11= rdevSize.11=0 rdevId.11= rdevNumErrors.11=0 rdevLastIO.11=0 rdevSpinupGroup.11=0 diskNumber.12=12 diskName.12= diskSize.12=0 diskState.12=0 diskId.12= rdevNumber.12=12 rdevStatus.12=DISK_NP rdevName.12= rdevSize.12=0 rdevId.12= rdevNumErrors.12=0 rdevLastIO.12=0 rdevSpinupGroup.12=0 diskNumber.13=13 diskName.13= diskSize.13=0 diskState.13=0 diskId.13= rdevNumber.13=13 rdevStatus.13=DISK_NP rdevName.13= rdevSize.13=0 rdevId.13= rdevNumErrors.13=0 rdevLastIO.13=0 rdevSpinupGroup.13=0 diskNumber.14=14 diskName.14= diskSize.14=0 diskState.14=0 diskId.14= rdevNumber.14=14 rdevStatus.14=DISK_NP rdevName.14= rdevSize.14=0 rdevId.14= rdevNumErrors.14=0 rdevLastIO.14=0 rdevSpinupGroup.14=0 diskNumber.15=15 diskName.15= diskSize.15=0 diskState.15=0 diskId.15= rdevNumber.15=15 rdevStatus.15=DISK_NP rdevName.15= rdevSize.15=0 rdevId.15= rdevNumErrors.15=0 rdevLastIO.15=0 rdevSpinupGroup.15=0 diskNumber.16=16 diskName.16= diskSize.16=0 diskState.16=0 diskId.16= rdevNumber.16=16 rdevStatus.16=DISK_NP rdevName.16= rdevSize.16=0 rdevId.16= rdevNumErrors.16=0 rdevLastIO.16=0 rdevSpinupGroup.16=0 diskNumber.17=17 diskName.17= diskSize.17=0 diskState.17=0 diskId.17= rdevNumber.17=17 rdevStatus.17=DISK_NP rdevName.17= rdevSize.17=0 rdevId.17= rdevNumErrors.17=0 rdevLastIO.17=0 rdevSpinupGroup.17=0 diskNumber.18=18 diskName.18= diskSize.18=0 diskState.18=0 diskId.18= rdevNumber.18=18 rdevStatus.18=DISK_NP rdevName.18= rdevSize.18=0 rdevId.18= rdevNumErrors.18=0 rdevLastIO.18=0 rdevSpinupGroup.18=0 diskNumber.19=19 diskName.19= diskSize.19=0 diskState.19=0 diskId.19= rdevNumber.19=19 rdevStatus.19=DISK_NP rdevName.19= rdevSize.19=0 rdevId.19= rdevNumErrors.19=0 rdevLastIO.19=0 rdevSpinupGroup.19=0 diskNumber.20=20 diskName.20= diskSize.20=0 diskState.20=0 diskId.20= rdevNumber.20=20 rdevStatus.20=DISK_NP rdevName.20= rdevSize.20=0 rdevId.20= rdevNumErrors.20=0 rdevLastIO.20=0 rdevSpinupGroup.20=0 diskNumber.21=21 diskName.21= diskSize.21=0 diskState.21=0 diskId.21= rdevNumber.21=21 rdevStatus.21=DISK_NP rdevName.21= rdevSize.21=0 rdevId.21= rdevNumErrors.21=0 rdevLastIO.21=0 rdevSpinupGroup.21=0 diskNumber.22=22 diskName.22= diskSize.22=0 diskState.22=0 diskId.22= rdevNumber.22=22 rdevStatus.22=DISK_NP rdevName.22= rdevSize.22=0 rdevId.22= rdevNumErrors.22=0 rdevLastIO.22=0 rdevSpinupGroup.22=0 diskNumber.23=23 diskName.23= diskSize.23=0 diskState.23=0 diskId.23= rdevNumber.23=23 rdevStatus.23=DISK_NP rdevName.23= rdevSize.23=0 rdevId.23= rdevNumErrors.23=0 rdevLastIO.23=0 rdevSpinupGroup.23=0
February 1, 201511 yr All of your shares / files available are because with the failed drive unRaid is "emulating" the drive using the parity disk and the remaining other drives. You should really post a syslog as right now all we can tell is that for some reason disk 7 isn't reporting its heath status. And maybe a screen shot of the unRaid main menu
February 1, 201511 yr Author Thanks for taking a look Squid. Here are the screenshots and the syslog. Should I stop the array or let it run? Thanks, Abhi syslog-2015-02-01.zip
February 1, 201511 yr If you just let the array run, in a degraded state (one disk redballed), then if another drive failure happens, then you WILL lose data. Right now you have not lost anything. My first thought from looking at your syslog, is that it is a bad drive, because before the drive dropped from the array, you did have some Feb 1 04:21:06 Tower kernel: ata7.00: cmd 25/00:00:f0:b9:53/00:04:7f:00:00/e0 tag 0 dma 524288 in Feb 1 04:21:06 Tower kernel: res 51/40:3f:a8:ba:53/00:03:7f:00:00/e0 Emask 0x9 (media error) errors. However, it is possible that this could just be a bad /loose cable or a power issue.] I would reseat the cables at both the drive end and mobo end and restart server right now and seeing whether that drive is even recognized. If it is, then you could try posting the smart attributes from it. Otherwise its most likely an outright bad drive and should be replaced asap
February 4, 201511 yr Author Okay - looks like it was a disk issue. So I replaced the WDC Green drive with a Seagate Barracuda - and followed the steps on the wiki for replacing and now it is rebuilding the data on the new drive. Is that process really slow? My parity check usually gets done at over a 100MB/s in under 5 or 6 hours, never replaced a disk before so this is new to me. Also I made sure by going into the BIOS before starting that the SATA configuration was in AHCI mode. My MB always reverts to IDE after I perform some alteration of the hardware, I did replace the case and beefed up the power supply while at it. So I did make sure the configuration was set to AHCI before powering on. Mentioning this here because I read on the forum that the IDE configuration could cause the performance to slow down - I know that is not the case here. Any other reasons? Thanks,
February 4, 201511 yr Okay - looks like it was a disk issue. So I replaced the WDC Green drive with a Seagate Barracuda - and followed the steps on the wiki for replacing and now it is rebuilding the data on the new drive. Is that process really slow? My parity check usually gets done at over a 100MB/s in under 5 or 6 hours, never replaced a disk before so this is new to me. Also I made sure by going into the BIOS before starting that the SATA configuration was in AHCI mode. My MB always reverts to IDE after I perform some alteration of the hardware, I did replace the case and beefed up the power supply while at it. So I did make sure the configuration was set to AHCI before powering on. Mentioning this here because I read on the forum that the IDE configuration could cause the performance to slow down - I know that is not the case here. Any other reasons? Thanks, Yeah, it does seem a bit slow, but it depends upon what else is going on with the system. If you're playing a movie, copying files, or if cache dirs is running it will all slow down. But, now that it's started I would just let it finish. Play around with increasing the speed if need be on a non correcting parity check. As for why the mobo keeps reverting to legacy (ide) mode - maybe the battery is dead.
February 5, 201511 yr Author OKay the WebGUI crashed and the server is not responding - putty or even connected to a monitor - I see no activity. Hardware is still running - fans are spinning and LED's are on etc - but no life of the server actually running. I am worried since this happened in the middle of a data rebuild - which I was sure wasn't over it was well over 50% when I last checked but I am sure it was still not done. What do I do? Do I hard rebooot or just let it run? Any help please?
February 5, 201511 yr OKay the WebGUI crashed and the server is not responding - putty or even connected to a monitor - I see no activity. Hardware is still running - fans are spinning and LED's are on etc - but no life of the server actually running. I am worried since this happened in the middle of a data rebuild - which I was sure wasn't over it was well over 50% when I last checked but I am sure it was still not done. What do I do? Do I hard rebooot or just let it run? Any help please? Without any putty access or even console access (have you tried pressing a key? - Some of the v5's had a screen saver built in), the system has probably crashed hard and the rebuilding process is now over. If you're really paranoid, you can let it sit for awhile and see if anything ever happens, but I doubt it will. You're going to have to physically reset the system. Assuming that none of the other drives redballed, then you'll still be able to rebuild the drive. But, we do have to figure out why it crashed in the first place. After a reboot, log into the console and enter this: tail -f --lines=100 /var/log/syslog >/boot/syslogtail.txt It will continually capture the syslog and save it onto your flash so that if it happens again during the rebuild we can figure out what happened. You should also post up the syslog after the reboot because there may be errors in it prior to rebuilding.
February 6, 201511 yr Author I did physically reset (hard reboot) and start again. No issues this time and it just got done a little while back. All looking good - thanks for the help! The disk that had been replaced is still in the tower but not in the array - can I try and preclear the disk and see if it shows any errors or should I just let it be and assume it is dead?
February 8, 201511 yr Author Okay I tried to run preclear using Screen as instructed in the wiki. However, preclear_disk.sh -l , does not retun the unassigned drive (sdh). It just shows a multicard reader (sdb) I have on the case connected to the USB port on the MB. Both screenshots are attached. Why is the unassigned drive not showing up? Unassigned disk shown as sdh: Results of the above code showing drives available to preclear:
February 9, 201511 yr Author Has the array been started with the disk unassigned? Yes - the array has been started after this particular disk was replaced with another one as it showed faulty and the data was rebuilt and array is running now. That screenshot of the unassigned disk is with the array running.
February 10, 201511 yr If the drive is dead it may not show up at all. Is it listed during POST when booting up?
February 13, 201511 yr Author Yes - it does, it does get detected by unRAID as well as you can see in the unassigned and not in the array. I tried stopping the array and then assigning it as Drive 10 and it showed up as blue (new drive) and the array operation tab let me start a pre-clear on it. (I did not do it as I needed to access the array). So my question is can I run pre-clear on a an unassigned disk with the array started (using SSH/Telnet and screen) or can preclear only be run when the array is stopped?
February 13, 201511 yr So my question is can I run pre-clear on a an unassigned disk with the array started (using SSH/Telnet and screen) or can preclear only be run when the array is stopped? Yes, you can preclear while the array is started if you are using the preclear script. That is one reason why it was developed. See here for details: http://lime-technology.com/forum/index.php?topic=2817.0
February 13, 201511 yr I've always avoid using the term preclear unless I mean the preclear script. unRAID itself clears a new drive that has not already been precleared. I know it's hopeless to get everyone else to be consistent on this.
February 13, 201511 yr I've always avoid using the term preclear unless I mean the preclear script. unRAID itself clears a new drive that has not already been precleared. I know it's hopeless to get everyone else to be consistent on this. +1 That is the reason I always make sure to indicate which process I am referring to. While they both do the same thing but (as I recall) the internal unRAID clear process takes the array offline until it is finished. Many users are not really that aware that there are two ways to do the same thing and if they confuse one with the other, some real communication issues can occur. That is why I try to always be crystal clear which one I am talking about.
February 13, 201511 yr While they both do the same thing but (as I recall) the internal unRAID clear process takes the array offline until it is finished. I wouldn't say they do the same thing at all. The only common step in both processes is the writing of zeroes to the drive. While that zeroing process is the intended goal, the rest of the process and the two end results are different. Preclear - obtains a smart report, reads and writes in multiple passes, ending with a read that verifies all zeroes, obtains another smart report and compares the two reports and alerts to any changes, and adds a signature to allow quick adding of the drive to a parity protected array at a later time. Unraid clearing process only writes zeroes and immediately adds the drive to the array after it is done. No smart checking, no verification that the zeroes actually wrote correctly, etc. Additionally, the array is unavailable while the zeroes are written.
February 13, 201511 yr Author So my question is can I run pre-clear on a an unassigned disk with the array started (using SSH/Telnet and screen) or can preclear only be run when the array is stopped? Yes, you can preclear while the array is started if you are using the preclear script. That is one reason why it was developed. See here for details: http://lime-technology.com/forum/index.php?topic=2817.0 Then any ideas why it is not showing up as part of the drives that is available to be cleared as shown below. ? Okay I tried to run preclear using Screen as instructed in the wiki. However, preclear_disk.sh -l , does not retun the unassigned drive (sdh). It just shows a multicard reader (sdb) I have on the case connected to the USB port on the MB. Both screenshots are attached. Why is the unassigned drive not showing up? Unassigned disk shown as sdh: Results of the above code showing drives available to preclear:
February 13, 201511 yr Author I've always avoid using the term preclear unless I mean the preclear script. unRAID itself clears a new drive that has not already been precleared. I know it's hopeless to get everyone else to be consistent on this. Point noted trurl - I assumed it was the same thing - but I guess you are saying there is a difference. Thanks. So rephrasing, for my issue as part of the preclear script while checking preclear_disk.sh -l the drive does not show as one available for preclearing. This is with the array running. But if I stop the array and try to assign the drive it shows as new (blue dot) and the unRAID built in Clear does work. I needed to access the array so did not end up running it here. Question is why one detects the drive and the other doesn't? Screenshots are attached below? Any and all help appreciated.
February 13, 201511 yr Try using the preclear script specifying /dev/sdh as the drive to be cleared. TRIPLE check that the drive with the proper serial number is shown as the one to be cleared before you type "Yes". If the preclear script comes back with an error, post the problem in the Preclear script thread here: http://lime-technology.com/forum/index.php?topic=4068.0 If you are still uncomfortable proceeding or want to know why this drive is not showing as unassigned, I would suggest posting a query on that thread, stating the problem and a link to this thread. You should then get an answer from the Author of the preclear script.
Archived
This topic is now archived and is closed to further replies.