Drobo

Drobo V1 Disconnect, loss of drive letters

Anyone out there having this happen also? Im using v1 with 2x1TB, 1x1.5TB and 1x500GB drives and 1.6.7 DB and 1.3.5 FW connected directly to USB 2 port on pc. I have 2 partitions of 2TB. Intermittantly I lose the drive letters, DB greys out and says no connection. The Drobo looks fine, drive lights and used space LEDs on but I can’t access the drive. Im forced to pull power plug, wait then plug power back in. After Drobo reboots all is normal again. This started happening quite a while back after a FW upgrade. I was hoping new FW would correct. I can’t seem to figure out any common factors in disconnects, it just happens whenever, I could be accessing the drive copying files or upon waking pc. Any ideas/help appreciated.

1st run chkdsk on your volumes.
2nd try a different USB cable or port.

Hmm I have 2 volumes on the Drobo of 2TB each, one has <800GB and the other is <100GB. The larger volume won’t run through chkdsk. Just boots me back to dos prompt in second stage of check. Smaller volume checks fine.

That’s odd. Can you copy/paste the details of the offending chkdsk?

The type of the file system is NTFS.
Volume label is Drobo_vol1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

WARNING! I parameter specified.
Your drive may still be corrupt even after running CHKDSK.

CHKDSK is verifying files (stage 1 of 3)…
7 percent complete. (56065 of 78848 file records processed)

It them bumps me back out to DOSprompt.

Very strange.

Do you get different behavior if you run chkdsk /f ?

I’m wondering if it drops out either because it can’t get a lock on the drive, or if the /I parameter for less-vigorous checking is skipping something that needs to be fixed and therefore going kaput.

No I don’t it craps out partway through also. Im wondering if it might be due to fact that I have Windows Media Player library pointed to the Drobo. Though it craps out even after Ive asked to unmount and lock the drive solely for chkdsk…

Very very odd… I’d try a check that’s independent of your installed OS - like booting from BartPE.

Try it from another computer. Your Drobos LEDs behaves just as mine did when my motherboard got communication problems.

I am having the exact same issue with my Drobo, it started a few months ago and I havent had a chance to look into it yet but every so often I will just need to pull the power on the Drobo and reconnect and everything will be fine for a few weeks then it will no longer detect and I would repeat the same process. I have four 1 TB Western Digital drives. I am running Windows 7 Home Premium and my Drobo Dashboard is 1.5.1 and my Drobo Firmware is 1.3.5 which are both the most recent available. I will try to chkdsk my Drobo and see how that goes and post that info here in this thread.

If you lose connection to the dashboard or to your computer, please do not just pull the power on your drobo to reboot. This can cause data corruption/file system corruption.

Definitely run a chkdsk, try a different cable.

Are you on Firewire or usb?

Hmm am not able to boot and do anything in Safe Mode. PC reboots after few seconds in Safe Mode. I’ll have to try Windows PE or Bart PE…or reinstall windows.

If you can’t boot with the Drobo disconnected then there’s something more sinister going on with your PC…

Try Drobo on a different machine and if it’s OK there, Chkdsk it.

Sorry for the delay, finally got around to doing a chkdsk on my Drobo and here are the results:

C:\Users\Eugene>chkdsk Z:
The type of the file system is NTFS.
Volume label is Drobo1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)…
1280 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)…
1306 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)…
1280 file SDs/SIDs processed.
Security descriptor verification completed.
13 data files processed.
Windows has checked the file system and found no problems.

16777087 MB total disk space.
479279136 KB in 912 files.
588 KB in 15 indexes.
0 KB in bad sectors.
591519 KB in use by the system.
65536 KB occupied by the log file.
16308463 MB available on disk.

  4096 bytes in each allocation unit.

4294934518 total allocation units on disk.
4174966708 allocation units available on disk.

No errors at all, I will continue to monitor my Drobo connection and if I lose my mount again within the next week or two I will then update this task.
Thanks,
EC

No errors is good news - at least data-wise.

I’ve had USB devices “pop in and out” for a variety of reasons, including failing motherboards, semi-broken USB ports, and faulty USB cables. So unfortunately it could be a number of things, but at least so far you have confirmed it’s not the Drobo or data stored on it.

Issue is back, started my PC this morning and voila…Drobo is gonzo! Will unplug the power on the Drobo and recycle power to get it back up and will do a chkdsk and post the results here. I wonder if this has anything to do with my Windows 7?

[align=center]Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

[/align]Z:>chkdsk
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is Drobo1.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)…
1536 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)…
1562 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)…
1536 file SDs/SIDs processed.
Security descriptor verification completed.
13 data files processed.
Windows has checked the file system and found no problems.

16777087 MB total disk space.
586176256 KB in 1316 files.
716 KB in 15 indexes.
0 KB in bad sectors.
591775 KB in use by the system.
65536 KB occupied by the log file.
16204071 MB available on disk.

  4096 bytes in each allocation unit.

4294934518 total allocation units on disk.
4148242332 allocation units available on disk.

Z:>

I have my Drobo on a Windows 7 machine (USB connection) and it’s fine. When the machine resumes from sleep, it does take about 3 minutes (sometimes longer, toward the 7-10 range) before Drobo reappears, but it does reappear.

can you run chkdsk with this command:

chkdsk z: /x

[align=justify][quote=“Jennifer, post:19, topic:1009”]
can you run chkdsk with this command:

chkdsk z: /x
[/quote]

Boot up my PC and the Drobo again was not mounted, lost its connection again this morning. After cycling the power it came back up and I ran the chkdsk z: /x as you requested and here were the results:

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

Z:>chkdsk z: /x
The type of the file system is NTFS.
Volume label is Drobo1.

CHKDSK is verifying files (stage 1 of 3)…
1536 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)…
1562 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)…
1536 file SDs/SIDs processed.
Security descriptor verification completed.
13 data files processed.
Windows has checked the file system and found no problems.

16777087 MB total disk space.
588779012 KB in 1333 files.
716 KB in 15 indexes.
0 KB in bad sectors.
591775 KB in use by the system.
65536 KB occupied by the log file.
16201529 MB available on disk.

  4096 bytes in each allocation unit.

4294934518 total allocation units on disk.
4147591643 allocation units available on disk.[/align]