Torsdag 17 april 2008 23:42, skrev Jens Geile: > > > ... > > > "Odd. C/H/S does not multiply out to 312581808" > > > ... > > > "* We have fix_disk_geo_heads (78), writing into /dev/dsk1" > > > "* We have fix_disk_geo_sectors (60), writing into /dev/dsk1"
> > > "Legacy BIOS says 78 heads and 60 sectors." The hdd is a 160gb sata > > > drive > > > > Does not look right.. > > The only values I can remember that I have seen on a modern system: > > heads: 255 and 240 > > sectors: 63 > > Googling a bit revealed this: > http://www.mail-archive.com/[EMAIL PROTECTED]/msg02058.html Maybe Mario > can give us some info. This is exactly (well, more or less) what we try to fix with "fix_disk_geo_heads" and "fix_disk_geo_sectors". If they are set to some values, these values will be written into byte 26 and 24 on the actual partition. The reason is that parted do not always set disk geo right for the old windows installer. Yes, its the windows installer that is shitty here! > Wait ... I thought we weren't supposed to use "fix_disk_geo_heads" and > "fix_disk_geo_sectors" if we wanted nt5xinstall to take care of fixing > "random features"?! Or did I misunderstand what's written on > http://ubertechnique.com/unattended/nt5xinstall ? So which is it? Should i > set those two options to make nt5x-install do the magic or should i not? It depends.., it gives you two more knobs you can tweak. So to clarify a bit more the two settings we have: by default fix_disk_geo_heads and fix_disk_geo_sectors will be set to the values from 'legacy' BIOS and written into the 'active' partition, at byte position 24 and 26 In most cases that will work. In fact I have not seen a machine where it wont work. Obviously some of you have :-) We get the values from the kernel edd module and set the environment variables 'LEGACY_BIOS_HEAD' and 'LEGACY_BIOS_SECT' in the 'master' script at boot after the 'z' share is mounted. These environment variables are then picked up by install.pl. install.pl will only put the value from LEGACY_BIOS_HEAD into fix_disk_geo_heads if fix_disk_geo_heads is NOT set, ie: not defined in unattend.txt. Same goes for LEGACY_BIOS_SECT and fix_disk_geo_sectors. Examples: Do not fix disk geometry, use what parted believe it should be: fix_disk_geo_heads = "" fix_disk_geo_sectors = "" - ie: nothing to write into the partition, keeping whats there. - note: set to (or define) empty strings What most systems like: fix_disk_geo_heads = "255" fix_disk_geo_sectors = "63" - 'emulate' parted 1.6.22 (well, close enough, I suppose) Thinkpads and some older Compaq P3,P4 PATA systems: fix_disk_geo_heads = "240" fix_disk_geo_sectors = "63" - because we know what it should be 'Unset' previous unattend.txt settings, use 'legacy' bios settings: fix_disk_geo_heads = fix_disk_geo_sectors = - use the automagic again If this is useful, i will update the wiki :-) > > Oh believe me, I know your pain ... Try writing unattended installation > scripts for a couple dozen retarded learning softwares (primary school > stuff)... THAT's pure horror. -.- There is less than zero documentation. hehe, Im working in the same sector, makes me wonder about those strange people writing it.. :-D ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
