first boot

dracayr · 06-01-2008, 09:46 AM

hi,

I (almost) finished the book, all that remains is booting. When I try to boot the LFS, it sais:

fsck.ext3:no such file or directory while trying to open /dev/sda5

so I thought I could copy the device files from the host System. The problem is, I have

Code:

dd if=/dev/sda of=$LFS/dev/sda

running for over an hour now, and nothing happens, except that conky monitors a high disk io. Is there another possibility to obtain the device files?

dracayr

pixellany · 06-01-2008, 09:51 AM

That command does not look like it is copying device files.....It is copying the entire contents of /dev/sda to $LFS/dev/sda. Without knowing the contents of the variable $LFS, it's hard to know exactly what is happening.

dracayr · 06-01-2008, 10:21 AM

the command has terminated now (and it did copy the file). I am repeating the procedure now with the rest of the sda's

As this is the linux from scratch forum, $LFS is the path to the partition where the lfs is built

Edit: I guess you were right. /dev/sda worked fine, but when I try /dev/sda5, my partition slowly fills itself. But how do I get the files then?

dracayr

pixellany · 06-02-2008, 07:03 AM

I am not clear on what you are trying to do. Your original post included this error message:

Quote:

fsck.ext3:no such file or directory while trying to open /dev/sda5

That would not be fixed by copying files from the /dev directory.

Where in the boot sequence did you get this message?

dracayr · 06-02-2008, 07:26 AM

I'm on a different computer right now, but I'll say as much as I remember. This is about what I can see when the error occurs (before it goes too fast to read):

EDIT: Ok, changed it now to the actual values

Code:

setting the console log-level to 7	[OK]
populating /dev with device nodes	[OK]
Activating al swap files/partitions
swapon: cannot stat /dev/sda2:no such file or direcory	[fail]
Setting system clock			[OK]
mounting root file System in read only mode	[OK]
checking file system
fsck.ext3:no such file or directory while trying to open /dev/sda5	[fail]
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>

failure: ...

that's quite strange because it says it mounted the root filesystems, but not sda5. Yet sda5 IS my root fs

dracayr