Frans Pop wrote:
Package: yaird
Version: 0.0.12-3
Severity: important
After a new installation on hppa, the system seemed to boot correctly, but
failed to
mount /boot and /home directories. Also the eth0 network interface was not
brought
up automatically.
If I create the initrd using initramfs-tools these problems do not occur.
The reason /boot and /home are not mounted is that /dev/sd* is not present.
This seems to indicate a problem with udev, which would also explain eth0 not coming
up as it needs to be "hotplug detected".
Full log attached. Here are some relevant pieces with comments.
[...]
udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No
buffer space available
mmm, yes I encountered the same pb with a recent smp kernel (iirc
2.6.16-rc2...) and udev.
but not with a up kernel.
<!-- not sure about this message, but the same is shown for initramfs-tools -->
I don't (want to) use initramfs (not enough clue to rebuild it :\ )
[...]
Waiting for /dev to be fully populated...hda: CD-532E-B, ATAPI CD/DVD-ROM drive
<!-- Hmm. Looks like things have not really been waiting... -->
[...]
Checking all file systems.
[/sbin/fsck.ext2 (1) -- /boot] fsck.ext2 -a -C0 /dev/sda2
fsck.ext2: No such file or directory while trying to open /dev/sda2
/dev/sda2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a -C0 /dev/sda7
fsck.ext3: No such file or directory while trying to open /dev/sda7
/dev/sda7:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck died with exit status 8
File system check failed.
A log is being saved in /var/log/fsck/checkfs if that location is writable.
Please repair the file system manually.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and resume system boot.
Give root password for maintenance
(or type Control-D to continue):
The same here.
Sorry to not being of more help but I don't yet found time to debug
more this other udev pb with smp kernel ;<(
Joel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
