Hard drive woes 2012, part 2

Well, I can confirm that if you have one of the Lacie Network Space 2 2TB drives and you’re worried about your data, should you begin to get the old flashy light syndroome, you can rest in piece, as there’s a chance that your data is perfectly safe, albeit, coccooned in a little shitty box with incrediby sharp corners. All you have to do is get inside that box.

And it’s actually pretty easy to get inside. I’ll say from now though, that doing the following will almost certainly void your warranty, but if you’re like me, 2Tb of precious porn legitimate data is far more important than that. The case is relatively easy to open. There’s a little clip where the LED is. Just push it in, and the case will lift straight off. There are 4 screws keeping the drive on. These are standard screws, nothing to be worried about. Mine had a warranty sticker over one of the screws, which has been subsequently popped. Oh dear.

The drive then just slides backwards to disconnect it from the SATA fitting. That’s part one done, you should be left with a hard drive in your hand. The model in mine is a Seagate Barracuda Green. Other models may vary, but it’s just a bog standard drive. You’ll need to connect it to a SATA socket, both for power and data. Dependant on what you’re using from here, getting the data off it might be slightly different. I’ll write it how I did it, using Windows. the same should be possible on a Mac, and if you’re using Linux, you should already know what you’re doing.

Before you go ahead and do anything, first check your PC is recognising the drive correctly. To do this, right-click Computer, then Manage. Your normal drives will be there, along with the new drive, with several partitions listed as “RAW”. DO NOT DO ANYTHING ELSE AT THIS POINT. Windows cannot recognise the paritions, and naturally, tinkering around with them is going to be an entirely fruitless excercise. You’ve shown, however, that your data should be intact, and as I mentioned before, the drive is in a format that any Linux distribution should understand.

There are many ways to go from here. Personally, I chose the soft option. I downloaded a live Ubuntu CD, burned that, and booted from it. The 2Tb drive was recognised straight away, and I found the data store in /shares/1

I’m delighted I was able to get the data off the drive, hopefully this will help someone who has had a similar issue with their LaCie drive. I’m happy to answer comments if anyone has any queries.

Hard drive woes 2012, part 1…

Good lord, I bet you thought I’d fallen off the face of the earth. 2 months without an update. I’m afraid I’ve had another one of those “writers block” periods, where anything I write down blog-wise is just got enough to meet with my high standards of complete and utter tripe. Today, I shall strive to meet, nay even exceed my own lofty demands, as I begin to tell you, and explain in minute detail the problems I’ve currently been having when it comes to hard drives, or more exacter, my 2Tb LaCie Network Space 2 NAS drive.

To put it simply, a NAS drive is a network drive. A little box, whose sole purpose is to sit at one end of an ethernet connection, and serve me data.

“It’s easier than adding an internal drive to my computer”, I thought.

“It’ll be more convenient than leaving my computer on all the time”, I thought.

“It’ll be fun”, I thought.

To be fair, it was all of those three things, until Tuesday night. I’d been out to the Steak club. It’s not a club, but you can buy steaks for cheap. It was delicious. I returned home, and tried to access the drive through the network. Nothing. Not even the smallest hint of a sausage. Well, there was, because I could “ping” the drive on the network, but couldn’t access anything else. Not even the power button was responsive

“Joy”, I thought, as I ripped the power cable out of the back. It was then, when my nice little network drive, became nothing more than a solid, black brick. It would do one of two things, either start flashing red/blue after a few seconds, or slowly flash blue. I’ve left the drive in both of these modes for 24 hours, but still, nothing to report. Of course, just like any tech savvy idiot, I whinged on Twitter…

Bah. Looks like the NAS has given up the ghost. flashing red/blue light on Network Space 2 2Tb? Terminal?

Their reply was a little optimistic…

@mercuryvapour Hi, if its rhythmical red/blue/red/blue that means the automatic backup is in progress.

Yup, I checked the manual, and there it was, the flashing blue/red. I was almost excited, until I realised I’d left the drive in this state for 24 hours. I got back to them…

It is blue/red. Starts about 10 seconds after switch-on, been flashing like this for 24 hours, no other response from drive

I sat, and waited for what would hopefully be a nice, long list of steps I could get around this…

If the drive doesn’t work, you should get in contact with our support guys to investigate whats going on with it.

YE…. oh. You could almost hear my heart deflate, as I stared at the flashing box. It’s crypt of data, cuttently sealed, in a plastic shell, designed by Neil Poulton. the whole purpose of this blog entry is to see if anyone else has had the same problem, if they got around it, and if they avoided having to contact technical support…

THINGS I KNOW:-

If I need to crack it open, There’s just one drive in the box, so that should mean there’s no RAID shit to worry about. It’s either in ext3 or ext4 in XFS format (EDIT: SEE note below), which all versions of Linux should support. there are 10 partitions…

A couple of days before its death, I pulled the logfiles off it, though I doubt they’d give me any insight as to what’s wrong with it, they’ll at least give me some information on how the drive lived before it dies.

Line 57: May 26 23:24:29 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Disk 4 - /dev/sda - enabled]
	Line 60: May 26 23:24:29 NetworkSpace2 [DEBUG resource.set@460] Setting config value unicorn.storage.volume.root_device to [/dev/sda2]
	Line 65: May 26 23:24:30 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 1 - /dev/sda9 - enabled]
	Line 66: May 26 23:24:30 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 2 - /dev/sda8 - enabled]
	Line 67: May 26 23:24:30 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 3 - /dev/sda7 - enabled]
	Line 68: May 26 23:24:31 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 4 - /dev/sda6 - enabled]
	Line 69: May 26 23:24:31 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 5 - /dev/sda5 - enabled]
	Line 70: May 26 23:24:31 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 6 - /dev/sda4 - enabled]
	Line 71: May 26 23:24:31 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 7 - /dev/sda3 - enabled]
	Line 72: May 26 23:24:32 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 8 - /dev/sda2 - enabled]
	Line 74: May 26 23:24:32 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 9 - /dev/sda10 - enabled]
	Line 75: May 26 23:24:33 NetworkSpace2 [DEBUG resource.handle_event@262] Updating [Volume 10 - /dev/sda1 - enabled]

I feel I’m going to have fun and games with this…

EDIT: The fun and games, of which there were none of, are described in the post following this one. I’m not up on my Linux filesystems, so I’m not sure if there’s a big difference between what I originally said (ext2/3) or XFS. It may be possible to read XFS partitions in Windows, but it’s probably easier, quicker and less time consuming to download a live Linux CD and go nuts with it from there.