On Sat, 02 Oct 2004 11:31, Gareth Williams wrote: > On Sat, 2 Oct 2004 10:38:30 +1200, Robert Fisher <[EMAIL PROTECTED]>
wrote: > > On Sat, 02 Oct 2004 10:20, Gareth Williams wrote: > > > I am not suggesting that it is a faulty disk. I am interested to know > > > if you can actually mount /dev/sda4, that is all. The errors above > > > look like fatal errors to me - that is to say, they seem to strongly > > > suggest that the mount command failed, resulting in a still un-mounted > > > /dev/sda4. How, then, do you come to the state in which /dev/sda4 IS > > > mounted? (which I presume you must, in order to use the partition). > > > > Sorry Gareth, I thought I was replying to the list earlier. > > > > Buggered if I know how it works after the error but it does. > > LOL. I thought I was too! I didn't realise this was "off-list" until just > now. damn gmail. I wish I could un-set that "reply-to:" header. Sending > this to the list now, to get it back on-list. > > Um, can I ask how you know it's working? Could you please do the > following commands directly after boot and post the output: > > # df > # mount /dev/sda4 /home/share > # df > > I have my suspicions that it isn't mounting, and anything you write to > "/home/share" is in fact being written inside that directory on the > root filesystem. Indeed. btw you'll get more information about mounted filesystems using the mount command without any arguments vis;- [EMAIL PROTECTED] ~ $ mount /dev/hda3 on / type reiserfs (rw,noatime,notail) none on /dev type devfs (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) none on /proc/bus/usb type usbdevfs (rw) none on /proc/bus/usb type usbfs (rw) nfsd on /proc/fs/nfs type nfsd (rw) berty:/usr/portage/distfiles/ on /usr/portage/distfiles type nfs (rw,addr=192.168.2.10) berty:/mnt/disk1 on /mnt/disk1 type nfs (rw,noexec,nosuid,nodev,addr=192.168.2.10) Be sure to check that you have either got the kernel module for the filesystem loaded, or the driver compiled into the kernel? [EMAIL PROTECTED] ~ $ zcat /proc/config.gz | egrep -i 'reiser|ext3' # CONFIG_EXT3_FS is not set CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set CONFIG_REISERFS_PROC_INFO=y # CONFIG_REISERFS_FS_XATTR is not set Hope that Helps -- Sincerely etc., Christopher Sawtell
