May 29, 201115 yr Hi guys, I recently moved my disks into a new server and when I did it flagged the parity drive as being wrong, or more specifically "Disk in parity slot is not biggest". Googling turned up a number of posts on the subject and while I never ran on 3.x the old system did have a Gigabyte mobo. I've been running on 4.5beta since I started so I figured I'd try a later version and see if it had better luck recognising the space but no such luck... in fact, the new version complained about one of the data disks for the same reason. So I've reverted to my 4.5beta config and I'm hoping you guys can help me. 1. Is there a simple way to make it redetect the parity drive size? I did try the restore option in 4.5 but it made all of the disk orbs flash blue. I then had no further options that I could see/it didnt look like it was doing anything? (so again, restored a backup of my pendrive and am back to square 1) 2. Is there any way I can start the array unprotected by a parity drive so that I can confirm I have a full copy of the files on the server elsewhere? If so, I'll happily wipe disks afterwards, no problem. I tried mounting and even reiserfsck but both complained about a bad superblock on each data disk. I've already got a copy of most/all of the data elsewhere so I'm not *completely* screwed if there's no resolution other than wiping everything - I just wont know what (if anything) I'm missing... until I need it and don't have it! Thanks.
May 29, 201115 yr Hi guys, I recently moved my disks into a new server and when I did it flagged the parity drive as being wrong, or more specifically "Disk in parity slot is not biggest". Googling turned up a number of posts on the subject and while I never ran on 3.x the old system did have a Gigabyte mobo. I've been running on 4.5beta since I started so I figured I'd try a later version and see if it had better luck recognising the space but no such luck... in fact, the new version complained about one of the data disks for the same reason. So I've reverted to my 4.5beta config and I'm hoping you guys can help me. 1. Is there a simple way to make it redetect the parity drive size? I did try the restore option in 4.5 but it made all of the disk orbs flash blue. I then had no further options that I could see/it didnt look like it was doing anything? (so again, restored a backup of my pendrive and am back to square 1) 2. Is there any way I can start the array unprotected by a parity drive so that I can confirm I have a full copy of the files on the server elsewhere? If so, I'll happily wipe disks afterwards, no problem. I tried mounting and even reiserfsck but both complained about a bad superblock on each data disk. I've already got a copy of most/all of the data elsewhere so I'm not *completely* screwed if there's no resolution other than wiping everything - I just wont know what (if anything) I'm missing... until I need it and don't have it! Thanks. # 1. Post a syslog. We are not psychic. #2. Look in the wiki at HPA, your old MB probably added an HPA and made the parity disk smaller. You need to remove it. You can probably do it using hdparm commands. Some however have had to use other utilities (Seatools, etc) As far as bad superblock, you are probably trying to check/mount the wrong partition. You will screw it up if you try to force build a superblock where one does not belong. The file systems are on the first partition of each disk, and you should be running reiserfsck on /dev/mdX devices to maintain parity, otherwise, you are introducing parity errors by running it on the /dev/sdX1 devices. Joe L.
May 30, 201115 yr Author I'll give (2) a go ASAP but it'll likely be a few days before I'm back near the box. I'll update the thread with the result/syslog at that point. Thanks for the reply Joe.
June 3, 201115 yr Author Thanks a lot Joe - there were two HPA disks, though one was loading without issue. After fixing the first (with HDPARM) I could start the array and verify I had all my files. After fixing the second the array refuses to start - but that's okay since I'd like to refresh it/clean the server out. With that in mind is there a process to reset the disks/array to scratch? I can't seem to find a 'how to lose all your data on purpose' type guide on google Thanks again for all your help!
June 3, 201115 yr http://tower/Utils then "new config". That should erase your unraid configuration and let you start over.
June 3, 201115 yr http://tower/Utils then "new config". That should erase your unraid configuration and let you start over. That will not erase the data on the disks, but it will immediately invalidate parity and set a new disk configuration based on the assigned disks.
June 3, 201115 yr Author Thanks for the quick replies guys. Navigating to /Utils, /utils or /utils.htm all give me a blank page. None of the screens that I can access via links seem to have a 'new config' section/button/similar (there's no 'new' anything in fact). This is running on 4.7.
June 3, 201115 yr Thanks for the quick replies guys. Navigating to /Utils, /utils or /utils.htm all give me a blank page. None of the screens that I can access via links seem to have a 'new config' section/button/similar (there's no 'new' anything in fact). This is running on 4.7. you are correct. There is no such page in 4.7. On 4.7 you must stop the array and THEN log in as "root" on either the system console, or via telnet and type: initconfig Respond to its prompt with Yes (capital "Y" lower case "es")
June 3, 201115 yr Author Since I'm starting anew, would you recommend jumping to the 5.0 beta or just sticking with 4.7? Thanks again Joe.
June 3, 201115 yr Oops. sorry. yes, i forgot that was a 5.X thing. as far as 4.7 vs 5beta. I would stick with 4.7 unless you need a feature or hardware support that is only in 5.x
June 4, 201115 yr Author Excellent - it's rebuilding, the data is still available too. For those reading this thread at a later date - the HDPARM command worked perfectly on 4.5 but on 4.7 it complained about the disks. I ran it on 4.5 then upgraded to 4.7 and it's happily working with my disks. It's an easy and quick process, the longest part of course being the rebuild of parity. I really can't thank you guys enough for all of your help on this. Thanks again!
Archived
This topic is now archived and is closed to further replies.