Very frustrated just now.
I've been having issues with an internal drive on the Studio PC. The drive has the Win7 NTFS GRAPHICS (G:) and VIDEO (V:) partitions on it, and I'm still having issues backing them up. Accessing individual files doesn't seem to be an issue, but trying to copy them over to an external drive hangs the copy very quickly, and causes Win7 to have "hiccups" with "Not responding messages on other applications. I tried booting to Linux Mint instead but Dolphin had issues mounting the drive. Last year I had similar issues accessing Illustrator files on G: and eventually I moved the exported PDF files and my documents / exegesis stuff to a server on my MEDIA PC. Everything points to a dying internal hard drive, and I'm no longer sure about what I can about this.
This morning when I tried to boot the PC, windows seemed to take forever to boot, and trying then to reboot to Linux Mint (either on the PC or off a live disk) seemed to hang as well. I've just got it to boot in Win7 (finally). I did a search on the net about issues related to copying from internal to external drives and one forum suggested it's an issue with older Western Digital drives (which it is). I have managed to create new folders on that drive, but maybe it's contributing to the issues.
Next I'm going to try copying stuff from G: over the local network to some spare space on the Media disk (I replaced an internal drive in that a couple of weeks back and it gained me an extra 1TB). If that works it'll slow, but it will at least back them up. I HAVE to make an effort to recover my graphic novel. The last backup it seems was in 2012.
*Suggestions please. *
#windows7 #harddrive
I can get you spinrite which can help with bad disks. I would yank the drive and mount it on usb and mirror, copy, iso, try anything that does not write, first.
ReplyDeleteI could do that - I have an old Astore mount that connects to USB. I'd have to remove the 1TB drive in that already. I might try a small copy test to the network first.
ReplyDeleteIt seems to be be 1/2 working. I have only about 70GB to back up on G:, and the Masters artwork is only about 45GB of that. Argh, it's like watching a kettle boil. I think I need to have lunch and check again.
ReplyDelete!! It's doing it slowly, but it seems to be working.
ReplyDeleteEven if Linux won't mount it you may be able to use dd on the raw device to copy it to a fresh disk and then maybe try a partition repair (fsck). If you can tell how many sectors the dodgy disk has you should be able to make a destination partition the same size. Otherwise a larger partition should be safe.
ReplyDeleteRob Masters do you have any suggestions?
I've certainly used the approach Stephen Gunnell suggested.
ReplyDeleteBTW I meant run fsck on the copy not the original. In fact don't use any repair utility on the original because it may well make things worse.
ReplyDeleteIf you haven't succeeded in recovering anything useful then bring the disk over here when you come and I'll have a look.
Stephen Gunnell
ReplyDeleteIt is copying about between 5-8kb/second to a USB drive, and about 14kb/sec over a network.
Hmm, I would need a fresh drive to copy it on to. That'd be an INTERNAL one wouldn't it? I was going to replace another internal drive on that PC so I already allocated $$$ to buy a 2TB drive.
Is dd and fsck Linux or Win?
Laura Ess It doesn't need to be an internal drive. Those commands are both old Unix tools virtually from day one but every Linux will have them. dd will do a raw block or stream copy from any Unix file system object to any other object (and that includes devices). It is fairly unused outside of sysadmin circles but when you need it you usually need it badly. fsck is file system consistency check. It is THE tool for repairing broken file systems in the Unix world. These days it has a lot of different modules for repairing different types of file systems.
ReplyDeleteSo I'd probably boot to a Live Mint and do these commands as ROOT on a terminal?
ReplyDeleteYep, but be sure to read up on the dd man page ... maybe post the command you work out here so it can be reviewed.
ReplyDeleteOK, we'll see what I can do.
ReplyDelete