i have just moved from 4.6-rc2 to 4.7

all was well before the upgrade (only copied bzimage,bzroot and memtest) and have not changed ANY hardware or bios settings etc.

just a reboot and i get disk too small error

i have attached my syslog and a screenshot..

not sure what too do

please help.

syslog-2011-01-26.txt

Your problem is that you have HPA on that drive now:

Jan 26 17:01:54 Terok-Nor kernel: ata1.03: HPA detected: current 1953523055, native 1953525168
Jan 26 17:01:54 Terok-Nor kernel: ata1.03: ATA-7: SAMSUNG HD103SI, 1AG01118, max UDMA7
Jan 26 17:01:54 Terok-Nor kernel: ata1.03: 1953523055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
Jan 26 17:01:54 Terok-Nor kernel: ata1.03: configured for UDMA/133

 

I am going to assume you have a Gigabyte motherboard.  It just tried to "help" you by saving a copy of your BIOS settings to a hard drive... which happened to be in your array.

 

You need to first disable HPA in your BIOS and ALSO check for a BIOS update for your board so that HPA is disabled by default.  If it is not it is only a matter of time before this happens again.

 

Directions for removing the HPA are here.  You would use sde instead of sdf.

One of your disks has an HPA  (Host protected area)

Jan 26 17:01:54 Terok-Nor kernel: ata1.03: HPA detected: current 1953523055, native 1953525168

Jan 26 17:01:54 Terok-Nor kernel: ata1.03: ATA-7: SAMSUNG HD103SI, 1AG01118, max UDMA7

Jan 26 17:01:54 Terok-Nor kernel: ata1.03: 1953523055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

 

See this post, and the one following for instructions on how to remove it.

http://lime-technology.com/forum/index.php?topic=10483.msg99685#msg99685

 

You'll also need to disable the Gigabyte BIOS "feature" that creates it... Otherwise, it will just create it again and possibly clobber data stored on a disk.

 

The command for you will be:

To see the current setting:

hdparm -N /dev/sde

 

To permanently change the HPA

hdparm -N p1953525168 /dev/sde

 

To see if it was changed.

hdparm -N /dev/sde

 

Joe L.

 

i want to say thanks all for the very quick responses but i just copied back my old bzimage and root etc.

and the array is working fine and i will attempt to correct this other problem on the weekend, is there any chance of data loss following those instructions?

 

thanks

i want to say thanks all for the very quick responses but i just copied back my old bzimage and root etc.

and the array is working fine and i will attempt to correct this other problem on the weekend, is there any chance of data loss following those instructions?

 

thanks

Not much risk.  The disk will be detected as a different disk, and will be re-constructed as if it is a new disk replacing the old.  If your other disks are working properly, not much risk.  If your other disks are not, there is risk.

 

You have the exact same risk if you have a disk fail.  In this case though you are re-writing exactly what is there already for 99.9999% of the drive. 

 

Joe L.

thanks for the help once again JoeL

will try that on the weekend, to busy building me new pc... 

Hi there Joe, prostuff i have FINALLY got around to upgrading my unRAID software and i was busy following the instructions to disable the BIOS settings but i notice i actually have a intel motherboard... what now??

 

there is no setting for the HPA.

 

thanks

 

 

The subject drive was at one time used in a Gigabyte MB. That is when the HPA was created. Once you remove it it will be gone for good. The Intel MB will not recreate it.

thanks for the answer,

still need input... when  i run the command that JoeL said which is "hdparm -N /dev/sde" i get the following reply.. "/dev/sde:

max sectors   = 1953523055/7368112, HPA setting seems invalid" is there something wrong.. what should i see here ?  i have not done any other commands as i am VERY scared of data loss and i have a good working array.

 

 

thanks

 

 

ran the command JoeL posted a few posts up and now it's doing a rebuild.. (finger crossed, then i can upgrade to 4.7.. thanks JoeL)

 

 

just for info sake all went very smooth JoeL's commands worked fine no data loss and running v4.7... thanks to all involved.

 

(just interesting to note that all the disks i have came shrink wrapped and the fact that they have been ONLY in this machine is wierd that the hdd was in another machine at one stage..!!!)