May 28, 201214 yr I removed a disk in hopes of preclearing more drives at one time. This was addressed in another post. As a result, when I tried to put the original drive back into the machine the array did not recognize the drive. (Can't hot swap drives.) I unassigned the drive under devices. I tried putting the drive in another slot. It didn't help. I powered down and put the drive back into it's original slot. Booted and assigned the drive I now have a blue indicator next to the drive indicating that it is a new drive. I have about 800MB on this disk that I do not want to lose. I am running 4.7. Joe L stated in the other post. Setting a new disk configuration will immediately invalidate any parity calculations, so upon starting the array, parity will be re-calculated. Also, you must be VERY CAREFUL if you attempt to re-add the original drive back to its original slot. Unless you AGAIN set a new disk configuration, the drive will be zeroed. (not what you want if there is data on it) I have not been able to find anything in the wiki about this. I've included the current syslog and smart report as well. I need some help please. syslog-2012-05-24.txt syslog-2012-05-25.txt smart_report.txt
May 29, 201214 yr Author Here is the the main screen. Where or how do I enter initconfig? Array Status RECON_DISK, unRAID ARRAY is STOPPED 5 disks in array. Parity is Valid:. Last parity check 5 days ago with no sync errors. Array Disk Status Status Disk Mounted Device Model/Serial Temp Reads Writes Errors Size Used %Used Free OK parity /dev/sdd SAMSUNG_HD204UI_S2H7JD2B227180 * 5367 456 OK /dev/md1 /dev/sdf SAMSUNG_HD204UI_S2H7JD2B227115 * 10131 26 OK /dev/md2 /dev/sdg SAMSUNG_HD204UI_S2H7JD5ZC01566 * 75168 26 OK /dev/md3 /dev/sda SAMSUNG_HD204UI_S2H7JX0B900925 * 7683 25 New Disk /dev/md4 /dev/sdc * 207 0 Total: 0.00K 0.00K 78% 0.00K UNRAID Drive Device Model/Serial Mounted File System Size Used %Used Free /dev/sdb1 usb-Kingston_Reader_SD_MS_AA00000000176750-0:0 /boot vfat 3.96G 85.03M 3% 3.87G Drive Partitions - Not In Protected Array Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/sde SAMSUNG_HD103UJ_S13PJ9CSB00035 23°C 1.00T /dev/sde1 SAMSUNG_HD103UJ_S13PJ9CSB00035 reiserfs 23°C
May 29, 201214 yr Author I typed the command in and the new main is: Since I am in unfamiliar territory I don't want to do anything that might destroy my data. Is it correct the next step is to start the array and let it run a parity-sync? Is there a way to just do a parity check and not a rebuild as referenced below? The parity should not have changed since no data has been added nor deleted and each disk is in the same slot. 12: SET INVALIDSLOT - Special command that tells unRAID that the array is already protected. Starting the array after this command will trigger a PARITY CHECK and not a PARITY REBUILD. (Remember that the array is protected during a parity check, but not during a parity rebuild). Array Status NEW_ARRAY, unRAID ARRAY is STOPPED 5 disks in array. PARITY NOT VALID: DISK_NEW Array Disk Status Status Disk Mounted Device Model/Serial Temp Reads Writes Errors Size Used %Used Free DISK_NEW new disk /dev/sdd * 5368 456 DISK_NEW new disk /dev/sdf * 10132 26 DISK_NEW new disk /dev/sdg * 75169 26 DISK_NEW new disk /dev/sda * 7684 25 DISK_NEW new disk /dev/sdc * 208 0 Total: 0.00K 0.00K 78% 0.00K UNRAID Drive Device Model/Serial Mounted File System Size Used %Used Free /dev/sdb1 usb-Kingston_Reader_SD_MS_AA00000000176750-0:0 /boot vfat 3.96G 85.00M 3% 3.87G Drive Partitions - Not In Protected Array Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/sde SAMSUNG_HD103UJ_S13PJ9CSB00035 * 1.00T /dev/sde1 SAMSUNG_HD103UJ_S13PJ9CSB00035 *
May 29, 201214 yr No. You're at a point where you need to rebuild your parity. You're essentially starting over. You can't even do a parity check, because you no longer have a valid parity drive. Just assign your drives as before and start building your parity.
Archived
This topic is now archived and is closed to further replies.