July 5, 200917 yr Hi all. Hopefully this is something simple, but I didn't want to mess anything up by tinkering with it. Yesterday I finished building my first unRAID build. Per some suggestions seen in other threads, I copied about 720GB of data to my array (some to each of two data disks) with no parity drive assigned. Once the data copied, I assigned the parity drive and let it do a parity sync (that was this morning). Everything seemed to be working fine since the parity sync until I decided to install unMenu. I stopped the array and clicked shutdown. After it shut down, I took the flash drive out and connected it to my Mac. Copied unMenu to the flash drive, plugged it back into the tower and booted it up. Now, when I access the main unRAID page through my web browser, both data disks show up, but the parity drive says Not Installed. I stopped the array, can see my other physical drive listed in the Devices page. Grabbed my syslog and came here. I'm using unRAID 4.4.2 Basic (3 drives). Here is my hardware setup: Motherboard -- GIGABYTE GA-MA74GM-S2 AM2+/AM2 AMD 740G Micro ATX AMD Motherboard - Retail CPU -- AMD Athlon 64 LE-1640 Lima 2.7GHz Socket AM2 45W Single-Core Processor Model ADH1640DPBOX - Retail RAM -- Transcend JETRAM 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model JM2GDDR2-8K - Retail Power Supply -- CORSAIR CMPSU-400CX 400W ATX12V V2.2 80 PLUS Certified Compatible with Core i7 Power Supply - Retail 1 x Hitachi 1TB HDT721010SLA360 SATA2 U300 72 2 x SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive - OEM Attached is the syslog I grabbed after it booted up saying "Not Installed" for the parity drive. I don't have an earlier syslog. The data on the array is still available on my external drive, so it's not the end of the world if I have to start over.
July 5, 200917 yr Hi all. Hopefully this is something simple, but I didn't want to mess anything up by tinkering with it. Yesterday I finished building my first unRAID build. Per some suggestions seen in other threads, I copied about 720GB of data to my array (some to each of two data disks) with no parity drive assigned. Once the data copied, I assigned the parity drive and let it do a parity sync (that was this morning). Everything seemed to be working fine since the parity sync until I decided to install unMenu. I stopped the array and clicked shutdown. After it shut down, I took the flash drive out and connected it to my Mac. Copied unMenu to the flash drive, plugged it back into the tower and booted it up. Now, when I access the main unRAID page through my web browser, both data disks show up, but the parity drive says Not Installed. I stopped the array, can see my other physical drive listed in the Devices page. Grabbed my syslog and came here. I'm using unRAID 4.4.2 Basic (3 drives). Here is my hardware setup: Motherboard -- GIGABYTE GA-MA74GM-S2 AM2+/AM2 AMD 740G Micro ATX AMD Motherboard - Retail CPU -- AMD Athlon 64 LE-1640 Lima 2.7GHz Socket AM2 45W Single-Core Processor Model ADH1640DPBOX - Retail RAM -- Transcend JETRAM 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model JM2GDDR2-8K - Retail Power Supply -- CORSAIR CMPSU-400CX 400W ATX12V V2.2 80 PLUS Certified Compatible with Core i7 Power Supply - Retail 1 x Hitachi 1TB HDT721010SLA360 SATA2 U300 72 2 x SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive - OEM Attached is the syslog I grabbed after it booted up saying "Not Installed" for the parity drive. I don't have an earlier syslog. The data on the array is still available on my external drive, so it's not the end of the world if I have to start over. Your data is fine, Your syslog seems to indicate that the parity drive has not been assigned. It is as if you did not cleanly shot down. unMENU is reporting what it is finding. If you were to go to the normal unRAID main page, what does it show? Did you switch cables around to the parity drive, or plug the USB drive into a different connector? Joe L.
July 5, 200917 yr Author I didn't move anything around internally, but it's possible I plugged the flash drive into a different slot in the back of the tower. Should I try shutting down, moving the flash drive to a different slot, and booting back up? Otherwise, if I simply assign my Hitachi drive to be the parity drive again, will it have to do another parity sync? Thank you, Joe.
July 5, 200917 yr I didn't move anything around internally, but it's possible I plugged the flash drive into a different slot in the back of the tower. Should I try shutting down, moving the flash drive to a different slot, and booting back up? Otherwise, if I simply assign my Hitachi drive to be the parity drive again, will it have to do another parity sync? Thank you, Joe. After you re-assign the parity drive, you can use the "Trust-My-Parity" process. I'd let it do the full parity check anyway, since apparently you've never done that yet.. See here in the wiki: http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Joe L.
July 5, 200917 yr Author After I copied my data to the data disks, I assigned the parity drive. At that point, it did a parity sync... took about 4.5 hours. Is there a different parity check I should do?
July 5, 200917 yr After I copied my data to the data disks, I assigned the parity drive. At that point, it did a parity sync... took about 4.5 hours. Is there a different parity check I should do? Yes. You "wrote" all the parity data to the parity drive, calculated by reading all the equivalent blocks on your data disks (doing what you called a parity-sync) Now, today's hard disks have built into them SMART firmware that will re-allocate disk blocks it cannot "read." So far, you've never "read" the blocks on the parity drive. Once you have initially calculated parity, you will want to periodically press the button on the user-interface to perform a "Parity Check" (most of us do it monthly) This will read every block from every disk. Any that cannot be read will be marked for re-allocation by the SMART firmware on the disk. If one of your data disks has a "read" error it will be written-to based on parity and the other data disks, thereby allowing the SMART firmware to re-allocate the disk block it was previously unable to read. (It will first try to re-write the original block, and if still unable to read it, will write to the new block from its stock of spare blocks) If the block that is unable to be read is on the parity drive, unRAID will re-write it, based on the data disks. Normally, you will never see any errors during this process of doing a parity "check", but you might see the re-allocated sectors increase on a disk. This is good, unless of course, the re-allocated sectors continue to increase on a disk over time. Then it is time for an RMA. There are no hard and fast rules for how many re-allocated sectors are "appropriate" Some will say none. Others will say it depends.. If initially detected, and then no change, and the number is small... odds are the drive will have a long life. So, initial parity calc is to allow you to reconstruct when a disk fails. (and eventually one will fail... it is only a matter of time) Subsequent parity check is to verify your disk's ability to read the disk platters and self-repair. I've only had one "parity" error in about 5 years on my array, and it was after a power hit (before I had a UPS) I've had up to 100 reallocated sectors on a disk. (and those have not changed in years) I do monthly parity checks. Joe L.
Archived
This topic is now archived and is closed to further replies.