December 14, 200916 yr Ok, I left for the weekend and I "powerdown"ed my machine using the powerdown script. I came back home, and realized the power had been interrupted at my place at some point (don't know for how long, though). I powered on my unRAID machine and got this: NEW_ARRAY, unRAID ARRAY is STOPPED 8 disks in array. PARITY NOT VALID: DISK_NEW This sort of alarms me, as the array was fine when I powered it down earlier. Is it ok to start the array? I want to make sure I don't lose any of the data on any of the disk(s). Attached is my syslog.
December 14, 200916 yr Your config/super.dat file is corrupted. These two lines in the syslog are present: Dec 14 00:19:11 Persephone kernel: md: invalid superblock checksum Dec 14 00:19:11 Persephone kernel: md: initializing superblock It is where the array status is stored. As long as all your disks are working you can use the "Trust-my-parity" procedure to get back online without having to wait for a full parity calc to complete, or start the array and let it compute parity. See here in the wiki: http://lime-technology.com/wiki/index.php?title=Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily
December 14, 200916 yr Author Ok, thanks Joe. I'm wondering where it got corrupted from when it shutdown to when it started up.
December 14, 200916 yr Which "powerdown" were you using? The one built into unRAID or the user community addon?
December 14, 200916 yr Which "powerdown" were you using? The one built into unRAID or the user community addon? From one user's experience, the "built-in" command line command Tom added does not first stop the array, so it would cause errors. I've not validated this, but since it invokes the same "url" as the power-down button that is not normally visible unless the array is stopped it makes sense. Unless you typed the full path of /sbin/powerdown, you used the built-in one, as it is first in the execution path.
December 14, 200916 yr Author Hmmm I didn't realize there was a built-in powerdown script. I thought I was using the community script, but I can't be sure now. I putty'd into the server and typed "powerdown". I hadn't realized there was already an alias for this command. Something new: I'm at work and can't see the machine log, but I started the array last night and now I'm getting these emails: This message is a status update for unRAID Persephone ----------------------------------------------------------------- Server Name: Persephone Status: The unRaid array needs attention. One or more disks are disabled or invalid. Date: Mon Dec 14 06:40:00 GMT+8 2009 Disk Temperature Status ----------------------------------------------------------------- Parity Disk [sdd]: 34°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071) Disk 1 [sde]: 32°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028) Disk 2 [sdg]: 29°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530) Disk 3 [sdh]: 34°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483) Disk 4 [sdi]: 29°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295) Disk 5 [sda]: 32°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015) Disk 6 [sdb]: 33°C (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672) Disk 7 [sdf]: 31°C (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410) Disk SMART Health Status ----------------------------------------------------------------- Parity Disk PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071) Disk 1 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028) Disk 2 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530) Disk 3 PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483) Disk 4 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295) Disk 5 PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015) Disk 6 PASSED (DiskId: ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672) Disk 7 PASSED (DiskId: ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410) Output of /proc/mdcmd: ----------------------------------------------------------------- cmdOper=status cmdResult=ok sbName=/boot/config/super.dat sbVersion=0.95.0 sbCreated=1260797923 sbUpdated=1260798274 sbEvents=1 sbState=0 sbNumDisks=8 sbSynced=0 sbSyncErrs=0 mdVersion=0.95.0 mdState=STARTED mdNumProtected=8 mdNumDisabled=0 mdDisabledDisk=0 mdNumInvalid=1 mdInvalidDisk=0 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=1465138552 mdResyncPos=178788816 mdResyncPrcnt=12.2 mdResyncFinish=365.2 mdResyncSpeed=58694 diskNumber.0=0 diskName.0= diskState.0=6 diskSize.0=1465138552 diskModel.0=WDC WD15EADS-00S2B0 diskSerial.0= WD-WCAVY0850071 diskNumReads.0=0 diskNumWrites.0=44707955 diskNumErrors.0=0 diskId.0=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071 rdevNumber.0=0 rdevStatus.0=DISK_INVALID rdevName.0=sdd rdevSize.0=1465138552 rdevModel.0=WDC WD15EADS-00S2B0 rdevSerial.0= WD-WCAVY0850071 rdevId.0=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0850071 diskNumber.1=1 diskName.1=md1 diskState.1=7 diskSize.1=1465138552 diskModel.1=WDC WD15EADS-00P8B0 diskSerial.1= WD-WCAVU0126028 diskNumReads.1=44706779 diskNumWrites.1=8 diskNumErrors.1=0 diskId.1=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028 rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sde rdevSize.1=1465138552 rdevModel.1=WDC WD15EADS-00P8B0 rdevSerial.1= WD-WCAVU0126028 rdevId.1=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0126028 diskNumber.2=2 diskName.2=md2 diskState.2=7 diskSize.2=1465138552 diskModel.2=WDC WD15EADS-00P8B0 diskSerial.2= WD-WCAVU0125530 diskNumReads.2=44707283 diskNumWrites.2=1129 diskNumErrors.2=0 diskId.2=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdg rdevSize.2=1465138552 rdevModel.2=WDC WD15EADS-00P8B0 rdevSerial.2= WD-WCAVU0125530 rdevId.2=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125530 diskNumber.3=3 diskName.3=md3 diskState.3=7 diskSize.3=1465138552 diskModel.3=WDC WD15EADS-00S2B0 diskSerial.3= WD-WCAVY0862483 diskNumReads.3=44707228 diskNumWrites.3=722 diskNumErrors.3=0 diskId.3=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483 rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sdh rdevSize.3=1465138552 rdevModel.3=WDC WD15EADS-00S2B0 rdevSerial.3= WD-WCAVY0862483 rdevId.3=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0862483 diskNumber.4=4 diskName.4=md4 diskState.4=7 diskSize.4=1465138552 diskModel.4=WDC WD15EADS-00P8B0 diskSerial.4= WD-WCAVU0125295 diskNumReads.4=44707424 diskNumWrites.4=1403 diskNumErrors.4=0 diskId.4=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdi rdevSize.4=1465138552 rdevModel.4=WDC WD15EADS-00P8B0 rdevSerial.4= WD-WCAVU0125295 rdevId.4=ata-WDC_WD15EADS-00P8B0_WD-WCAVU0125295 diskNumber.5=5 diskName.5=md5 diskState.5=7 diskSize.5=1465138552 diskModel.5=WDC WD15EADS-00S2B0 diskSerial.5= WD-WCAVY0839015 diskNumReads.5=44707325 diskNumWrites.5=1037 diskNumErrors.5=0 diskId.5=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015 rdevNumber.5=5 rdevStatus.5=DISK_OK rdevName.5=sda rdevSize.5=1465138552 rdevModel.5=WDC WD15EADS-00S2B0 rdevSerial.5= WD-WCAVY0839015 rdevId.5=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0839015 diskNumber.6=6 diskName.6=md6 diskState.6=7 diskSize.6=1465138552 diskModel.6=WDC WD15EADS-00S2B0 diskSerial.6= WD-WCAVY0903672 diskNumReads.6=44706866 diskNumWrites.6=117 diskNumErrors.6=0 diskId.6=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672 rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=sdb rdevSize.6=1465138552 rdevModel.6=WDC WD15EADS-00S2B0 rdevSerial.6= WD-WCAVY0903672 rdevId.6=ata-WDC_WD15EADS-00S2B0_WD-WCAVY0903672 diskNumber.7=7 diskName.7=md7 diskState.7=7 diskSize.7=1465138552 diskModel.7=WDC WD15EADS-00P8B0 diskSerial.7= WD-WMAVU0501410 diskNumReads.7=44707800 diskNumWrites.7=6529 diskNumErrors.7=0 diskId.7=ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410 rdevNumber.7=7 rdevStatus.7=DISK_OK rdevName.7=sdf rdevSize.7=1465138552 rdevModel.7=WDC WD15EADS-00P8B0 rdevSerial.7= WD-WMAVU0501410 rdevId.7=ata-WDC_WD15EADS-00P8B0_WD-WMAVU0501410
December 14, 200916 yr Author Hmmm... not sure what happened, but now I'm getting: Status: unRaid is OK Date: Mon Dec 14 13:25:58 GMT+8 2009 I guess I'll figure out what's going on when I get home.
Archived
This topic is now archived and is closed to further replies.