[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#265597: Alpha+DAC960: aboot installation failed



reassign 265597 aboot-installer
thanks

Hi Nathan,

On Fri, Aug 13, 2004 at 04:13:33PM -0500, Nathan Poznick wrote:
> Machine: AlphaServer 2100 4x275
> Processor: 2 x Alpha EV45 275mhz
> Memory: 512MB
> Root Device: HW RAID5 on DAC960 controller, /dev/rd/c0d0
> Root Size/partition table: (a=aboot, b=/boot, c=/, d=swap)
> 5 partitions:
> #       start       end      size     fstype   [fsize bsize   cpg]
>   a:        1*        1*        0*      ext2
>   b:        1*       39*       38*      ext2
>   c:       39*    14075*    14035*      ext2
>   d:    14075*    14319*      244*      swap

> Base System Installation Checklist:

> Initial boot worked:    [O]
> Configure network HW:   [O]
> Config network:         [O]
> Detect CD:              [O]
> Load installer modules: [O]
> Detect hard drives:     [O]
> Partition hard drives:  [O]
> Create file systems:    [O]
> Mount partitions:       [O]
> Install base system:    [O]
> Install boot loader:    [E]
> Reboot:                 [ ]
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

> Comments/Problems:

> Well things are getting far better than they used to be.  With the daily
> from 20040812, I was able to get all the way to the installation of the
> bootloader (aboot, since this is on an Alpha), which gave me this
> message:

> An installation step failed. You can try to run the failing item
> again from the menu, or skip it and choose something else. The
> failing step is: Install aboot on a hard disk

> I noticed that it appeared to be trying to install aboot to
> "/dev/rd/c0d0p".  If I remember swriteboot's usage, it should perhaps be
> using /dev/rd/c0d0.  Otherwise, it needs a partition number after the p.
> Syslog tells me,

> Jul  7 22:08:05 main-menu[258]: DEBUG: Menu item 'aboot-installer' selected
> Jul  7 22:08:05 main-menu[258]: DEBUG: configure aboot-installer, status: 2
> Jul  7 22:08:05 main-menu[258]: DEBUG: configure chroot, status: 0
> Jul  7 22:08:18 aboot-installer: info: Installing aboot on '/dev/rd/c0d0p'
> Jul  7 22:08:18 main-menu[258]: (process:5501): open disk device: No such file or directory
> Jul  7 22:08:18 main-menu[258]: WARNING **: Configuring 'aboot-installer' failed with error code 1
> Jul  7 22:08:18 main-menu[258]: WARNING **: Menu item 'aboot-installer' failed.

What a wonderful bug report to see -- this means makedev is fixed on
alpha for DAC960 support, and now aboot-installer just needs to be
updated to match. :)

I'll see if I can't squeeze some time in for fixing this over the
weekend.

> I chroot'd into /target and manually did an swriteboot / abootconf
> invocation:

> cd /boot
> swriteboot -f1 /dev/rd/c0d0 bootlx
> abootconf /dev/rd/c0d0 3 

> but then noticed that my /etc/aboot.conf wasn't going to be much help
> (not sure if this would have been corrected had the aboot installation
> completed, or not).  It was:

> 0:3/vmlinux.gz ro root=/dev/sda2
> 1:3/vmlinux.old.gz ro root=/dev/sda2
> 2:3/vmlinux.new.gz ro root=/dev/sda2
> 3:3/vmlinux ro root=/dev/sda2

Yes, aboot-installer fixes up the aboot.conf after it finishes
installing to the boot drive.

Cheers,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: