Hard drive woes, 2012, part 3

I’m returning back to the ‘old’ subject of my Lacie “Network Space 2” drive, which committed suicide a few months back, thanks to a couple of email questions. You may have followed the previous posts where I mention getting the data off the drive. this was, in all, a 90% success, but even running Linux, I ran into a similar problem as pointed out in the email. Some of the files couldn’t be accessed. I knew it was one I could easily overcome, but putting the time, and the little bit of effort in to do it, was a bit of a bore, so I left it.

That is, until my health problems re-arose. Well, not quite. I just had to go to the hospital so they could stick things all over my chest, and take yet more of my blood. Are they panning that shit for gold, or something? They might find amber nectar in there, but certainly no gold.

I digress. I decided to fire the drive up again, and rescue the last data on there. The problem was, that although I moved the majority of the data off the drive, I couldn’t access certain files, as they were owned by “root”, basically, the superuser of any Linux system. If you boot from a live Linux CD as I suggested in the past, you’re only a standard user. You’ll need to access the files owned by this root user.

Since my last update, I managed to find my 4Gb USB stick, so I changed my plans from using a live CD, to using a similar live CD, but mounted on a USB stick. To do this, you download the ISO you require as normal, download and run a program called Unetbootin, and allow it to work its magic. This allows you to have a USB stick with a bootable version of your favourite non-standard operating system. This was, as you can imagine, a lot quicker, smoother and quieter than having the DVD drive access something every time I move the mouse. This time, I ditched Ubuntu, and used the Ubuntu-based Linux Mint. It’s just that little more user-friendly. A couple more useful utilities , and because it’s on the USB drive, I can happily use stuff like Firefox without the whole system freezing while it uses the DVD drive.

Of course, you’ll run into the same problem you had with the original Ubuntu. You’re still a standard user. This is how you log-in as root…

Open “terminal”

sudo passwd root

It’ll then prompt you to enter a new password. Twice. It’s thorough like that.

Click on the “Start” button equivalent (forget what it’s called) and click “Leave”

There’ll be an option in there for a new session. Select that, and enter the user “root” and your new root password. Hurrah, you’ll now have a GUI with root access, and should be able to move those stubborn files as you would normally. I assume these instructions will work good with many, if not all Linux distros.

Thanks to the root access, I was able to have a poke around the drive’s “hidden” sections, and examine the “messages” file to see if I can decipher exactly what went wrong with it. Basically, I can’t.

