November 3, 20178 yr Hello All, First time posting, after a few problems I have had - I can't locate the post I am looking for to help but I hope you guys can help... I haven't used my unRAID in ages (over a year) and it has gone a little pear shaped. First I changed house and changed my static address and it then wouldn't boot the program as the VGA/bios ended up saying "hostname lookup failure"?? even when I changed it to DHCP in network.cfg It would not create an IP and would go to HP Login: (in dos) as it's a HP machine? KEY PART... So I wiped my USB and started again and then when I got into /Tower I had to assign the array devices and as it had been so long I had forgotten which one was the parity drive??? is there a way I can tell?? Then I just assigned them all to normal drives leaving the Parity Unassigned... One of my drives won't mount as it said "Unmountable - No file system (32)" - is that the parity drive or is it a dead drive? Now I can't assign a drive to the Parity as it says it will WIPE the drives data.. Have I gone down a unfixable path??? Please help and put my worry to bed. Thanks in advance. Russ
November 3, 20178 yr Community Expert 8 minutes ago, rustywood said: One of my drives won't mount as it said "Unmountable - No file system (32)" - is that the parity drive or is it a dead drive? Likely that is parity but to be sure assign all disks as data disks, leave parity unassigned, start the array and if there's only one unmountable disk it's your parity, if there are more post your diagnostics.
November 3, 20178 yr Author Hi Johnnie, thanks for the reply, I have done this and only one drive that came up with "Unmountable - No file system (32)" So I suppose is 100% the Parity! Is it OK to reassign it to Parity and wipe the disk? I hope it's not got any important data on it.. but as raids work like this I feel like it's a stupid question. So after that I need to wipe the disk and rebuild the parity? is that correct?
November 3, 20178 yr Community Expert Do another new config, now assign all data disks plus parity and before starting the array check "parity is already valid", start the array and run a parity check, a few sync errors are normal after doing this.
Archived
This topic is now archived and is closed to further replies.