Joshua Murphy schreef: > On 4/2/07, Fred Verschueren <[EMAIL PROTECTED]> wrote: > >> hello, >> >> I'm rather new to Linux although not a novice. >> To increase my knowledge of Linux I try to make my own system from >> scratch by following the book Cross Compiled Linux from Scratch Version >> 1.0.0-x86_64-Multilib. >> At the moment I'm on item 7.21 where I need to boot Linux. >> And here I have in fact two problems: >> 1. I have a problem during boot which resulted in the error " superblock >> could not be read ...." and the PC powerts off. But I think something >> went wrong before. >> 2. And my second problem is that all relevant messeges are running off >> the screen. >> >> My question: how can I catch these message ??? so I can have a look in >> the problem and try to solve it myself. >> >> Thanks in advance. >> Fred. >> > > Scroll Lock may help with #2 ... > > As for #1: How far does the system get before presenting that? Does > the BIOS pass control off to the boot loader (Grub, in this case)? > Does Grub load the kernel? Does the kernel make it to starting INIT? > > Thans for thast response.
#2 Scroll lock doesn't help --> no response #1. System starts booting but it's difficult to say what's happening because of #2 but --> my disks are recognised and attached and what I can see on the screen when the scrolling stops is the following =============== starting udevd udevd[585] init_udevd_sochet: error getting socket: address family not supported by protocol udevd[585]:main:error initializing udevd socket:illigal seek performing Cold plugging mkdir:cannot create dir /dev/.udev:read only file system mounting root file system in read only mode checking file systems ... /dev/sda14 The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and it really contains an ext2 file system ( 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 8192 <device> FAILURE File system errors were encountered that could not be fixed auromatically. This system cannot continue to boot and will therefore be halted until those errors are fixed by a System Administrator. After you press Enter this system will be halted and powerd off. Press enter to continue .... ===================== When I after this boot in my home systen (SUSE 10.2) I can mount /dev/sda14 on /mnt/clfs without any problem and all the files I created before are still there and accessible. I can mount and unmount /dev/sda14 at will without problem. If you can give me some more hints I would appreciate it very much. Thanks in advance. Fred. _______________________________________________ Clfs-support mailing list Clfs-support@lists.cross-lfs.org http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
