Re: not accessible due to inpage error" <-- Why is this happening?
- From: Will Pittenger <see.my.sig@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 17 May 2009 13:56:25 -0500
Well, we got the external drive due to problems on my Dad's computer. I had an older one that was working, but he needed more disk space. We found the WD for $69 with free shipping and no tax. So I decided to use it and put the other external on Dad's computer.
As for why I do backups to an external drive; well, my system was built in 2003, so I am concerned. But the reason why I started doing backups to an hard drive was I could gobble up even Blue-Ray disks -- and I don't have a Blue-Ray drive and just 250 GB on the internal drive.
I do need backups as the internal drive is relatively new and I have had to send it back to Seagate several times already. Each time usually at least means reinstalling Windows. (Hence, I started backing up the boot partition.)
I don't know much about the BSODs. All where hardware related. At least one was Page Fault in Non-paged Area. I would update my drivers, but most are considered legacy now and rarely updated. (Notably my ATI 9700.)
What corrupted the old Backups partition was G4L. I don't know all the options and accidentally told it to copy the boot partition on top of the backup partition rather than as a file. (The new image is a file, not a partition. I got that down.) At the time, I was getting grief from an old version of G4L that appears to have had a bit overflow on the amount of disk space available at the destination.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]
Shenan Stanley wrote:
Will Pittenger wrote:.Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.
I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.
I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.
The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.
Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the drive - to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD said, what registry settings were trying to be replaced, etc.)
In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside Windows." <-- you want to explain that? Sounds like you could have dmaged the *new* drive.
- References:
- Re: not accessible due to inpage error" <-- Why is this happening?
- From: Shenan Stanley
- Re: not accessible due to inpage error" <-- Why is this happening?
- Prev by Date: Re: still not working
- Next by Date: USB device shuts down PC
- Previous by thread: Re: not accessible due to inpage error" <-- Why is this happening?
- Next by thread: Re: not accessible due to inpage error" <-- Why is this happening?
- Index(es):
Relevant Pages
|
