View previous topic :: View next topic |
Author |
Message |
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Fri Nov 23, 2012 6:20 pm Post subject: init-early.sh (1101) used greatest stack depth[solved] |
|
|
Gentoo stops booting at :
init-early.sh (1101) used greatest stack depth: 3560 bytes left
I have fixed this temporarily by making /boot rw, here's my grub entry:
title Gentoo
root (hd0,1)
kernel /boot/kernel13 root=/dev/sda5 rw
I have compiled devtmpfs support into the kernel
Last edited by Adel Ahmed on Sat Dec 01, 2012 6:59 am; edited 1 time in total |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Fri Nov 23, 2012 8:17 pm Post subject: |
|
|
the next line would be like "udevd[????]: starting version ???"
do you also have "[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs" which should be harmless in any case but which has been reported to relieve some udev stall problems.
what version of udev? _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Sat Nov 24, 2012 6:05 am Post subject: |
|
|
After compiling Automount devtmpfs at /dev, after the kernel mounted the rootfs
I stopped getting the messages, but X-server cannot boot now
error:
hostname: Host name lookup failure
/usr/bin/startx: line 174: cannot create temp file for here-document:Read-only file system
xauth: error in locking authority file /home/adel/.Xauthority
/usr/bin/startx: line 191: cannot create temp file .....etc
Fatal server error:
Could not create lock file in .tnno/tX0-lock
please consult the X.org.......
xinit:giving up
xinit: unable to connect to X server: Network is unreachable
xinit: server error
xauth: error in locking uthority file ........
When I set /boot back to rw, xorg is booting just fine, is the system failing to switch /boot to rw after the initial boot stages?
I'm clueless here |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Sat Nov 24, 2012 6:28 am Post subject: |
|
|
I agree with you, all the indications are that root was ro or there was a permissions problem when you were trying to start X.
boot cd abd run fsck on root partition
running Code: | rm /home/adel/.Xauthority | may clear the "xauth: error in locking authority file /home/adel/.Xauthority"
will tell if mounted ro
Code: | mount -o remount,rw / | will change to rw _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Sat Nov 24, 2012 7:39 am Post subject: |
|
|
When I removed the file, the system was unable to create a new authority file, fsck showed there wwere no problems, mount showed the root FS mounted as rw (/dev/root at / noatime, rw or something like that)
however I tried creating a directory under / and under/home and I got the read only file system error
and thanks for the fast responses |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Sat Nov 24, 2012 6:18 pm Post subject: |
|
|
Quote: | I tried creating a directory under / and under/home and I got the read only file system error | what permissions does show? does running Code: | mount -o remount,rw / | give you the ability to create directories/files? does a root login change your results? _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Mon Nov 26, 2012 7:12 pm Post subject: |
|
|
well remounting with teh rw options fixes everything and allows me to run startx, logging as root give the same result(ro file system)
here's the result of ls -l:
http://www.4shared.com/photo/k4bgpa8w/CAM00037.html
thanks,
Adel |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Mon Nov 26, 2012 7:27 pm Post subject: |
|
|
If root is an ext4fs and you are not using these menuconfig choices; they have been reported to help your problem:
Quote: | < > Second extended fs support
< > Ext3 journalling file system support
<*> The Extended 4 (ext4) filesystem
[*] Use ext4 for ext2/ext3 file systems
[*] Ext4 extended attributes
[ ] Ext4 POSIX Access Control Lists
[ ] Ext4 Security Labels
[ ] EXT4 debugging support |
setting as a kernel parameter in grub.conf has also beem reported to help _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Tue Nov 27, 2012 4:56 pm Post subject: |
|
|
nope my root fs is formatted in ext3 |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Nov 27, 2012 6:43 pm Post subject: |
|
|
Code: | nano/etc/init.d/root | should show the script that should be remounting root read write. should show fsck and root in the boot runlevel. What is in /etc/fstab? _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Wed Nov 28, 2012 6:21 pm Post subject: |
|
|
here's my init script:
#!/sbin/runscript
# Copyright (c) 2007-2009 Roy Marples <roy@marples.name>
# Released under the 2-clause BSD license.
description="Mount the root fs read/write"
depend()
{
need fsck
keyword -jail -openvz -prefix -vserver -lxc
}
start()
{
case ",$(fstabinfo -o /)," in
*,ro,*) return 0;;
esac
if echo 2>/dev/null >/.test.$$; then
rm -f /.test.$$ /fastboot /forcefsck
return 0
fi
ebegin "Remounting root filesystem read/write"
case "$RC_UNAME" in
Linux) mount -n -o remount,rw /;;
*) mount -u -o rw /;;
esac
if eend $? "Root filesystem could not be mounted read/write"; then
rm -f /fastboot /forcefsck
fi
}
here's my rc-udate
bootmisc | boot
consolekit | default
dbus | default
devfs | sysinit
dmesg | sysinit
fsck | boot
hostname | boot
hwclock | boot
keymaps | boot
killprocs | shutdown
local | default
localmount | boot
modules | boot
mount-ro | shutdown
mtab | boot
net.lo | boot
netmount | default
procfs | boot
root | boot
savecache | shutdown
swap | boot
sysctl | boot
termencoding | boot
udev | sysinit
udev-postmount | default
urandom | boot
wicd | boot
xdm | default
and here's y fstab
/dev/sda2 /boot ext3 defaults,noatime 1 2
/dev/sda5 / ext3 noatime 0 1
/dev/sda8 none swap sw 0 0 |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Wed Nov 28, 2012 9:42 pm Post subject: |
|
|
editing /etc/rc.conf to uncomment logging may provide extra information. Quote: | # rc_logger launches a logging daemon to log the entire rc process to
#/var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES" |
my /etc/init.d/root is different Code: | #!/sbin/runscript
# Copyright (c) 2007-2009 Roy Marples <roy@marples.name>
# Released under the 2-clause BSD license.
description="Mount the root fs read/write"
depend()
{
need fsck
keyword -jail -openvz -prefix -vserver -lxc
}
start()
{
case ",$(fstabinfo -o /)," in
*,ro,*)
;;
*)
# Check if the rootfs isn't already writable.
if checkpath -W /; then
rm -f /fastboot /forcefsck
else
ebegin "Remounting root filesystem read/write"
case "$RC_UNAME" in
Linux)
mount -n -o remount,rw /
;;
*)
mount -u -o rw /
;;
esac
eend $? "Root filesystem could not be mounted read/write"
if [ $? -eq 0 ]; then
rm -f /fastboot /forcefsck
fi
fi
;;
esac
ebegin "Remounting filesystems"
local mountpoint
for mountpoint in $(fstabinfo); do
case "${mountpoint}" in
/)
;;
/*)
mountinfo -q "${mountpoint}" && \
fstabinfo --remount "${mountpoint}"
;;
esac
done
eend 0
} | my /etc/init.d/fsck is Code: | #!/sbin/runscript
# Copyright (c) 2007-2009 Roy Marples <roy@marples.name>
# Released under the 2-clause BSD license.
description="Check and repair filesystems according to /etc/fstab"
_IFS="
"
depend()
{
use dev clock modules
keyword -jail -openvz -prefix -timeout -vserver -lxc
}
_abort() {
rc-abort
return 1
}
# We should only reboot when first booting
_reboot() {
if [ "$RC_RUNLEVEL" = "$RC_BOOTLEVEL" ]; then
reboot "$@"
_abort || return 1
fi
}
_forcefsck()
{
[ -e /forcefsck ] || get_bootparam forcefsck
}
start()
{
local fsck_opts= p= check_extra=
if [ -e /fastboot ]; then
ewarn "Skipping fsck due to /fastboot"
return 0
fi
if _forcefsck; then
fsck_opts="$fsck_opts -f"
check_extra="(check forced)"
elif ! yesno ${fsck_on_battery:-YES} && ! on_ac_power; then
ewarn "Skipping fsck due to not being on AC power"
return 0
fi
if [ -n "$fsck_passno" ]; then
check_extra="[passno $fsck_passno] $check_extra"
if [ -n "$fsck_mnt" ]; then
eerror "Only 1 of fsck_passno and fsck_mnt must be set!"
return 1
fi
fi
ebegin "Checking local filesystems $check_extra"
# Append passno mounts
for p in $fsck_passno; do
local IFS="$_IFS"
case "$p" in
[0-9]*) p="=$p";;
esac
set -- "$@" $(fstabinfo --passno "$p")
unset IFS
done
# Append custom mounts
for m in $fsck_mnt ; do
local IFS="$_IFS"
set -- "$@" "$m"
unset IFS
done
if [ "$RC_UNAME" = Linux ]; then
local skiptypes x
for x in $net_fs_list $extra_net_fs_list; do
skiptypes="${skiptypes}no${x},"
done
skiptypes="${skiptypes}noopts=_netdev"
fsck_opts="$fsck_opts -C0 -T -t $skiptypes"
if [ -z "$fsck_passno" -a -z "$fsck_mnt" ]; then
fsck_args=${fsck_args--A -p}
if echo 2>/dev/null >/.test.$$; then
rm -f /.test.$$
fsck_opts="$fsck_opts -R"
fi
fi
fi
trap : INT QUIT
fsck ${fsck_args--p} $fsck_opts "$@"
case $? in
0) eend 0; return 0;;
1) ewend 1 "Filesystems repaired"; return 0;;
2|3) if [ "$RC_UNAME" = Linux ]; then
ewend 1 "Filesystems repaired, but reboot needed"
_reboot -f
else
ewend 1 "Filesystems still have errors;" \
"manual fsck required"
_abort
fi;;
4) if [ "$RC_UNAME" = Linux ]; then
ewend 1 "Fileystem errors left uncorrected, aborting"
_abort
else
ewend 1 "Filesystems repaired, but reboot needed"
_reboot
fi;;
8) ewend 1 "Operational error"; return 0;;
12) ewend 1 "fsck interrupted";;
*) eend 2 "Filesystems couldn't be fixed";;
esac
_abort || return 1
}
stop()
{
# Fake function so we always shutdown correctly.
_abort() { return 0; }
_reboot() { return 0; }
_forcefsck() { return 1; }
yesno $fsck_shutdown && start
return 0
} | It might be helpful to try my versions. _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Fri Nov 30, 2012 6:47 am Post subject: |
|
|
Well the config files did not work, when I restored my config files however, it stated that /dev/sda5(my root partition) needs a disk check
so I used my emergency disk(slitaz 4.0 live usb) to perform a fsck on the partition, and it did find many errors, most were fixed I still have this single error(don't remember the exact error it had something to do with the inodes, I'll check l8er today) now everytime I start using the udev kernel, a mandatory disk check is performed on /dev/sda5
and the problem persists |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Fri Nov 30, 2012 7:35 am Post subject: |
|
|
may be a dying hard drive
boot cd, run fsck on all partitions, correct all errors, then see if you can get a clean boot.
do you have smartmontools installed? _________________ Defund the FCC. |
|
Back to top |
|
|
Adel Ahmed Veteran
Joined: 21 Sep 2012 Posts: 1523
|
Posted: Sat Dec 01, 2012 6:59 am Post subject: |
|
|
you are correct
I fixed the fsck problem using this page: http://bitc.bme.emory.edu/~lzhou/blogs/?p=70
and then fsck fixed the problems
now everything is working just fine
thanks alot for your time DONAHUE |
|
Back to top |
|
|
|