January 26, 201016 yr Author heres the output root@Tower:~# reiserfsck /dev/sdb1 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sdb1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Jan 26 18:13:39 2010 ########### Replaying journal.. Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 120995 Internal nodes 746 Directories 114 Other files 927 Data block pointers 122350984 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Jan 26 18:27:51 2010 ########### root@Tower:~# reiserfsck /dev/sde1 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sde1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Jan 26 18:31:31 2010 ########### Replaying journal.. Reiserfs journal '/dev/sde1' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 594558 Internal nodes 3639 Directories 838 Other files 11130 Data block pointers 600611449 (286559232 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Jan 26 18:38:17 2010 ########### root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /mnt/disk1 mount: /dev/sdb1 already mounted or /mnt/disk1 busy root@Tower:~# root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 mount: /dev/sde1 already mounted or /mnt/disk4 busy root@Tower:~#
January 26, 201016 yr root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /mnt/disk1 mount: /dev/sdb1 already mounted or /mnt/disk1 busy root@Tower:~# root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 mount: /dev/sde1 already mounted or /mnt/disk4 busy If you just type 'mount' without any arguments, it will show what's mounted where.
January 26, 201016 yr Author mount output root@Tower:~# mount fusectl on /sys/fs/fuse/connections type fusectl (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sdg1 on /boot type vfat (rw,umask=000,shortname=mixed) /boot/bubba/portal/bubba_portal.fs on /var/www type ext3 (rw,loop=/dev/loop0) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime) /dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev)
January 26, 201016 yr OK, now for a few questions... If the two disk partitions are not mounted, and the reeiserfsck tests show they have no file system corruption, then the error output from that last attempt to mount the raw partitions is puzzling. I'm suspecting the "md" device is keeping the partitions "locked" but it could be the mount points are busy and the error message is just misleading. Let just try an alternate mount point first mkdir /tmp/xyz mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /tmp/xyx If it fails with the same error message, then it is the partition that is already in use by the "md" device. To stop the "md" device we'll need to un-mount the disks that it could mount, then unload the device. The following commands are extracted from your syslog. the "mount" command you ran showed disk2,3 and 5 mounted, so to un-mount those disks umount /mnt/disk2 umount /mnt/disk3 umount /mnt/disk5 If they were able to be un-mounted, then to un-load the "md" module rmmod md-mod Once the "md" device is un-loaded, we can re-try the mount of the raw disk partitions. mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /mnt/disk1 mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 It that works, then I'm going to be really confused. But let's see what happens. the file-systems look clean, but your "mount" is failing... I see you are running bubbaRAID, so you will get little support from lime-tech when booting that kernel. you might want to consider reverting back to a stock unRAID until your disks are back online. If the disks can be mounted, then to un-mount them type: umount /mnt/disk1 umount /mnt/disk4 To re-load the "md" kernel module type: modprobe md-mod super=/boot/config/super.dat slots=8,48,8,64,8,80,8,0,8,16,8,32,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 To re-mount the partitions on the "md" devices mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 Joe L.
January 26, 201016 yr Author heres the ouput, they didnt mount Linux 2.6.27.7-unRAID-Bubba. root@Tower:~# mkdir /tmp/xyz root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /tmp/xyx mount: mount point /tmp/xyx does not exist root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /tmp/xyz mount: /dev/sdb1 already mounted or /tmp/xyz busy root@Tower:~# umount /mnt/disk2 root@Tower:~# umount /mnt/disk3 root@Tower:~# umount /mnt/disk5 root@Tower:~# rmmod md-mod root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /mnt/disk1 mount: /dev/sdb1 already mounted or /mnt/disk1 busy root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 mount: mount point /mnt/disk4 does not exist root@Tower:~# ill stop using bubbaraid, dont really need to be running now anyway
January 26, 201016 yr Author heres a new log with bubbaraid disabled, i had to start unmenu to get the log, hope that wont effect anything. (but the server started with it not running and drives still showed up as unformatted) syslog-2010-01-27.txt
January 26, 201016 yr The mkdir worked. root@Tower:~# mkdir /tmp/xyz The mount failed because I made a typo, and you did not spot it. Your target to mount the partition should have been /tmp/xyz root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /tmp/xyx It knew xyx did not exist... (sorry, but the x and z are adjacent on my keyboard, and my poor typing got me) mount: mount point /tmp/xyx does not exist This however points me to the partition being locked by the "md" driver. root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /tmp/xyz mount: /dev/sdb1 already mounted or /tmp/xyz busy root@Tower:~# umount /mnt/disk2 root@Tower:~# umount /mnt/disk3 root@Tower:~# umount /mnt/disk5 un-loading the "md" drive should have released the lock... (I'm just guessing here, but sounds good) root@Tower:~# rmmod md-mod But it looks like it did not. Darn.... root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /mnt/disk1 mount: /dev/sdb1 already mounted or /mnt/disk1 busy It looks like /mnt/disk4 does not exist. You would need to create it first with "mkdir /mnt/disk4" and try once more. root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 mount: mount point /mnt/disk4 does not exist root@Tower:~# Interesting try... but no proof either way. not so far.
January 26, 201016 yr Author heres the new output (sorry i missed the fact disk4 dir didnt exist - rush to get to work ) root@Tower:~# mkdir /mnt/disk4 root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 mount: /dev/sde1 already mounted or /mnt/disk4 busy
Archived
This topic is now archived and is closed to further replies.