September 3, 201213 yr Hi, all. Following the steps here: http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta_Release_Notes At this point: Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly except for the Cache disk. If you previously had a Cache disk assigned, you will need to re-assign it manually and re-apply any unique configuration settings for it. I'm seeing an error: disk2 Wrong ST31500341AS_9VS0E8QB I'm unsure as to why it is reading as wrong. The SN is the same. I am attaching a screenshot of before and after. Before: After: SysLog: https://dl.dropbox.com/u/1233738/SysLog.txt Please advise. Thanks.
September 3, 201213 yr it is being detected as a different size. (and therefore,unRAID considers it a different disk) You have an HPA to deal with. Sep 3 16:32:43 Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Sep 3 16:32:43 Tower kernel: ata6.00: HPA detected: current 2930275055, native 2930277168
September 3, 201213 yr Author it is being detected as a different size. (and therefore,unRAID considers it a different disk) You have an HPA to deal with. Sep 3 16:32:43 Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Sep 3 16:32:43 Tower kernel: ata6.00: HPA detected: current 2930275055, native 2930277168 Thank you, Joe. I'm sorry, where can I find out what an HPA is and how to deal with it? Thanks. EDIT: I found this link - http://lime-technology.com/wiki/index.php/UnRAID_Topical_Index#HPA But I think I'm getting in over my head.
September 3, 201213 yr it is being detected as a different size. (and therefore,unRAID considers it a different disk) You have an HPA to deal with. Sep 3 16:32:43 Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Sep 3 16:32:43 Tower kernel: ata6.00: HPA detected: current 2930275055, native 2930277168 Thank you, Joe. I'm sorry, where can I find out what an HPA is and how to deal with it? Thanks. EDIT: I found this link - http://lime-technology.com/wiki/index.php/UnRAID_Topical_Index#HPA But I think I'm getting in over my head. Stop the array,then login via telnet and type: hdparm -N p2930277168 /dev/sdc That will probably remove the HPA since it seems your disk controller is able to read the true size. Type hdparm -N /dev/sdc to confirm the size. You can then reboot the server and see if the HPA warning in the syslog is gone. If it is gone, then click on the I'm sure checkbox under "Start" and let unRAID reconstruct the drive's contents onto itself. Joe L.
September 3, 201213 yr Author Stop the array,then login via telnet and type: hdparm -N p2930277168 /dev/sdc That will probably remove the HPA since it seems your disk controller is able to read the true size. Type hdparm -N /dev/sdc to confirm the size. You can then reboot the server and see if the HPA warning in the syslog is gone. If it is gone, then click on the I'm sure checkbox under "Start" and let unRAID reconstruct the drive's contents onto itself. Joe L. I think that's got it. Here's the new syslog. https://dl.dropbox.com/u/1233738/NewSysLog.txt I'm not seeing HPA in there anywhere. I think it's safe to start the array?
September 3, 201213 yr I'm not seeing HPA in there anywhere. I think it's safe to start the array? yes. me too.
September 3, 201213 yr Author I'm not seeing HPA in there anywhere. I think it's safe to start the array? yes. me too. Okie dokie. Fired up and I'm now seeing: Do I now need to click on "Rebuild" or just let it proceed on it's own?
September 3, 201213 yr I think you need to let it re-construct the disk. (basically, it thinks the disk is a replacement for the one that was in there, since the size changed) Since the array is started, you should be able to see the contents of disk2. (simulated from parity and the other data disk) Click on "Rebuild" and it should start writing to disk2, reading from the others. Let it complete.
September 3, 201213 yr Author Wonderful! It's got an estimated rebuild time of 6.5 hours. Thank you so much for your guidance on this.
September 3, 201213 yr Wonderful! It's got an estimated rebuild time of 6.5 hours. Thank you so much for your guidance on this. I'm hoping the disk had been used on another system with a Gigabyte motherboard. It added the HPA. If you are still using the Gigabyte motherboard you need to disable the "feature" that copies the BIOS to an HPA. Otherwise, it will create one again and trash one of your disks. Read the links in the wiki for details. Joe L.
September 3, 201213 yr Author I'm hoping the disk had been used on another system with a Gigabyte motherboard. It added the HPA. If you are still using the Gigabyte motherboard you need to disable the "feature" that copies the BIOS to an HPA. Otherwise, it will create one again and trash one of your disks. Read the links in the wiki for details. I'm fairly certain that's what happened. It's currently in a system with an ASUS board (P4P800 I believe). I goofed around in the BIOS a bit after trying to learn a bit more through the breadcrumbs you provided at the start. This is only for another 2-3 days at most before my new system is finished all it's testing and the new 3TB parity arrives.
Archived
This topic is now archived and is closed to further replies.