unforseen error in /etc/rc.d/rcsysinit.d/S40mountfs!!!!!!

Nathan Coulson conathan at conet.dyndns.org
Mon Mar 1 19:09:10 PST 2004


> Nathan Coulson wrote:
>>>so my /etc/fstab looks like this:
>>>
>>>#begin /etc/fstab
>>>
>>># filesystem  mount-point    fs-type  options         dump   fsck-order
>>>
>>>/dev/hdb1     /              ext2     defaults        1      1
>>>/dev/hdb2     swap           swap     pri=1           0      0
>>>proc          /proc          proc     defaults        0      0
>>>devpts        /dev/pts       devpts   gid=4,mode=620  0      0
>>>shm           /dev/shm       tmpfs    defaults        0      0
>>>#usbfs         /proc/bus/usb  usbfs    defaults        0      0
>>>
>>>#end /etc/fstab
>>>
>>>i set the fs-type to ext2, should i follow the books example and set
>>>reiserfs???
>>>
>>>
>>>and the partiton skeme:(i hope u have mean that, couse i'm not sure if
>>>there is a diffrence betwen a skeme and table)
>>>
>>>
>>>Disk /dev/hdb: 255 heads, 63 sectors, 4865 cylinders
>>>Units = cylinders of 16065 * 512 bytes
>>>
>>>    Device Boot    Start       End    Blocks   Id  System
>>>/dev/hdb1   *         1       510   4096543+  83  Linux
>>>/dev/hdb2           511       608    787185   82  Linux swap
>>>/dev/hdb3           609      4865  34194352+   f  Win95 Ext'd (LBA)
>>>/dev/hdb5           609      4865  34194321    c  Win95 FAT32 (LBA)
>>
>>
>> that is what it meant, [and table's probably the technical term].
>>
>> well, everything looks correct...  can I see /boot/grub/menu.lst as
>> well?
>
>
> the /boot/grub/menu.lst looks like this:
>
>
> #
>        #
> #                                menu.lst
>        #
> #
>        #
> ###############################################################################
>
>
> #------------------- by default boot the 4th list entry
>
> default=3
>
> #---------------- allow 10 seconds befor booting the default
>
> timeout=10
>
> #-------------------------- use preetier colors
>
> color green/black light-green/black
>
> #-----------------------------------------------------------------------------#
>
> ###############################################################################
>
> #.............................................................................#
>
> title Red Hat Linux (2.4.18-14)
>
> 	root (hd1,1)
> 	kernel /boot/vmlinuz-2.4.18-14 ro root=LABEL=/1 hda=ide-scsi
> ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0 ide5=0
> ide6=0 ide7=0 ide8=0 ide9=0
> 	initrd /boot/initrd-2.4.18-14.img
>
> #.............................................................................#
>
> title LFS 5.0 Linux (2.4.22)  ---> tests
>
> 	root (hd0,0)
> 	kernel (hd0,0)/boot/lfskernel root=/dev/hdb1 ro
>
> #.............................................................................#
>
> title Red Hat Linux (2.4.20)  ---> <ISDN + NETWORK> build in
>
> 	root (hd1,1)
> 	kernel /boot/vmlinuz-2.4.20-final ro root=/dev/sda2 ide0=0x1f0,0x3f6,14
> ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0 ide5=0 ide6=0 ide7=0 ide8=0
> ide9=0
> 	initrd /boot/initrd-2.4.20.img
>
> #.............................................................................#
>
> title Windows XP
>
> 	map (hd0,0) (hd1,0)
> 	map (hd1,0) (hd0,0)
> 	rootnoverify (hd1,0)
> 	chainloader +1
>
>
> #.............................................................................#
>
>
> i have build the system  from the red hat linux (2.4.18-14) distro
> but when i was building it my drive (the lfs drive) was atached to the
> promise udma100 controler on my asus a7v board and the value for ide4
> was -> ide4=0x6000,0x05802,10 so:
>
> during the whole build the drive was something like on /dev/hdi
> with the lfs partition hdi1 and swap hdi2
>
> also i had probs with installing grub cause in my chroot env after
> typing "grub"
>
> root ( "tab"
>
> grub recognized only my raid aray so the output was only hd0,
> but i had the lfs on hd1
>
> i had to install grub from the floppy disk
>
> after that booting was fine but i had instead of this error
>
> i mean the "unforseen error
>
> also another one wich exited witch the value 255
>
> and also the login prob
>
>
> so i atached the drive to the stnd controller on my board,
> changed the values in /etc/fstab to hdb1 and hdb2
>
> got rid of the 255 error (was something like /dev/hdi1 /dev/hdi2 :
> no such file or directory)
>
> but still having this one.....
>
> maybe this will help couse im still not sure if my raid configuration
> and the udma100 controller(wich is known for strange behavior)
> didnt mase up the whole build

I am sorry, but I am not sure what the problem is.  [Perhaps someone else
can give more advice].

Everything looks fine,  and obviously it is using the LFS Bootscripts, 
[implies right rootdir]



More information about the lfs-support mailing list