View previous topic :: View next topic |
Author |
Message |
Craig_Williamson n00b
Joined: 04 Mar 2003 Posts: 65 Location: New Zealand
|
Posted: Fri Jan 13, 2006 8:29 pm Post subject: Booting issues |
|
|
When I did my first boot up after installing gentoo I keep getting an error message relating to my /etc/fstab file. The file is as follows:
Code: |
tmpfs /newroot tmpfs rw 0 0
/dev/cdroms/cdrom0 /newroot/mnt/cdrom iso9660 ro 0 0
/dev/loop/0 /newroot/mnt/livecd squashfs ro 0 0
proc /newroot/proc proc rw,nodiratime 0 0
sysfs /newroot/sys sysfs rw 0 0
udev /newroot/dev tmpfs rw,nosuid 0 0
devpts /newroot/dev/pts devpts rw 0 0
cachedir /newroot/mnt/livecd/lib64/splash/cache tmpfs rw 0 0
tmpfs /newroot/mnt/livecd/lib64/firmware tmpfs rw 0 0
tmpfs /newroot/mnt/livecd/usr/portage tmpfs rw 0 0
usbfs /newroot/proc/bus/usb usbfs rw 0 0
/dev/sda3 / reiserfs rw 0 0
/dev/sda6 /shared vfat users,owner,rw,umask=000 0 0
none /proc proc rw,nodiratime 0 0
|
The error is to do with the lines that have /newroot/ in them. What do I do to fix this problem? I am new to gentoo so I don't really have a clue yet If you can help it would be really grateful.[/code]
Last edited by Craig_Williamson on Fri Jan 13, 2006 8:39 pm; edited 1 time in total |
|
Back to top |
|
|
Lazy_Dewd Tux's lil' helper
Joined: 22 Dec 2004 Posts: 144
|
Posted: Fri Jan 13, 2006 8:34 pm Post subject: |
|
|
EDITED
didn't recognised it as a fstab, lol
could you put it between 'code' tags please for the readability?
thx..
also, could you post the 'error message' |
|
Back to top |
|
|
Craig_Williamson n00b
Joined: 04 Mar 2003 Posts: 65 Location: New Zealand
|
Posted: Fri Jan 13, 2006 8:44 pm Post subject: |
|
|
Thanks for that. Is there a booting log anywhere I can't seem to find one. Anyway, all the error message says is that the system can't find the filesystems with the /newroot/ line in the /etc/fstab file. How do I fix this? |
|
Back to top |
|
|
Lazy_Dewd Tux's lil' helper
Joined: 22 Dec 2004 Posts: 144
|
Posted: Fri Jan 13, 2006 9:06 pm Post subject: |
|
|
I must admit I have never seen an fstab like that. what version of gentoo do you use? and did you alter things yourself?
there is something that can be usefull to you.
will give you the information about some things that happen on you system, mostly errors. the tail gives you only the latest so removing it will show you more.
after booting, there could be information on what went wrong.
normally the error means you havent got the needed filesystem in your kernel, but I can't pinpoint the error since I don't know this fstab layout |
|
Back to top |
|
|
yabbadabbadont Advocate
Joined: 14 Mar 2003 Posts: 4791 Location: 2 exits past crazy
|
Posted: Fri Jan 13, 2006 9:11 pm Post subject: |
|
|
That looks like an (almost) exact copy of the fstab that is part of the live filesystem when booted from the live cd. Did you just copy that to your chrooted system? If so, you need to re-read the installation manual. If not, then beats me how it got there. Either way, boot the live cd, enter the chroot, and follow the steps in the manual for configuring your fstab. |
|
Back to top |
|
|
Craig_Williamson n00b
Joined: 04 Mar 2003 Posts: 65 Location: New Zealand
|
Posted: Fri Jan 13, 2006 9:18 pm Post subject: |
|
|
All dmesg seems to do is list the kernel output when it boots. The error I got is after that in the standard boot process. I'll comment out the lines and see if that helps. Thanks for all your help. |
|
Back to top |
|
|
Lazy_Dewd Tux's lil' helper
Joined: 22 Dec 2004 Posts: 144
|
Posted: Fri Jan 13, 2006 9:40 pm Post subject: |
|
|
yabbadabbadont, glad you cleared the strange fstab layout up for me.
Craig_Williamson, please do as yabbadabbadont says. if commenting out doesn't work create your fstab. you'll have to do that manually by starting with the example
I doubt commenting out will work as a long-term solution. if it doesn't give you errors now, it might start asking for stuff later
the dmesg also gives the error messages during boot (not the complete text). at the moment, my filesystems didn't mount properly and dmesg gives me the error. try searching for fs
also, make sure you include (*) your modules for your filesystems instead of creating them as modules (M) |
|
Back to top |
|
|
|