Bug#275222: Successful installation
On Wednesday 06 October 2004 21:08, Hans van Zijst wrote:
> Couldn't find a way to make installer create RAID arrays and use one of
> them for LVM, so I did it myself. When I got to the point where I had
> to partition the disks, I fired up a terminal, created the RAID arrays,
> ran pvcreate, vgcreate and lvcreate and returned to the installer. The
> partitioner happily detected the RAID arrays and logical volumes I had
> just made, and everything installed just fine from there.
This is supported in the latest daily builds of the installer [1] and will
be supported in the next release.
[1] http://www.nl.debian.org/devel/debian-installer/
> At boot time, however, I get these messages (I installed 2 different
> machines and got the same messages while booting):
>
> devfs_mk_dev: could not append to parent for /disc
> devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to
> parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could
> not append to parent for /disc devfs_mk_dir: invalid
> argument.<4>devfs_mk_dev: could not append to parent for /disc
> devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to
> parent for /disc
>
> I get 129 of these ones... After that, I get these:
>
> VFS: Can't find ext3 filesystem on dev dm-0.
> VFS: Can't find ext2 filesystem on dev dm-0.
> VFS: Can't find ext3 filesystem on dev dm-0.
> VFS: Can't find ext2 filesystem on dev dm-0.
>
> ...which is correct, because I use JFS on my logical volumes (I don't
> like the idea of unmounting an active volume after a vgextend). Finally
> there's this bit:
Sorry, can't help you with these messages.
> cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[cut]
> shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
> shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
These messages are caused by hotplug trying to load modules that are not
supported by your hardware. You can get rid of them by blacklisting these
modules in /etc/hotplug/blacklist or by compiling a custom kernel.
Cheers,
FJP
Reply to: