Nils Olav Fossum schrieb: > torsdag 15. juni 2006, 13:42, skrev Falko Trojahn: >> Nils Olav Fossum schrieb: >>> onsdag 14. juni 2006, 17:38, skrev Peter Huber: >>>>> this will do only on blank drives, and according to this >>>>> http://lists.gnu.org/archive/html/bug-parted/2004-07/msg00030.html >>>> as I see here, parted uses /proc/ide/hda/settings to overwrite the >>>> values returned by HDIO_GETGEO. >>> My understanding: >>> ..and this is what parted uses to set the geometry when there is a blank >>> disk. >>> >>> So now I wonder what would happen if we do not blank the drive..?? >>> ..will parted read geometry from the drive??.. >> Yes. This seems to be the main problem, since any former software could >> have formatted the disk it's way. According to Patrick, parted uses the >> partition table to get some informations. > > Or, we can use whats already on disk (as parted do?) > if no /proc/ide/$sys_hda/settings file = do not erase disk before we run > parted. > (im trying to find where the first erasing is done in the script..) It depends on the way you are doing the formatting and what is in fdisk_cmds. Look for "#Partition the disk" in install.pl. Usually - as stated in the documentation on http://unattended.sourceforge.net/meta.php - you have a fdisk_cmds line in your setup like this: fdisk_cmds="fdisk /clear 1;fdisk /pri:4000;fdisk /activate:1" which only deletes partition no. 1, but perhaps not the whole partition table.
I'm doing it this way http://www.mail-archive.com/unattended-info@lists.sourceforge.net/msg04840.html so fdisk to parted conversion under linux is out of the way. In my partition_cmds variable you see "parted mklabel msdos" which according to http://www.gnu.org/software/parted/manual/html_chapter/parted_toc.html#TOC16 means erasing all partitions from the partition table. > >> What we could do here is getting an bootsector from this manual install on >> this specific device, save it then - having booted Knoppix or other live CD >> - eg. with dd if=/dev/sda of=mybootsec count=1 >> and put this file to /z/site/mybootsec >> >> When installing with unattended, throw it with >> dd if=/z/site/mybootsec of=/dev/sda >> on the disk before parted is first time started (you know, it's the same as >> erasing all data on the disk, so be careful). > > or, is it possible to 'patch' mbr' direct on disk? > If you know what's the real reason for the problem with the thinkpads ... Best regards, Falko _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
