April 20, 201412 yr i was in the process of trying to recover emhttp that suddenly decided to disappear, and to shut it down I issued the /etc/rc.d/rc.unraid stop command from the command prompt. All the disks in the array were shut down except, disk3, and i got the following error. Apr 20 13:45:44 Tower rc.unRAID[27533][27649]: Stopping the Array Apr 20 13:45:44 Tower rc.unRAID[27533][27655]: /root/mdcmd: line 11: echo: write error: Device or resource busy Apr 20 13:45:44 Tower kernel: mdcmd (73): stop Apr 20 13:45:44 Tower kernel: md: 2 devices still in use. looking at my server chassis (which has led indicators for each of the hard drives) i see that led for disk3 is on. Here is the output of ps -ef i should point out that i am also pre-clearing a separate drive, so that is not the one that is showing as active. after the drive is precleared, i'd like to reboot my server without damaging the data drive that seems to be active. UID PID PPID C STIME TTY TIME CMD root 1 0 0 Apr19 ? 00:00:06 init root 2 0 0 Apr19 ? 00:00:00 [kthreadd] root 3 2 0 Apr19 ? 00:00:06 [ksoftirqd/0] root 5 2 0 Apr19 ? 00:00:00 [kworker/0:0H] root 7 2 0 Apr19 ? 00:00:00 [kworker/u:0H] root 8 2 0 Apr19 ? 00:00:00 [migration/0] root 9 2 0 Apr19 ? 00:00:00 [rcu_bh] root 10 2 0 Apr19 ? 00:00:35 [rcu_sched] root 11 2 0 Apr19 ? 00:00:00 [migration/1] root 12 2 0 Apr19 ? 00:00:05 [ksoftirqd/1] root 14 2 0 Apr19 ? 00:00:00 [kworker/1:0H] root 15 2 0 Apr19 ? 00:00:03 [migration/2] root 16 2 0 Apr19 ? 00:00:05 [ksoftirqd/2] root 18 2 0 Apr19 ? 00:00:00 [kworker/2:0H] root 19 2 0 Apr19 ? 00:00:00 [migration/3] root 20 2 0 Apr19 ? 00:00:05 [ksoftirqd/3] root 22 2 0 Apr19 ? 00:00:00 [kworker/3:0H] root 23 2 0 Apr19 ? 00:00:00 [migration/4] root 24 2 0 Apr19 ? 00:00:02 [ksoftirqd/4] root 26 2 0 Apr19 ? 00:00:00 [kworker/4:0H] root 27 2 0 Apr19 ? 00:00:00 [migration/5] root 28 2 0 Apr19 ? 00:00:02 [ksoftirqd/5] root 30 2 0 Apr19 ? 00:00:00 [kworker/5:0H] root 31 2 0 Apr19 ? 00:00:00 [migration/6] root 32 2 0 Apr19 ? 00:00:02 [ksoftirqd/6] root 34 2 0 Apr19 ? 00:00:00 [kworker/6:0H] root 35 2 0 Apr19 ? 00:00:00 [migration/7] root 36 2 0 Apr19 ? 00:00:02 [ksoftirqd/7] root 38 2 0 Apr19 ? 00:00:00 [kworker/7:0H] root 39 2 0 Apr19 ? 00:00:00 [khelper] root 197 2 0 Apr19 ? 00:00:00 [bdi-default] root 199 2 0 Apr19 ? 00:00:00 [kblockd] root 376 2 0 Apr19 ? 00:00:00 [ata_sff] root 386 2 0 Apr19 ? 00:00:00 [khubd] root 494 2 0 Apr19 ? 00:00:00 [rpciod] root 524 2 1 Apr19 ? 00:21:33 [kswapd0] root 545 2 0 14:36 ? 00:00:00 [kworker/4:1] root 586 2 0 Apr19 ? 00:00:00 [fsnotify_mark] root 606 2 0 Apr19 ? 00:00:00 [nfsiod] root 610 2 0 Apr19 ? 00:00:00 [cifsiod] root 625 2 0 Apr19 ? 00:00:00 [crypto] root 807 2 0 Apr19 ? 00:00:00 [deferwq] root 816 2 0 Apr19 ? 00:00:00 [scsi_eh_0] root 817 2 0 Apr19 ? 00:00:00 [usb-storage] root 867 1 0 Apr19 ? 00:00:00 /sbin/udevd --daemon root 937 2 0 Apr19 ? 00:00:00 [scsi_eh_1] root 941 31192 0 14:40 pts/0 00:00:00 /bin/bash ./preclear_disk.sh -A root 947 941 0 14:40 pts/0 00:00:00 /bin/bash ./preclear_disk.sh -A root 948 947 3 14:40 pts/0 00:00:00 dd if=/dev/sdi bs=8225280 of=/de root 949 947 0 14:40 pts/0 00:00:00 sed -n 3p root 950 947 0 14:40 pts/0 00:00:00 awk { print $8,$9 } root 951 28383 0 14:41 pts/1 00:00:00 ps -ef root 969 2 0 Apr19 ? 00:00:00 [fw_event0] root 999 2 0 Apr19 ? 00:00:00 [scsi_eh_2] root 1011 2 0 Apr19 ? 00:00:00 [scsi_eh_3] root 1012 2 0 Apr19 ? 00:00:00 [scsi_eh_4] root 1013 2 0 Apr19 ? 00:00:00 [scsi_eh_5] root 1014 2 0 Apr19 ? 00:00:00 [scsi_eh_6] root 1015 2 0 Apr19 ? 00:00:00 [scsi_eh_7] root 1016 2 0 Apr19 ? 00:00:00 [scsi_eh_8] root 1018 2 0 Apr19 ? 00:00:01 [kworker/u:4] root 1110 2 0 Apr19 ? 00:00:00 [scsi_wq_2] root 1112 2 0 Apr19 ? 00:00:00 [kworker/3:1H] root 1114 2 0 Apr19 ? 00:00:00 [kworker/2:1H] root 1116 2 0 Apr19 ? 00:00:00 [kworker/1:1H] root 1159 2 0 Apr19 ? 00:00:00 [poll_0_status] root 1264 1 0 Apr19 ? 00:00:00 /usr/sbin/syslogd -m0 root 1268 1 0 Apr19 ? 00:00:00 /usr/sbin/klogd -c 3 -x bin 1310 1 0 Apr19 ? 00:00:00 /sbin/rpc.portmap root 1314 1 0 Apr19 ? 00:00:00 /sbin/rpc.statd root 1324 1 0 Apr19 ? 00:00:00 /usr/sbin/inetd root 1333 1 0 Apr19 ? 00:00:00 /usr/sbin/acpid 81 1343 1 0 Apr19 ? 00:00:00 /usr/bin/dbus-daemon --system root 1348 1 0 Apr19 ? 00:00:00 /usr/sbin/crond -l notice daemon 1350 1 0 Apr19 ? 00:00:00 /usr/sbin/atd -b 15 -l 1 root 1851 2 0 01:35 ? 00:00:03 [kworker/5:2] root 2645 2 0 08:31 ? 00:00:03 [kworker/7:2] root 8294 2 0 07:05 ? 00:00:03 [kworker/6:1] root 8894 2 0 12:38 ? 00:00:00 [kworker/5:0] root 10036 2 0 Apr19 ? 00:00:00 [md] root 10037 2 0 Apr19 ? 00:00:00 [mdrecoveryd] root 10040 2 0 Apr19 ? 00:00:00 [spinupd] root 10041 2 0 Apr19 ? 00:00:00 [spinupd] root 10042 2 0 Apr19 ? 00:00:00 [spinupd] root 10043 2 0 Apr19 ? 00:00:00 [spinupd] root 10044 2 0 Apr19 ? 00:00:00 [spinupd] root 10045 2 0 Apr19 ? 00:00:00 [spinupd] root 10046 2 0 Apr19 ? 00:00:00 [spinupd] root 10096 2 0 Apr19 ? 00:00:26 [unraidd] root 10099 867 0 Apr19 ? 00:00:00 /sbin/udevd --daemon root 10100 867 0 Apr19 ? 00:00:00 /sbin/udevd --daemon root 10116 2 0 Apr19 ? 00:00:00 [reiserfs] root 10162 1 0 Apr19 ? 00:00:00 /usr/local/sbin/shfs /mnt/user0 root 10171 1 88 Apr19 ? 18:40:54 /usr/local/sbin/shfs /mnt/user - root 10334 1 13 Apr19 ? 02:55:53 [java] <defunct> root 10425 2 0 07:12 ? 00:00:00 [kworker/7:1] root 13687 2 0 11:01 ? 00:00:00 [kworker/4:2] root 19339 2 0 07:41 ? 00:00:00 [kworker/3:2] root 26277 1 0 Apr19 tty1 00:00:00 -bash root 26278 1 0 Apr19 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 26279 1 0 Apr19 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 26280 1 0 Apr19 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 26281 1 0 Apr19 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 26282 1 0 Apr19 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 26628 2 0 Apr19 ? 00:00:00 [kworker/0:1H] root 26747 2 0 Apr19 ? 00:00:00 [kworker/4:1H] root 26754 2 0 Apr19 ? 00:00:00 [kworker/5:1H] root 26979 2 0 13:40 ? 00:00:00 [kworker/2:0] root 27069 2 0 13:41 ? 00:00:00 [kworker/0:1] root 27418 2 0 Apr19 ? 00:00:00 [kworker/7:1H] root 27556 2 0 Apr19 ? 00:00:00 [kworker/6:1H] root 28115 2 0 03:04 ? 00:00:16 [kworker/0:2] root 28382 1324 0 13:52 ? 00:00:00 in.telnetd: 192.168.1.7 root 28383 28382 0 13:52 pts/1 00:00:00 -bash avahi 28763 1 0 Apr19 ? 00:00:00 avahi-daemon: running [Tower.loc avahi 28764 28763 0 Apr19 ? 00:00:00 avahi-daemon: chroot helper root 28772 1 0 Apr19 ? 00:00:00 /usr/sbin/avahi-dnsconfd -D root 29763 2 0 14:05 ? 00:00:00 [kworker/4:0] root 29834 2 0 Apr19 ? 00:00:00 [kworker/u:1] root 29853 2 0 14:06 ? 00:00:00 [kworker/1:0] root 30118 2 0 14:08 ? 00:00:00 [kworker/2:1] root 30703 26277 0 Apr19 tty1 00:00:00 screen root 30704 30703 0 Apr19 ? 00:00:32 SCREEN root 30705 30704 0 Apr19 pts/0 00:00:00 /bin/bash root 31192 30705 0 Apr19 pts/0 00:00:14 /bin/bash ./preclear_disk.sh -A root 31249 1 0 Apr19 ? 00:00:00 /bin/bash /usr/local/sbin/cache_ root 31371 31249 0 Apr19 ? 00:00:00 find /mnt/user/movies -noleaf root 31714 2 0 06:36 ? 00:00:00 [kworker/6:2] root 32262 2 0 08:22 ? 00:00:00 [kworker/1:1] root 32503 1324 0 14:32 ? 00:00:00 in.telnetd: 192.168.1.7 root 32504 32503 0 14:32 pts/2 00:00:00 -bash root 32692 2 0 14:33 ? 00:00:00 [kworker/3:1] any thoughts on what i should do?
April 20, 201412 yr See here to rebuild the failed drive: http://lime-technology.com/forum/index.php?topic=32491.msg298738#msg298738
April 20, 201412 yr Author dgaschk, Thanks for that linked post. Only problem is that (if you remember you helped me on this other issue), one of my drives (disk4) has actually failed. I'm in the process of preclearing a drive to replace that failed disk4. Somehow it looks like unraid is stuck not releasing disk3. So on my server chassis the LEDs for disk3 and disk4 are both lit up (disk4 is lit up because there is a new hard drive being precleared). But disk3 is lit up because it is just stuck. If I follow the instructions in that post you linked would it not use the parity drive to rebuild disk3 similar to standard data rebuild? The last thing I want is to "rebuild" the stuck disk3 using the parity drive when the array isn't even complete (i.e. disk4 is missing), probably resulting in a bad construct. I was thinking of restarting the array (hard reboot) using these instructions that garycase provided here : http://lime-technology.com/forum/index.php?topic=32982.msg303429#msg303429 If I am not mistaken, I think what you suggested requires a fully operational array without a single drive failure?
April 21, 201412 yr Author Ok but how is issuing this command from the prompt different from starting the array with a new drive and asking for a data rebuild from parity into the new drive via the webui? Sent from my iPhone using Tapatalk
April 21, 201412 yr The procedure in the link is much safer. If all disks save one, e.g., disk3, are working then the procedure will safely rebuild disk 3 when the array is started.
Archived
This topic is now archived and is closed to further replies.