March 8, 201115 yr So I started my unRaid a couple weeks back with just 1 HDD. Over the weekend I pre-cleared 2 new WD20EARS drives and today I tried to add them to the array. Both disks pre-cleared with 0 problems and the smart reports for both looked clean. I have about 500g of BluRay ISOs on the first disk already before adding these two new drives. After assigning these two new drives, the one assigned to as parity shows a blue ball and unMenu Array Management shows "PARITY NOT VALID: DISK_DSBL_NEW." What does the blue ball mean, and how do I know if my parity drive is working?
March 8, 201115 yr Author Nevermind. I got it to start parity sync. I'm not sure what happened the first time, but it unRaid didn't do a parity sync the first time I started the array with the new drives assigned. I just brought the array down and reassigned the drives and this time, unRaid asked to do a parity sync. All is good. I'd still like to know why unRaid didn't do the sync the first time though. Weird...
March 8, 201115 yr What did you do when you added the disks? Did you just assign them and then try to start or did you use the "initconfig" command? Next time, a syslog taken while the server is having an issue can help others actually troubleshoot what happened instead of guessing. Peter
March 8, 201115 yr Author I assigned the disks, formatted the data disk, and then started the array all from the WebGui. After formatting, I wasn't given the check box to perform a parity sync so I just started the array normally. I was actually more curious about what the blue ball represents than anything. I was guessing the blue ball meant the disk either wasn't configured probably, or frozen (blue = ice = frozen?). I'll definitely post a syslog the next time something weird happens.
March 8, 201115 yr unRAID does not do a parity sync when you add new disks to an existing array. You indicated you had a valid array with 1 data disk. Then, you indicate that you added 2 new disks. unRAID should not have made the parity blue ball or required a parity sync to add the new disks to the existing array. The blue ball is unconfigured or not yet a valid array. Peter
March 8, 201115 yr Author I started with 1 data disk and no parity disk when I first built the machine a couple weeks ago. Yesterday, I added the parity and the second data disk. Shouldn't unRaid perform a parity sync if a new parity disk is being added?
March 8, 201115 yr I started with 1 data disk and no parity disk when I first built the machine a couple weeks ago. Yesterday, I added the parity and the second data disk. Shouldn't unRaid perform a parity sync if a new parity disk is being added? yes, it should. What version of unRAID are you running??
March 8, 201115 yr OK, I didn't realize one of the new disks was the parity. Yes, it should have done the parity sync when you started the array. I have a funny feeling adding the new data disk and the new parity disk at the same time messed it up. You could have also pressed the parity check button and it would have fixed up the parity. You'd see a lot of errors but they aren't really errors since it's creating the parity the first time. And as Joe posted, tell us the version of unRAID. Peter
March 9, 201115 yr Author Quote from: Joe L. on March 08, 2011, 01:30:36 PM Quote from: yelnatsch517 on March 08, 2011, 01:24:59 PM I started with 1 data disk and no parity disk when I first built the machine a couple weeks ago. Yesterday, I added the parity and the second data disk. Shouldn't unRaid perform a parity sync if a new parity disk is being added? yes, it should. What version of unRAID are you running?? I'm running unRaid 4.7 since I built the server just a couple weeks ago. Quote from: lionelhutz on March 08, 2011, 02:39:25 PM OK, I didn't realize one of the new disks was the parity. Yes, it should have done the parity sync when you started the array. I have a funny feeling adding the new data disk and the new parity disk at the same time messed it up. You could have also pressed the parity check button and it would have fixed up the parity. You'd see a lot of errors but they aren't really errors since it's creating the parity the first time. And as Joe posted, tell us the version of unRAID. Peter Actually without a parity drive configured properly, the check parity button wasn't even there. It was incredibly weird to say the least. I assigned the drives, and started the array up just as if the parity drive was never assigned, except the devices tab clearly showed a disk assigned to parity and the main tab showed a blue ball next to the parity disk. I performed short smart tests on both tests and both looked fine. I forgot to mention that this was through unMenu's unRaid Main Tab; not sure how that would make a difference though. Parity sync is now finished and everything is up and running properly. Except for that weird hiccup, everything was smooth. I swear I always have the worst/best luck with everything. Worst on the receiving end, best if I'm a beta tester. I always seem to find that one tiny exception nobody else encounters. Undecided
March 9, 201115 yr Except for that weird hiccup, everything was smooth. I swear I always have the worst/best luck with everything. Worst on the receiving end, best if I'm a beta tester. I always seem to find that one tiny exception nobody else encounters. +1 know exactly how you feel...
March 9, 201115 yr Starting the array through the unRAID "Main" screen accessed through the window in unMENU should not have had any effect. It should have started the initial parity sync. Joe L.
Archived
This topic is now archived and is closed to further replies.