Well, I'm at a bit of a wall here. The SSD apparently shows up, but does not mount. Since it won't mount, I can't use rsync or gparted. Yet it will still begin to boot windows before it hits the corrupted AVG file making it hang.
So I know there has to be some way to get the files (including folders and filenames, etc.) back, but I don't know how. Does anyone know how to do this? Or how to delete AVG from the drive so I can try to boot?
If the file system is corrupted, then it will be very difficult to impossible to get those filenames back.
Can you post the full error code?
If you made it that far once, then use photorec to save your files to a safe partition and comb through them carefully. ( Ive recovered many drives like this, but there are other ways too, some more difficult to use without prior experience or knowledge of error codes prohibiting the OS from booting )
Very difficult without being able to mount the drive...
p.s rsync is only good if you mounted the SSD, rsync wont read the drive at block level like /dev/sda2
It would fail to load avgidsha.sys, reboot, and keep cycling like that. I followed the directions from AVG to fix it, but that didn't work.
Yeah, I used photorec to copy all the files over to the Raid6 in the server, and the few I tested seem perfect, but of course they don't have the file names so it's a mess. If I can't get the file structure back then I guess I'll start sorting, but I'd rather restore the names if possible.
Can you explain how I mount a drive, just to make sure it isn't user error?
The drive is /dev/sda, but it has two partitions on it and /dev/sda/sda2 is the big one, so I assume I want to mount that partition and not the whole drive? And if that is true, then I would use the full path sudo mount /dev/sda/sda2 /media/ssd correct?
If by 'The Big One' you mean that is the SSD, then yes.
On a side note, Are you doing this with an LiveOS or did you attach the ssd to your desktop? The reason is, I find it weird that a drive you attached to a running system shouldn't have a derive letter like /dev/sda2 can you for sake of sanity and good practice type fdisk -l in the terminal and make sure the ssd is /dev/sda2 because fdisk -l will show you all the drives on your system
No, the SSD itself is /dev/sda, but it has two sub-directories (is that the right term?), /sda1 and /sda2. Based on the sizes for each directory I'm assuming /sda1 is the recovery partition, and /sda2 is the main Windows C: partition.
So I'm almost certain I did the mounting process correctly, but it returned a blur of errors.
Line after line of [ 763.********] end_request: critical target error, dev sda, sector ********* with the *'s being different numbers for each line. So I'm guessing this means it's not happy with the corrupt drive?
Damn... That's both what I was afraid of and what I was expecting. I've already used photorec to get the files back, so now what? Would a data recovery company be able to do anything with this, or is my only option basically format the drive, sort all the files from photorec, and learn my lesson about backups?