Sep 18 02:04:44 NetworkSpace2 kernel: [  180.820000] ata1.00: status: { Busy }
Sep 18 02:04:44 NetworkSpace2 kernel: [  180.820000] ata1: hard resetting link
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.330000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.390000] ata1.00: configured for UDMA/33
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.390000] ata1: EH complete
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.410000] ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.410000] ata1: edma_err_cause=00000020 pp_flags=00000001, SError=00180000
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.410000] ata1: SError: { 10B8B Dispar }
Sep 18 02:04:44 NetworkSpace2 kernel: [  181.410000] ata1: hard resetting link
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.920000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.980000] ata1.00: configured for UDMA/33
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.980000] ata1: EH complete
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x180000 action 0x6 frozen
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000] ata1.00: edma_err_cause=00000020 pp_flags=00000001, SError=00180000
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000] ata1: SError: { 10B8B Dispar }
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000] ata1.00: cmd c8/00:20:e0:f2:38/00:00:00:00:00/e0 tag 0 dma 16384 in
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000]          res d0/00:20:e0:f2:38/00:03:00:00:00/e0 Emask 0x12 (ATA bus error)
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000] ata1.00: status: { Busy }
Sep 18 02:04:45 NetworkSpace2 kernel: [  181.990000] ata1: hard resetting link
Sep 18 02:04:45 NetworkSpace2 kernel: [  182.500000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
Sep 18 02:04:45 NetworkSpace2 kernel: [  182.560000] ata1.00: configured for UDMA/33
Sep 18 02:04:45 NetworkSpace2 kernel: [  182.560000] ata1: EH complete
Sep 18 02:e.vendor

After the e.vendor in that above logfile, which really shouldn’t be there, is a load of corrupt looking garbage, and I’m sure those “ATA bus error”, means that there’s something wrong with the drive, or the system can’t read from it. I remember those before the HDD died in my old firewall / server machine many years ago.

I’m not sure if that info above will help anyone else out, but drop me an email if it doesn’t, I’ll see what I can do.


In what is honestly going to be my final word on the subject, I thought I’d have one last little play with the dreaded Lacie Network Space 2, and my own personal findings. I powered it on again today, for one last “hurrah”. It, once again did either of the slow flashing, or rhythmic red/blue flashing. For funsies, I threw in a generic 500Gb drive, which it won’t have been expecting. The method behind my madness was that it may have had a failsafe copy of its operating system in ROM, and if it detects the “new” HDD, it might kick into some factory restore mode and initialize the drive. This wouldn’t appear to be the case, as I instantly got the flashing red/blue light, as soon as the drive began to boot. A factory reset didn’t help either.
Therefore, I consider the drive now to be scrapped.

I’ll keep the drive out of it, naturally. 2Tb could certainly come in useful (On Dec 8th 2012, I did indeed do this, via a cheap SATA caddy from C World). I don’t believe there’s a physical fault with the drive, but I do think there was some sort of root file system corruption. A decent NAS drive would be able to at least do something failsafe-y, perhaps a backup / disagnostic copy of the OS kept in flash ROM to allow some type of automatic restore / file system rebuild… the cost of flash memory these days is ridiculously low. It can’t be too difficult / much more expensive to do?

So, it’s all over. It was a short, bittersweet relationship. It had its uses. It turned out to be very limited, slow, and ultimately risked 2 terabytes of my precious porn torrentz photos of fluffy kittens and whalesong. As a plus-side (I can think of two), the drive was easy to open, and the OS was Linux based, so the data was easily rescued.

It’s not the end of my NAS drive experience though. I enjoyed it while it lasted, and I’m feeling the need to spend some money on something bigger and better…

UPDATE 4/2/17 It took me a good few years before I relied on NAS storage again, but these days I’m running a Synology DS216j. I never went back to this Lacie heap of shit. The drive itself still survives.

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…


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.

bash-3.2$ rm -r /gallery/*

Regular viewers will notice that, since February, the gallery has been half the man it used to be, and over the last few days, it’s ended up completely broken. The software itself was first installed in about 2007, and possibly due to constant upgrades, server moves and permission changes,it would appear that it’s became horribly corrupt, therefore I’m starting from scratch with it. I asked Andy the Iridium Fan if there was anything he wanted keeping on there, and he said “You may aswell delete all the photos from the Gallery and start again.”

Therefore, that’s exactly what I’ve done. Emptied the database, and deleted everything. I’ll probably start using it a lot more for my stuff, instead of uploading everything to flickr. It’ll probably be easier.

Watch this space…

A sad death to report.

Bah, I’ve been blogging for less than 24 hours, and I’m already swinging the scythe around. Thankfully, this isn’t the death of an actual person / animal / cellular structure, more an inanimate object. An inanimate object that I loved very much. I’m sad to announce the death of my big Canon camera, or rather the lens that came with it. It met a sad demise at 11AM yesterday morning when it lost a fight with the landing floor.

Annoyingly I was in the middle of preparing for my first proper photoshoot with it. I’d arranged with Gary F, Jamie S and Andy D, to take some photos of the vintage car rally that is brought to Hartlepool every year or so. For many years, I’d wanted to go for many years but unfortunately, other commitments (usually work) stopped me from attending. This year, I obviously didn’t have that to worry about, which meant I had the ideal opportunity to go and point the camera at brightly colured, shiny vehicles.

The morning started out a logistical nightmare to begin with. Jamie S’s car is off the road. Gary was coming to pick me up, but Jamie S also wanted to go. Fair enough. I send a text to arrange the slight change of travel plans.

Text: “Can you pick Jamie S up on the way?”
Reply: “You were meant to send that to Gary, not me”.

Yup. Turns out I’d sent a text to Jamie S, asking to pick himself up. Today was going to be a long day.

So, I go about preparing stuff, dusting down the big camera. Everything was OK. Ship shape, as it were.Gary arrives at the bottom of the long, gravel driveway that leads up to Mercuryvapour Towers. I grab the big camera, and on my way out of the door I think “oooh, I’ll take the little camera too”. I dash upstairs and realise I already had it, it was in my pocket. Gah, wasted trip. On my way out of the SLABJL office, Gary rings me, and in the juggle between answering phone and swinging unweildy camera bag about, the camera leaves the bag, and hits the carpeted, yet still hard, landing floor. “Whoops”, I thought, but the camera has survived harder falls than this. I bundle the whole lot back into the bag, and head off to the car rally. I switch on the camera. It doesn’t “sound” right. And it didn’t automatically focus either. Instead, it would judder around for a bit, the focus would attempt to fix itself, failing miserably. Sigh, the lens was dead. I lugged the camera around with me for the whole 2 hours we were there, knowing I was carrying what I’d class as a “dead relative”. We got back to the car, and I’d take a closer look at my deceased camera.

It wasn’t pretty. I’d tried to zoom in a few times, the lens jammed, I looked through the viewfinder, and was confronted with a broken image, as if part of the glass had shattered. Well, that was that. It was all over… maybe.

I get home, to inspect the damage. The first step was to remove the lens… and something fell out… THIS.


Now, I’m not expecting any help from this blog directly, but I’m a member of a few photography sites which I’ll add this to, in the hope of knowing what its purpose is. All I know is that it fell out. The lens is just the standard stock / kit lens that comes with the EOS 450D. Here’s what the ITPC data has to say about it.

Lens Type Canon EF-S 18-55mm f/3.5-5.6 IS

Anyway, something was clearly broken. While the lens was out, I gave the focus / zoom a go. It didn’t jam up. I looked through it, and it appeared to look normal. No broken glass. I took a photo of Daddykins. It worked. Wow. Obviously, my lens was missing a part, yet still “functional”. Or so I thought.

Obviously, I had to try this out a bit more. I’m sure if I’d lost some of my internal connections, I’d act slightly retarted (What, more than usual? – Ed). Shut up. I went out into the back garden, and the results weren’t pretty. The normally “smooth-for-a-kit-lens” auto focus would judder and jolt, rather like a floppy drive hitting a bad sector, the sounds were similar. Your eyes, using the viewfinder might only pick up the centre of the image. It’s not until you view it through the computer that you get the extent of the damage….


As my ex-work colleague Spence would say, in his own unique style… “Fuck, shit, piss”. Yup, something was shot. I contacted Andy D and asked if I could try his lens on my camera. I’m pleased to say it passed with flying colours. Or, at least the few shots I’d taken with it appeared to be OK. It means, that the loose part must have came from the lens (unless you know different?) and I’ll have no problems shopping for a new bit of glass.

Goodbye my trusty friend…

Oh, I can’t believe this has just happened. In fact, I have a little lump in my throat as I type this, but I have broken my trusty little Acer camera, which has been the stalwart of my photography since winter 2006. Over those 4 years, it’s not been far from my pocket, capturing the entirety of my trips to Edinburgh, Paris and Berlin over those past 4 years, along with many thousands of other images which have resided mainly on my flickr account since then.It’s even seen uses in situations where my main camera is a bit too bulky to carry around

Unfortunately, as quickly as it came into my life, and filled it full of wonderment, it exited, and has already left a gaping hole. I was taking some random photos earlier, mainly of a delicious curry I’d made, complete with incredibly undercooked chillies, when the batteries ran out. “Gah”, I thought as the lens retracted, and the power went off.

I slapped it in my trouser pocket, and proceeded to take the charger upstairs with me. As I bent over, to plug it in, I heard a shuddering crack. Knowing that there was only one thing my pocket, except for my keys, I knew something had gone horribly, horribly wrong.

And, indeed it had. My faithful little Acer, had, for some reason, switched itself back on and the lens had fully extended while in my pocket. I’d say that I’d accidentally switched it on with my massive penis, but these jeans are quite thick and the “on” button is quite small, meaning that any accidental button pushing with my enormous phallus is highly unlikely.

I removed it from my pocket to find the lens jammed in partially, After switching it off and back on, the lens motor sounded particularly unhealthy, and the lens got stuck halfway. I was presented with a “lens error”, and the camera switched itself off.

I’ve enjoyed using it, and have put it through probably more than it was designed for. The case is scratched to hell and back. The lens cover itself would occasionally get stuck when opening, The screen’s cracked, and there’s dirt on the sensor, as shown here…

The dirt is that little dark patch on the left, in case you didn’t know, or are thick. As can be seen in that photo, however, is that even after that amount of time, it still takes a good picture.

The batteries are on charge, so hopefully after a small amount of charge, it’ll be good to go again. It’ll be a sad day when it finally enters that little bit of drawer space in the sky.

I bet you thought I’d got lost…

You know, it’s always the same, I have a big long spell of blogging, and then I don’t do anything for two weeks. Oops. This wasn’t intended, but it seems I did the same last year, after the dizzying heights of the Berlin trip. Oh well.

Even for a British summer, the weather has been truly appaling. There hasn’t a day gone by where it’s not absolutely hoyed down at some point, or been so dull that it’s not even worth sticking your foot out of the door, never mind going around and doing stuff. Ever since I’ve came back from Paris, I have had absolutely nothing to look forward to… I tried to change this by arranging a trip to Countdown for me and Chris, but seeing as he has no holidays left, this has fallen through, leaving me once again, staring to the inky void, where the only light at the end of the tunnel is the reflection from the bottom of a beer glass. Even worse, is that it would have been my last chance to see it under its current guise.

On a lighter, and much happier note, Wayne has finally got back in touch after 18 months of being silent!! Unfortunately, he missed all of the email I’d sent to him in this time, thanks to NTL/Virgin’s policy of only keeping email on their servers for 90 days, but at least he’s still alive! Coatesy, however, is still radio-silent, and it’s looking less likely that he’ll ever get back in touch.

Christ, this is an amusing entry isn’t it? Laugh-a-bloody-minute.

To make things worse, morale at Employment Palace has hit an all time low. Once again, I can’t go into details, mainly because I’ll end up putting my fist through the monitor. This has depressed me more than anything, I think.

On another note, I’m an organ donor. Or rather, I’ve been for months, but I never bothered mentioning it before. I’m only metioning it now, because I’ve just found an old registration form I meant to send off, but never did. On the back of it, it states “Discuss your wishes with those closest to you, so they know your wishes should the time ever come… I’m sorry, I know whatthey mean, but surely that’s the worst way of putting it, ever? What do they mean by “should”? Do they suddently think I’m immortal, or something?

Ahem. On the subject of death, another reason I’ve not been updating much is the “dying” of Beastbits, my main machine… You may remember a few months ago, the 250Gb drive I had, started clicking, going all weird and just not working in general? Well, I replaced it with a 500Gb drive. And that’s on the way out too. It began with The Click of Death.

Eventually, strange things started happening The drive would disappear from Windows completely, and today, during the reboot, in the BIOS detection it wouldn’t reappear. Nasty. I decided the drive was duff. My curiousity got the better of me, and after a physical power-off, it reappeared.

Now, something was up, and I decided to back everything up to an external HDD. During ther copying process, it halted with a CRC error. Not good. Files were on the bad sectors! Oooooo!

I happened to note the name mentally of the corrupt file. Thankfully, it was just an outdated SQL dump I’ve done from my website, and wasn’t of much use anyway. The rest of the backup passed without a hitch. Everything else copied. For a bit of mirth, I decided to copy the original file I’d had a problem with. It copied first time. To me, this began to sound like something more “logical” than physical.

Soooo, I powered up “Darik’s Boot And Nuke”. I had used this in the past to “fix” the bad sectors on the earlier faulty drive I mentioned. Anyway. I started it on this drive, and it failed. It quit with an error saying that the drive may have bad sectors. Duh.

Fair enough, this wasn’t playing ball, so I grabbed the diagnostic software from the Samsung website. I wasn’t expecting miracles. Still, I ran it, and there they were, the bad sectors…


Fair enough, at least they were official.

I wasted at least 3 hours of my finite time on this planet allowing the disk check to finish. It prompted me to perform a disk erase. Meh. All backed up. It can’t do any harm. After all, these sectors were goosed, so another few hours later, the entire hard drive was erased, and I ran another diagnostic check Now, thanks to that photo, I had the exact location the bad blocks. Imagine my surprise as it skipped over them without a single bit of hesitation.

OK, so unbelievably, the drive was back to its normal self. All of this took place on Monday night, so I formatted the drive while I was at work on Tuesday. I returned home, and copied all of the stuff from the external backup drive onto it. And, tonight (Friday), it has gone back to the original problem of the click of death. Joy!

In a thread on Glens’ forum, I mentioned my problems, and although Crag has a very valid point, it’s still a 100% failure rate. And, I can’t even send it back either, because the only way it will detect bad sectors is obviously after the disk has been in use for a few days after an erase, which means there has to be data on it. And, seeing as I know the sort of ahem… “data” I keep on it, I’d rather not let it out of my sight!