LinuxMCE Forums
General => Installation issues => Topic started by: the_brain_police on August 14, 2007, 11:21:19 am
-
I'm having trouble performing a diskless boot using version 0704. The boot runs to LMCEUpdate_Apply.sh after which nothing else happens. Pressing any key dumps me to a login prompt.
I've tried this with two different PCs (a via sp13000 and an Intel laptop) - both appear to fail at the same place with only the timestamps and hostnames differing. I've rebuilt the boot images as described at http://wiki.linuxmce.com/index.php/Automatic_diskless_boot_of_media_directors (http://wiki.linuxmce.com/index.php/Automatic_diskless_boot_of_media_directors), but without success.
QSettings: error creating /home/mythtv/.qt
QSettings::sync: filename is null/empty
2007-08-14 09:25:48.819 New DB connection, total: 1
2007-08-14 09:25:48.852 Connected to database 'mythconverg' at host: dcerouter
2007-08-14 09:25:48.863 Current Schema version: 1160
No setting found for this machine's BackendServerIP.
Please run setup on this machine and modify the first page of the general settings.
* Starting Bluetooth services [ OK ]
* Starting MD monitoring service mdadm --monitor [ OK ]
* Starting anac(h)ronistic cron anacron [ OK ]
* Starting periodic command scheduler crond [ OK ]
usr/pluto/bin/LMCEUpdate_Apply.sh: line 21: /var/log/pluto/LaunchManager.progress.log: Read-only file system
Ubuntu 7.04 moon113 tty1
moon113 login:
Other 'read-only', 'permission denied' warnings/errors also appear earlier in the log - are these legitimate, or can they be ignored?
Any help would be much appreciated.
Cheers,
Calum
-
I can see 2 possible options for this happening, maybe the filesystem is for some reason shared as read-only in which case the nfs-server on the core needs to be reconfigured. Or the filesystem is mounted read only during the boot of the diskless machine, in this case you could try logging in as root (should have no password) and run these commands:
mount / -o remount,rw
startx
With a bit of luck I reckon that will remount the root filestem as read-write, and start the graphic environment. If this works (at least the first command) then the bootparameters of the diskless' kernel probably need to be readjusted.
-
also you can post the output of cat /etc/fstab or mount to see if there are rw options. also, post the output of startx too see for any error messages. it is possible that the xorg.conf might be incorrect.
-
Re-mounting the disk appear seem to make a difference. The outputs are as follows -
Diskless Laptop
cat /etc/fstab
proc /proc proc defaults 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
sysfs /sys sysfs defaults 0 0
192.168.0.2:/usr/pluto/diskless/113 / nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
192.168.0.2:/usr/pluto/var /usr/pluto/var nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
192.168.0.2:/usr/pluto/orbiter /usr/pluto/orbiter nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
192.168.0.2:/usr/pluto/keys /usr/pluto/keys nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
192.168.0.2:/usr/pluto/deb-cache /usr/pluto/deb-cache nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
//192.168.0.2/home /home cifs credentials=/usr/pluto/var/sambaCredentials.secret 1 1
mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
startx
/usr/bin/startx: line 132: cannot create time file for here document: Read-only file system
xauth: error in locking authority file /root/.Xauthority
/usr/bin/startx: line 144: cannot create time file for here document: Read-only file system
xauth: error in locking authority file /root/.Xauthority
/usr/bin/startx: line 144: cannot create time file for here document: Read-only file system
X: unable to open wrapper config file /etc/X11/Xwrapper.config
X: cannot stat /tmp/.X11-unix (No such file or directory), aborting.
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
xauth: error in locking authority file /root/.Xauthority
Core
cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 -- converted during upgrade to edgy
UUID=acba1f6e-db3a-428c-831e-8cd6e3da5801 / ext3 defaults,errors=remount-ro,user_xattr 0 1
# /dev/sda5 -- converted during upgrade to edgy
UUID=d17cfaa4-765b-4558-8d09-7a37b821e4c1 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
#Added by diskmounter utility
/dev/hde1 /media/hde1 vfat rw,user,fmask=0133,dmask=0022,uid=1000,gid=1000 0 0
mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro,user_xattr)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-16-386/volatile type tmpfs (rw)
automount(pid5582) on /mnt/device type autofs (rw,fd=4,pgrp=5582,minproto=2,maxproto=4)
nfsd on /proc/fs/nfsd type nfsd (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
Cheers,
Calum
-
Could you paste the output of "cat /proc/mounts" as well?
-
Sure thing -
Diskless Laptop
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
192.168.0.2:/usr/pluto/diskless/113 / nfs rw,vers=3,rsize=262144,wsize=262144,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.0.2 0 0
192.168.0.2:/usr/pluto/diskless/113 /dev/.static/dev nfs rw,vers=3,rsize=262144,wsize=262144,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.0.2 0 0
tmpfs /var/run tempfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tempfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tempfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /dev/bus/usb/.usbfs usbfs rw 0 0
udev /proc/bus/usb tmpfs rw 0 0
usbfs /proc/bus/usb/.usbfs usbfs rw 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
192.168.0.2:usr/pluto/var /usr/pluto/var nfs rw,vers=3,rsize=262144,wsize=262144,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.0.2 0 0
192.168.0.2:usr/pluto/orbiter /usr/pluto/orbiter nfs rw,vers=3,rsize=262144,wsize=262144,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.0.2 0 0
192.168.0.2:usr/pluto/keys /usr/pluto/keys nfs rw,vers=3,rsize=262144,wsize=262144,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.0.2 0 0
192.168.0.2:usr/pluto/deb-cache /usr/pluto/deb-cache nfs rw,vers=3,rsize=262144,wsize=262144,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.0.2 0 0
nfsd /proc/fs/nfsd nfsd rw 0 0
Core
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/disk/by-uuid/acba1f6e-db3a-428c-831e-8cd6e3da5801 / ext3 rw,data=ordered 0 0
/dev/disk/by-uuid/acba1f6e-db3a-428c-831e-8cd6e3da5801 /dev/.static/dev ext3 rw,data=ordered 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /lib/modules/2.6.20-16-386/volatile tmpfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /dev/bus/usb/.usbfs usbfs rw 0 0
udev /proc/bus/usb tmpfs rw 0 0
usbfs /proc/bus/usb/.usbfs usbfs rw 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
automount(pid5582) /mnt/device autofs rw,fd=4,pgrp=5582,timeout=10,minproto=2,maxproto=4,indirect 0 0
nfsd /proc/fs/nfsd nfsd rw 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
-
Sure thing -
Diskless Laptop
rootfs / rootfs rw 0 0
So the root filesystem is mounted RW according to the kernel (and just about everything else too) then I suppose it must be on the nfs-server's end.
BTW, have you configured your network in an unusual way? And could you show me the output of the "ifconfig" command?
-
maybe it could be helpful to force the mounting as rw of the diskless md. you should put just for a test the option rw into this line:
192.168.0.2:/usr/pluto/diskless/113 / nfs initr,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
it should be after the miodification:
192.168.0.2:/usr/pluto/diskless/113 / nfs initr,udp,rw,rsize=32768,wsize=32768,retrans=10,timeo=50 1 1
do the same thing for the other line that are related to the md.
-
I made the changes to /usr/pluto/diskless/113/etc/fstab as you suggested, but they don't seem to have made a difference.
My network setup is pretty straightforward -
192.168.0.1 - modem/router, DHCP disabled
192.168.0.2 - core, running DHCP (device 1)
192.168.0.3 - diskless VIA Epia SP13000, not currently used (device 94)
192.168.0.4 - diskless Intel laptop (device 113)
All devices are connected via 85MB Powerline ethernet.
Core ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:20:06:5A:11
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:499707 errors:0 dropped:0 overruns:0 frame:0
TX packets:1905873 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:408636180 (389.7 MiB) TX bytes:683445370 (651.7 MiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2371780 errors:0 dropped:0 overruns:0 frame:0
TX packets:2371780 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:269117037 (256.6 MiB) TX bytes:269117037 (256.6 MiB)
Laptop ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:05:0E:33
inet addr:192.168.0.4 Bcast:192.168.0.255 Mark:255.255.255.0
inet6 addr: fe80::20f:b0ff:fe05:e33/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:132185 errors:9 dropped:132 overruns:9 frame:0
TX packets:85233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:154779456 (147.6 MiB) TX bytes:9027049 (8.6 MiB)
Interrupt:18 Base address:0x4800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:326 errors:0 dropped:0 overruns:0 frame:0
TX packets:326 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32088 (22.5 KiB) TX bytes:32088 (22.5 KiB)
Core Network Settings
(http://img186.imageshack.us/img186/7510/corenetworksettingsti3.png)
-
Ah the infamous single network card setup rears it's ugly head again. Try to at least give the physical and virtual adapter eth0 and eth0:0) different ip-addresses. And that's about all the help I can give you with that kind of setup.
-
I just updated the 'known issues' wiki to talk about single nic installs.