[Solved] Upgrade From 4.7 to 5.0-rc3 Two Or More Disks Are Wrong

[twitch123]

Hey everyone,

 

Hoping someone can give me a hand here, I ran a parity check last night on 4.7 and upgraded to 5.0-rc3 today.  I stopped the array, did a power down on the pc.  Moved the flash drive to another pc and replaced bzroot and bzimage on the flash drive overwriting the two that were already there.

 

When I start up I'm getting this error message:

 

 

Attached is the syslog.

 

The disks seem to be in the correct place, this is what I copied to notepad from the devices tab in 4.7 before I upgraded:

 

parity device: pci-0000:00:11.0-scsi-2:0:0:0 host3 (sdc) WDC_WD15EADS-00P8B0_WD-WMAVU0931463

disk1 device: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD10EADS-00L5B1_WD-WCAU45178405

disk2 device: pci-0000:00:11.0-scsi-1:0:0:0 host2 (sdb) WDC_WD10EADS-00L5B1_WD-WCAU45177770

disk3 device: pci-0000:00:11.0-scsi-3:0:0:0 host4 (sdd) WDC_WD15EADS-00P8B0_WD-WMAVU1030189

disk4 device: pci-0000:00:14.1-ide-1:0 ide1 (hdc) WDC_WD10EADS-00L5B1_WD-WCAU45405441

disk5 device: unassigned

cache device: unassigned

 

Can someone point me in the right direction?  Thanks.

 

Edit:  The reason I'm updating is I'm running out of room and need to add new disks, I'm generally a 'if it's working, don't mess with it' kinda guy.  (For these reasons.)

newsys.txt

[Joe L.]

Those disks have HPAs

 

You'll need to deal with them (remove the HPAs) while on the 4.7 release,   

(doing one disk at a time and re-constructing to it one its HPA is removed)

or, you can stay on the 5.0rc3 release and just set a new disk config and re-calculate parity.

 

May 15 20:10:06 Tower kernel: ata2.00: HPA detected: current 1953523055, native 1953525168

May 15 20:10:06 Tower kernel: ata2.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133

May 15 20:10:06 Tower kernel: ata2.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

May 15 20:10:06 Tower kernel: ata1.00: HPA detected: current 1953523055, native 1953525168

May 15 20:10:06 Tower kernel: ata1.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133

May 15 20:10:06 Tower kernel: ata1.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

 

[twitch123]

 

or, you can stay on the 5.0rc3 release and just set a new disk config and re-calculate parity.

 

If I just want to go ahead and leave those disks as is can I just check off the checkbox and start the array like it's suggesting there.  "Start will just record the new disk positions and bring the array on-line. We recommend you start a Parity-Check afterwards just to be safe."

 

Obviously I don't want to lose my data in this and in my drive upgrades I can replace those HPA disks that way over the next few days.

 

Thanks

 

Edit: I tried the above and it seems to have worked, not sure why those two disks would have had HPA on them, but as I upgrade disks here I'll work on replacing them.  As it stands I can access everything and all seems right with the world.  Thanks!

[mbryanr]

Here is some more info on HPA

http://lime-technology.com/forum/index.php?topic=10866.0