March 1, 200917 yr The only customization to unRAID I've done is WOL and "Powerdown". Interesting... Type: pwd mount losetup -a cd umount /dev/md1 and paste the output here. You might also do a ps -ef and post its output in case a clue might be there why you cannot un-mount the disk. Joe L.
March 1, 200917 yr Author Here is the output: Tower login: root Linux 2.6.24.4-unRAID. root@Tower:~# pwd /root root@Tower:~# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sda1 on /boot type vfat (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime) root@Tower:~# losetup -a losetup: invalid option -- a usage: losetup loop_device # give info losetup -d loop_device # delete losetup -f # find unused losetup [-e encryption] [-o offset] {-f|loop_device} file # setup root@Tower:~# cd root@Tower:~# umount /dev/md1 umount: /mnt/disk1: device is busy umount: /mnt/disk1: device is busy root@Tower:~# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 1 10:56 ? 00:00:01 init root 2 0 0 10:56 ? 00:00:00 [kthreadd] root 3 2 0 10:56 ? 00:00:00 [ksoftirqd/0] root 4 2 0 10:56 ? 00:00:00 [events/0] root 5 2 0 10:56 ? 00:00:00 [khelper] root 46 2 0 10:56 ? 00:00:00 [kblockd/0] root 48 2 0 10:56 ? 00:00:00 [kacpid] root 49 2 0 10:56 ? 00:00:00 [kacpi_notify] root 132 2 0 10:56 ? 00:00:00 [ksuspend_usbd] root 138 2 0 10:56 ? 00:00:00 [khubd] root 141 2 0 10:56 ? 00:00:00 [kseriod] root 181 2 0 10:56 ? 00:00:00 [pdflush] root 182 2 0 10:56 ? 00:00:00 [pdflush] root 183 2 0 10:56 ? 00:00:00 [kswapd0] root 223 2 0 10:56 ? 00:00:00 [aio/0] root 232 2 0 10:56 ? 00:00:00 [cifsoplockd] root 233 2 0 10:56 ? 00:00:00 [cifsdnotifyd] root 407 2 0 10:57 ? 00:00:00 [scsi_eh_0] root 408 2 0 10:57 ? 00:00:00 [usb-storage] root 453 2 0 10:57 ? 00:00:00 [rpciod/0] root 515 1 0 10:57 ? 00:00:00 /sbin/udevd --daemon root 614 2 0 10:57 ? 00:00:00 [ata/0] root 618 2 0 10:57 ? 00:00:00 [ata_aux] root 620 2 0 10:57 ? 00:00:00 [scsi_eh_1] root 623 2 0 10:57 ? 00:00:00 [scsi_eh_2] root 1168 2 0 10:57 ? 00:00:00 [scsi_eh_3] root 1169 2 0 10:57 ? 00:00:00 [scsi_eh_4] root 1289 1 0 10:57 ? 00:00:00 /usr/sbin/syslogd -m0 root 1297 1 0 10:57 ? 00:00:00 /usr/sbin/klogd -c 3 -x bin 1815 1 0 10:57 ? 00:00:00 /sbin/rpc.portmap nobody 1820 1 0 10:57 ? 00:00:00 /sbin/rpc.statd root 1829 1 0 10:57 ? 00:00:00 /usr/sbin/inetd root 1839 1 0 10:57 ? 00:00:00 /usr/sbin/acpid root 1841 1 0 10:57 ? 00:00:00 /usr/sbin/crond -l10 daemon 1843 1 0 10:57 ? 00:00:00 /usr/sbin/atd -b 15 -l 1 root 1858 1 0 10:57 ? 00:00:00 /usr/sbin/ifplugd -i eth0 -fwI - root 1875 1 0 10:57 ? 00:00:00 /usr/local/sbin/emhttp root 1884 2 0 10:57 ? 00:00:00 [mdrecoveryd] root 1915 1 0 10:57 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 1916 1 0 10:57 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 1918 1 0 10:57 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 1920 1 0 10:57 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 1922 1 0 10:57 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 1925 1 0 10:57 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 1951 1 0 10:57 ? 00:00:00 /usr/sbin/nmbd -D root 1953 1 0 10:57 ? 00:00:00 /usr/sbin/smbd -D root 1954 1953 0 10:57 ? 00:00:00 /usr/sbin/smbd -D root 1957 2 1 10:57 ? 00:00:01 [unraidd] root 1984 2 0 10:57 ? 00:00:00 [reiserfs/0] root 2052 1829 0 10:57 ? 00:00:00 in.telnetd: 192.168.1.100 root 2053 2052 0 10:57 pts/0 00:00:00 -bash root 2070 1953 0 10:58 ? 00:00:00 /usr/sbin/smbd -D root 2071 2053 0 10:58 pts/0 00:00:00 ps -ef root@Tower:~#
March 1, 200917 yr OK, samba is still running. It might have the disk busy. To stop it from the command line: Try killall smbd killlall nmbd umount /dev/md1
March 1, 200917 yr Author I've closed telnet i could not restart it. Powerdown script does not work either. I've typed in unRAID console: killall smbd- it printed: no process killed killall nmbd- it printed: no process killed umount /dev/md1- it printed :umount: /mnt/disk1: device is busy umount: /mnt/disk1: device is busy
March 1, 200917 yr I've closed telnet i could not restart it. Powerdown script does not work either. I've typed in unRAID console: killall smbd- it printed: no process killed killall nmbd- it printed: no process killed umount /dev/md1- it printed :umount: /mnt/disk1: device is busy umount: /mnt/disk1: device is busy OK, let's try to get fuser to kill the processes accessing that disk for you Type fuser -ck /mnt/disk1 Then try the umount once more. If successful, it should no longer show up when you type mount Joe L.
March 1, 200917 yr Author When I type fuser -ck /mnt/disk1 it prints nothing on screen just goes back to prompt When I type mount it prints: proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sda1 on /boot type vfat (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime)
March 1, 200917 yr When I type fuser -ck /mnt/disk1 it prints nothing on screen just goes back to prompt When I type mount it prints: proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sda1 on /boot type vfat (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime) but did you type umount /dev/md1 in between? (or umount /mnt/disk1) ? Joe L.
March 1, 200917 yr Author No. So I just tried to repeat the process. 1.Type:fuser -ck /mnt/disk1 - nothing printed 2. umount /dev/md1 -device is busy 3.mount - still shows disk1
March 1, 200917 yr No. So I just tried to repeat the process. 1.Type:fuser -ck /mnt/disk1 - nothing printed 2. umount /dev/md1 -device is busy 3.mount - still shows disk1 Wow. Something certainly has the disk locked... Try a forced un-mount umount -f /dev/md1 or umount -f /mnt/disk1
March 1, 200917 yr I don't have time for more than a quick comment here unfortunately. But I think there is a good chance that the reiserfsck (once you can run it), will show a good system, since it is probably based on the file system that was formatted on the new and EMPTY drive. You are going to have to force a rebuild of the entire Reiser file system on this drive, to see all of the data files BEYOND the first few gigabytes that were overwritten (and ignore the empty file system at the beginning of the drive). Perhaps someone can guide him in that? Gotta go...
March 1, 200917 yr Author Thanks for now. I guess I'll have to wait as I have completely no clue about linux. unRAID was running good I did not want to do much customization so I would not mess it up but I was still able to screw it up . If it wasn't for this forum I do not know what would I do.
March 1, 200917 yr They both print: device or resource busy OK, time to try a different approach. I want to reboot, but NOT have the system start rebuilding parity. To do that, I think we can just move (rename) the existing config/super.dat file and then reboot. mv /boot/config/super.dat /boot/config/super.orig Then, you can try typing powerdown since you have it installed. If that does not do it, there is always the power cord... That will usually shut down power. When the system comes back up, it should think it is a brand new array and wait for you to start it. If it starts on its own, stop it. If it starts a parity check, stop it. The command we will eventually want to run, once we can get to unmount the drive is reiserfsck --rebuild-tree -S -l /boot/recovery.log /dev/md1 We can't do that until we can get the disk un-mounted. Joe L.
March 2, 200917 yr Author After forced reboot(power switch) the array is stoped and all drives are blue. After typing: reiserfsck --rebuild-tree -S -l /boot/recovery.log /dev/md1 and the Yes This is what printed: Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/md1': No such file or directory
March 2, 200917 yr After forced reboot(power switch) the array is stoped and all drives are blue. After typing: reiserfsck --rebuild-tree -S -l /boot/recovery.log /dev/md1 and the Yes This is what printed: Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/md1': No such file or directory We are getting closer. Typing mount will show that the drive is not mounted,(none are mounted) since the array is stopped. Time to start the array using the normal management interface, and immediately stop any parity check it will begin. Then, login via telnet and type samba stop And then, umount /dev/md1 And then the reiserfsck rebuild command you last tried. Joe L.
March 2, 200917 yr Author I've started the array,stoped parity sync(parity drive is orange). Telnet to "tower" samba stop - nothing printed umount /dev/md1 -THE DAMN thing again says "device is busy"
March 2, 200917 yr I've started the array,stoped parity sync(parity drive is orange). Telnet to "tower" samba stop - nothing printed umount /dev/md1 -THE DAMN thing again says "device is busy" (At least it is acting consistently) Can you stop the array? What "device" is disk1. /dev/hd? or /dev/sd? You can see it in parens on the devices assignment page. Joe L.
March 2, 200917 yr Author After pressing STOP I loose browser contact. Telnet seams to still work I've tried: /dev/sdd it prints -bash: /dev/sdd: Permission denied sdd is what device page in the browser listed for disk1
March 2, 200917 yr After pressing STOP I loose browser contact. Telnet seams to still work I've tried: /dev/sdd it prints -bash: /dev/sdd: Permission denied sdd is what device page in the browser listed for disk1 OK... If you type mount Do you see any disks mounted?
March 2, 200917 yr Author Yes. proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sda1 on /boot type vfat (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime)
March 2, 200917 yr Author Well.Looks like I will have to fire up "Ubuntu Live CD". and try it myself from inthere.
March 2, 200917 yr Well.Looks like I will have to fire up "Ubuntu Live CD". and try it myself from inthere. Good luck with that. Do you have a "cd" drive on the same computer? or do you have to physically move the disk? Joe L.
March 2, 200917 yr Author I have a USB cd drive I can boot with. DO you have any other sugestions beside Ubuntu?
March 2, 200917 yr Author Can I use the same command: reiserfsck --rebuild-tree -S -l /boot/recovery.log /dev/md1 in Ubuntu ?
March 2, 200917 yr Can I use the same command: reiserfsck --rebuild-tree -S -l /boot/recovery.log /dev/md1 in Ubuntu ? No, odds are /boot does not exist on it, so you will need to choose a different place for the log "/tmp/recovery.log" will work Also, the ubuntu OS will identify the drive as something other than /dev/md1. Odds are it will be /dev/sd? But you will need to be sure of the disk itself. If might be /dev/sdd, it might be /dev/sda. It all depends on the order in which it scans the disks. In any case, you will want to run reiserfsck on the first partition on the disk. If the disk was /dev/sdd, the first partition is /dev/sdd1 If the disk is /dev/sdb, the first partition is /dev/sdb1. If the disk is /dev/sda, the first partition id /dev/sda1. If sdb, the command would then be: reiserfsck --rebuild-tree -S -l /tmp/recovery.log /dev/sdb1
Archived
This topic is now archived and is closed to further replies.