On Mon, 2004-07-26 at 00:32, Steve Langasek wrote: > The second of these warnings should be addressed in partman-auto 27, > included on today's CD images, which creates a separate ext2 /boot > partition on alpha.
Partitioning seems to be going OK now...somewhat. But let me start at the beginning. I finally got around to trying D-I on alpha again, so I downloaded the latest netinst ISO to try both the installer and to check if the kernel would panic on me again (it didn't!). The installer version at that time: 20040806. Popping in the CD, and booting it goes all well. Autopartitioning on /dev/sdb works like charm too (aboot headroom, and /boot on ext2, no errors, no warnings), and even all the packages install...until it's time to install aboot. Tracking the aboot install yields a nice error message on TTY1, and the following in syslog: aboot-installer: info: Installing aboot on '/dev/sdb' main-menu[275]: (process:11725): error: bootcode overlaps with partition #9. If you really want this, use -f9 main-menu[275]: WARNING **: Configuring 'aboot-installer' failed with error code 1 Partition table: # fdisk -ul /dev/scsi/host0/bus0/target8/lun0/disc Disk /dev/scsi/host0/bus0/target8/lun0/disc: 4550 MB, 4550934016 bytes 255 heads, 63 sectors/track, 553 cylinders, total 8888543 sectors Units = sectors of 1 * 512 = 512 bytes 9 partitions: # start end size fstype [fsize bsize cpg] a: 1 1954 1954 ext2 b: 1955 158205 156251 ext2 c: 158206 451174 292969 ext2 d: 451175 3666018 3214844 ext2 e: 3666019 5101565 1435547 ext2 f: 5101566 5355472 253907 ext2 g: 5355473 8398441 3042969 ext2 h: 8398442 8888542 490101 swap i: 4294967295 8589934589 4294967295 ff Looking at that partition table, I notice partition "i" to look odd. To be honest, I have no idea what partition #9 is. My guess is that it's "i", and it's weird size is messing up aboot-installer's intelligence. But that's just my guess, maybe you have a better one? :-) > BTW, have you had any further problems with kernel panics from CDs? If > not, it may be that the disk didn't burn right, or that SRM was in an > inconsistent state. Nope, no panics this time. As to the cause I can only guess. I tried several times with the same CD, and it paniced at different points in the installation. Even after a few cold reboots, etc. Oh well, all seems well in the kernel area now, so one less worry. Thanks. -- Regards, Ferdinand O. Tempel Your friendly neighborhood linuxops.net administrator. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
