Aurimas Mikalauskas wrote:
> After installing the base system, kernel install reports an error,
> that the kernel 'kernel-image-2.4.26-1-mckinley-smp' could not be
> installed and it says to check /var/log/messages for errors. That's
> what I found in the log:
>
> The following NEW packages will be installed:
> kernel-image-2.4.26-1-mckinley-smp
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0B/24.6MB of archives.
> After unpacking 72.0MB of additional disk space will be used.
> Selecting previously deselected package kernel-image-2.4.26-1-mckinley-smp.
> (Reading database ... 7316 files and directories currently installed.)
> Unpacking kernel-image-2.4.26-1-mckinley-smp (from .../kernel-image-2.4.26-1-mck
> inley-smp_2.4.26-2_ia64.deb) ...
> Setting up kernel-image-2.4.26-1-mckinley-smp (2.4.26-2) ...
> /usr/sbin/mkinitrd: device /dev/ida/c0d0p1 is not a block device
> Failed to create initrd image.
> dpkg: error processing kernel-image-2.4.26-1-mckinley-smp (--configure):
> subprocess post-installation script returned error exit status 9
> Errors were encountered while processing:
> kernel-image-2.4.26-1-mckinley-smp
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> And of course, the /dev/ida/c0d0p1 is not a block device, it doesn't
> even exist. The partition list looks like this:
>
> /dev/ida/disc0/part1 on /target type ext2 (rw)
> /dev/ida/disc0/part3 on /target/home type ext2 (rw)
> /dev/ida/disc0/part4 on /target/tmp type ext2 (rw)
> /dev/ida/disc0/part2 on /target/usr type ext2 (rw)
> /dev/ida/disc0/part5 on /target/var type ext2 (rw)
>
> but the /target/etc/fstab shows:
>
> /dev/ida/c0d0p1 / ext2 defaults,errors=remount-ro 0 1
> /dev/ida/c0d0p3 /home ext2 defaults 0 2
> /dev/ida/c0d0p4 /tmp ext2 defaults 0 2
> /dev/ida/c0d0p2 /usr ext2 defaults 0 2
> /dev/ida/c0d0p5 /var ext2 defaults 0 2
> /dev/ida/c0d0p6 none swap sw 0 0
>
> How come does the /target/etc/fstab look like this if there's no such
> directory /dev/ida not talking about the devices in it?
This seems to be a bug in debootstrap on ia64. On i386, we all get
/dev/ida directories, because debootstrap calls MAKEDEV ida when it's
built:
setarchdevs = $(if $(findstring $(ARCH),$(1)),$(2))
DEVS := generic hde hdf hdg hdh sde sdf sdg sdh scd-all initrd input usb md lp rtc \
$(call setarchdevs,i386,isdn-io eda edb sonycd mcd mcdx cdu535 \
optcd sjcd cm206cd gscd lmscd sbpcd \
aztcd bpcd dac960 ida fd0 fd1 ataraid cciss) \
$(call setarchdevs,sparc,hdc hdd busmice) \
$(call setarchdevs,m68k,fd0 fd1 adc add ade adf hdc hdd) \
$(call setarchdevs,powerpc,hdc hdd fd0 fd1 isdn-io m68k-mice)
I guess that the assumption was that compaq smart arrays were i386
specific, and they're not.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature