I’m resurrecting my old thread because the problem, which I initially thought was restricted to CouchPotato, keeps coming back.
Over the summer I had some time on my hands while deployed, so I ripped hundreds of my DVDs to mkv files. I just hooked up the external drive to my computer and tried to copy a large amount (~200GB) to the Drobo. After about 20 minutes the copy process failed because the target directories couldn’t be created. Sure enough the Drobo was gone from my Windows, Mac and Linux computers.
I tried ssh into the drive where the /mnt directory was completely empty. I issued a reboot command, but after rebooting the device didn’t show up in Windows and was no longer accessible by ssh. I’ve since cold-started it twice and rebooted the Windows machine, but I still don’t see the device. All the lights are lit fine and the switch shows me it is connected to the network.
This is what will make me get rid of the Drobo. I can’t deal with it mysteriously going offline and then being so much trouble to get back.
I sent a summary of the problem to support before my year ran out, and their response was they don’t support ssh. No information about why the drive keeps dropping offline, just the mention of ssh triggered the “we don’t support ssh” canned reply.
I’ve restarted the device twice since starting this post, once completely unplugging and re-plugging it, but it still doesn’t show up even though the front lights look normal. I’m hopeful I’ll get it back soon and be able to post the requested logs.[hr]
The device came up right after I hit send. Here are the logs requested, although they seem to be full of startup info and nothing from before I restarted (especially since I re-started 5 times). Next time I will try to catch it while the drives are disconnected and ssh still works.
# dmesg | tail -n 20
sd 0:0:0:0: [sda] 34359738368 512-byte hardware sectors (17592186 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sda:<6>about to lock the queue
about to look for elements
about to unlock the queue
about to wait for completion
sd 0:0:0:0: [sda] Attached SCSI disk
process_get_msg:NR trying to free elt: 93013488, cache: 93cd06e0
sd 0:0:0:0: Attached scsi generic sg0 type 0
handle_intercore_msg: Got Time Valid message
process_get_msg:NR trying to free elt: 93013448, cache: 93cd06e0
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 262136k swap on /mnt/DroboFS/swapfile. Priority:-1 extents:67 across:266792k
tail -n 20 /var/log/messages
tail: can't open '/var/log/messages': No such file or directory
tail: no files
[code]# tail -n 20 /var/log/nasd.log
Starting dependancy: apache
Tue Oct 18 17:22:35 2011: ==========================================================
Tue Oct 18 17:22:35 2011: DNASConfigInitThread: LoadConfigAndStart Finished correctly
Tue Oct 18 17:22:35 2011: Trying command: /sbin/after_fsck /mnt/DroboFS/
ls: /mnt/DroboFS//lost+found/: No such file or directory
mv: cannot rename ‘/mnt/DroboFS//lost+found’: No such file or directory
forkProcessAndWaitForResult: /sbin/after_fsck exited with a 256 value
Tue Oct 18 17:22:35 2011: LinuxSupportExecuteCommand: /sbin/after_fsck command failed with return value 256
Tue Oct 18 17:22:35 2011: DNASConfigInitThread: Sharing data in lost+found for /mnt/DroboFS failed with error 256
Tue Oct 18 17:22:54 2011: SledCommandThread::~SledCommandThread: 0x1a68b8
Tue Oct 18 17:22:54 2011: Done with SledCommandThread::~SledCommandThread: 0x1a6 8b8
Tue Oct 18 17:23:05 2011: SledCommandThread::HandleTimeoutEvent: GetNASSharesConfig: Received command
Tue Oct 18 17:23:05 2011: SledCommandThread::HandleTimeoutEvent: GetNASAdminConfig: Received command
Tue Oct 18 17:23:06 2011: SledCommandThread::HandleTimeoutEvent: GetNASAdminConfig: Received command
Tue Oct 18 17:23:39 2011: SledCommandThread::HandleTimeoutEvent: GetNASSharesConfig: Received command
Tue Oct 18 17:23:39 2011: SledCommandThread::HandleTimeoutEvent: GetNASAdminConfig: Received command
Tue Oct 18 17:23:40 2011: SledCommandThread::HandleTimeoutEvent: GetNASAdminConfig: Received command
Not trying to flood the forum, but now as I’m trying to copy 1 large file the copy process keeps completely freezing then restarting. I’m getting an average copy speed of 4.6 MB/s where I usually get about 30. These two lines showed up in the dmesg log:
dri_dnas_abort: called to abort cmnd: 8d70c3c0, 8d0758c0
dri_dnas_abort: called to abort cmnd: 8d70cde0, 8d075560