the last word

Photography meets digital computer technology. Photography wins -- most of the time.

  • site home
  • blog home
  • galleries
  • contact
  • underwater
  • the bleeding edge
You are here: Home / The Bleeding Edge / Droboing over the weekend

Droboing over the weekend

June 27, 2009 JimK Leave a Comment

I got an email from a Drobo tech yesterday afternoon telling me to install the 1.3.1 release of the Drobo firmware. I told him I’d already figured that out but that I couldn’t do it until the Drobo console recognized Drobo1. He called and said to try power cycling it without the USB cable attached, and if that didn’t work, pull all the drives and power cycle.

I left the power off for a good minute and a half, and Drobo1 booted. I plugged in the USB cable, and the Drobo console saw the hardware. The lights on the front panel of the Drobo said that the disk was appropriately full, but Windows reported that the disk was corrupted and unreadable: I had lost all my data. Thank goodness it was just a backup.

I upgraded the firmware on Drobo1, and for good measure, did the same for Drobo2, which had been operating well.  I formatted Drobo1 using the Drobo console. I recreated the directory structure, set Vice Versa to work backing up all the files that had been lost, and went to bed.

When I got up this morning, the backup had failed. There was about 250 GB of data on Drobo1. The Drobo console reported everything was healthy. The file structure appeared correct for the data that was there. I tried writing a file to the Drobo and couldn’t. I tried opening a file stored on the Drobo and got a “file not found” message with the suggestion that I make sure a disk was in the specified drive.  I went down to the server room and took a look at the Drobo. All the lights were normal. This is the same situation that the box was in when my most recent troubles began. It seemed that the firmware update had not fixed the problem.

I thought about rebooting the Drobo, but it occurred to me that I might lose useful data from the log if I did that. I right-clicked on the Drobo Dashboard icon in the system try and selected “Get diagnostic information”.  I got a popup that said that I should wait while the console gathered diagnostic information. I waited…

…and waited. Finally, I got a popup that said, “I am unable to save the diagnostic information.” And, like so many of these windows that report bad news, the only option was to click “OK.” Why can’t there be a “That sucks” button?

And that’s where it sits. I will notify Drobo tech support.

The Bleeding Edge

← The Drobo plot thickens The new look →

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

March 2023
S M T W T F S
 1234
567891011
12131415161718
19202122232425
262728293031  
« Jan    

Articles

  • About
    • Patents and papers about color
    • Who am I?
  • Good 35-70 MF lens
  • How to…
    • Backing up photographic images
    • How to change email providers
  • Lens screening testing
    • Equipment and Software
    • Examples
      • Bad and OK 200-600 at 600
      • Excellent 180-400 zoom
      • Fair 14-30mm zoom
      • Good 100-200 mm MF zoom
      • Good 100-400 zoom
      • Good 100mm lens on P1 P45+
      • Good 120mm MF lens
      • Good 18mm FF lens
      • Good 24-105 mm FF lens
      • Good 24-70 FF zoom
      • Good 35 mm FF lens
      • Good 60 mm lens on IQ3-100
      • Good 63 mm MF lens
      • Good 65 mm FF lens
      • Good 85 mm FF lens
      • Good and bad 25mm FF lenses
      • Good zoom at 24 mm
      • Marginal 18mm lens
      • Marginal 35mm FF lens
      • Mildly problematic 55 mm FF lens
      • OK 16-35mm zoom
      • OK 60mm lens on P1 P45+
      • OK Sony 600mm f/4
      • Pretty good 16-35 FF zoom
      • Pretty good 90mm FF lens
      • Problematic 400 mm FF lens
      • Tilted 20 mm f/1.8 FF lens
      • Tilted 30 mm MF lens
      • Tilted 50 mm FF lens
      • Two 15mm FF lenses
    • Found a problem – now what?
    • Goals for this test
    • Minimum target distances
      • MFT
      • APS-C
      • Full frame
      • Small medium format
    • Printable Siemens Star targets
    • Target size on sensor
      • MFT
      • APS-C
      • Full frame
      • Small medium format
    • Test instructions — postproduction
    • Test instructions — reading the images
    • Test instructions – capture
    • Theory of the test
    • What’s wrong with conventional lens screening?
  • Previsualization heresy
  • Privacy Policy
  • Recommended photographic web sites
  • Using in-camera histograms for ETTR
    • Acknowledgments
    • Why ETTR?
    • Normal in-camera histograms
    • Image processing for in-camera histograms
    • Making the in-camera histogram closely represent the raw histogram
    • Shortcuts to UniWB
    • Preparing for monitor-based UniWB
    • A one-step UniWB procedure
    • The math behind the one-step method
    • Iteration using Newton’s Method

Category List

Recent Comments

  • JimK on Fujifilm GFX 100S pixel shift, visuals
  • Sarmed Mirza on Fujifilm GFX 100S pixel shift, visuals
  • lancej on Two ways to improve the Q2 handling
  • JimK on Sony 135 STF on GFX-50R, sharpness
  • K on Sony 135 STF on GFX-50R, sharpness
  • Mal Paso on Christmas tree light bokeh with the XCD 38V on the X2D
  • Sebastian on More on tilted adapters
  • JimK on On microlens size in the GFX 100 and GFX 50R/S
  • Kyle Krug on On microlens size in the GFX 100 and GFX 50R/S
  • JimK on Hasselblad X2D electronic shutter scan time

Archives

Copyright © 2023 · Daily Dish Pro On Genesis Framework · WordPress · Log in

Unless otherwise noted, all images copyright Jim Kasson.