> On Monday 04 June 2007 14:46:27 Scott Weisman wrote: > > Hello, > Hi > > > root:~# more /proc/mounts > > rootfs / rootfs rw 0 0 > > none /sys sysfs rw 0 0 > > none /proc proc rw 0 0 > > udev /dev tmpfs rw 0 0 > > /dev/sda1 / ext3 rw,noatime,data=ordered 0 0 > > /dev/sda1 /dev/.static/dev ext3 rw,data=ordered 0 0 > > none /dev ramfs rw 0 0 > > none /proc/bus/usb usbfs rw 0 0 > > none /dev/pts devpts rw 0 0 > > none /dev/shm tmpfs rw 0 03 > This seems strange to me: > What's the rootfs already mounted as / ? > What's the difference between 'udev /dev tmpfs' and 'none /dev ramfs'? > > > Here is /etc/fstab: > > > > none /dev/pts devpts defaults 0 0 > > none /dev/shm tmpfs defaults 0 0 > > /dev/sda1 / ext3 defaults,noatime,errors=remount-ro 0 1 > > /dev/sda2 none swap defaults,sw 0 0 > Seems fine. > > I don't know what happen, but you should check which init script, initrd or > whetever mounts partitions. You can try to go to singleuser mode (init 2, > network disabled), look at kernel boot options, at mkinitcpio.conf, or > whetever. > > No usefull info in logs?
mkinitcpio.conf is irrelevant since the server uses the Xen kernel. In fact, no kernel package is installed at all. There's no initrd or anything remotely similar in my drive. I copied the kernel modules tree from the original /lib/modules before overwriting the disk with Arch, but otherwise, that's it. dmesg returns the following: Kernel command line: root=/dev/sda1 ro EXT3 FS on sda1, internal journal The last bootup gave the following: messages.log.1:May 27 18:32:13 pegasus Bootdata ok (command line is root=/dev/sda1 ro) messages.log.1:May 27 18:32:13 pegasus Kernel command line: root=/dev/sda1 ro messages.log.1:May 27 18:32:13 pegasus EXT3 FS on sda1, internal journal Scott _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
