Repairable or New HD?
Repairable or New HD?
Scanning time with GetDataBack shows my missing files, but copying them requires a $80 fee.
Of course not. That's how they make their money. At least you know there's a possibilty of data recovery, but don't count on all recovered files being readable.
If $80 gets some/most/all your data back it's a bargain. A professional recovery agency would charge many hundreds or thousands of dollars.
Now might be a good time to start a 3-2-1 backup strategy, to cope with the next disk failure.
https://www.techtarget.com/searchdatabac...p-Strategy
Do you know Tom Bombadil?
Ha, first off,
yes
I know Tom! Most people don't know the reference but I've always loved that little pony. I also happens to be the name of my poor deceased cat. Anyway, you are indeed a person of culture.
Thanks for the 3-2-1 idea. I'm just going to take the L on the data. I happened to backed up most of my stuff on Feb 1 so the loss is not bad and not worth $80.
The bigger problem might be that my 60-second boot time is up to 30 minutes since the power surge
. It boots from a different drive, the C : drive, that showed no damage after a scan. Other odd things like in file explorer I need to manually refresh to see new files, etc. Could that be corrected when I install the new drive?
Here is the HDTune scan and health results for the C drive.
Scan - Yippie, all green!
https://imgur.com/DkBkYzF
View: https://imgur.com/DkBkYzF
Health - It kind of concerns me that its blank, just like the damaged 870 Evo drive above.
https://imgur.com/LSOj1HS
View: https://imgur.com/LSOj1HS
Could it help to I reinstall windows? Could installing the new drive solve the boot problem? If you have suggestion on how to trouble shoot this I would greatly appreciate it.
I'm just pasting my drive info here because I'm confused by it. Maybe sharper eyes than mine will see something. Thanks again.
D Drive - Disk 0
ST2000LM015-2E81
Description Disk drive
Manufacturer (Standard disk drives)
Model ST2000LM015-2E8174
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 1
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 1.82 TB (2,000,396,321,280 bytes)
Total Cylinders 243,201
Total Sectors 3,907,024,065
Total Tracks 62,016,255
Tracks/Cylinder 255
Partition Disk #0, Partition #0
Partition Size 1.82 TB (2,000,397,795,328 bytes)
Partition Starting Offset 1,048,576 bytes
C Drive - Disk 2
(Partitioned?)
Samsung MZVLW512 (MVMe - Wait, I have a 3rd drive?)
Description Disk drive
Manufacturer (Standard disk drives)
Model SAMSUNG MZVLW512HMJP-00000
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 3
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 1
SCSI Target ID 0
Sectors/Track 63
Size 476.94 GB (512,105,932,800 bytes)
Total Cylinders 62,260
Total Sectors 1,000,206,900
Total Tracks 15,876,300
Tracks/Cylinder 255
Partition Disk #2, Partition #0
Partition Size 100.00 MB (104,857,600 bytes)
Partition Starting Offset 1,048,576 bytes
Partition Disk #2, Partition #1
Partition Size 476.10 GB (511,209,835,008 bytes)
Partition Starting Offset 122,683,392 bytes
Partition Disk #2, Partition #2
Partition Size 740.00 MB (775,946,240 bytes)
Partition Starting Offset 511,332,843,520 bytes
E Drive - Disk 1
(Damaged)
Samsung SSD 870 EVO 2TB
Description Disk drive
Manufacturer (Standard disk drives)
Model Samsung SSD 870 EVO 2TB
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 1
SCSI Bus 1
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 1.82 TB (2,000,396,321,280 bytes)
Total Cylinders 243,201
Total Sectors 3,907,024,065
Total Tracks 62,016,255
Tracks/Cylinder 255
Partition Disk #1, Partition #0
Partition Size 1.82 TB (2,000,381,018,112 bytes)
Partition Starting Offset 16,777,216 bytes
When a failed drive undergoes detection during startup, it may slow down the boot process. Remove the faulty drive and mechanical HDD, then attempt to start without them. This should be quick. It suggests there might be an issue with an SSD or a mechanical HDD (possibly both). This situation can occur if the SATA controller is configured in RAID mode. In BIOS, verify that the SATA controller is set to AHCI mode.
Oh, you mentioned the scary word "BIOS!" Really, thank you. I'll do that. I'm in that situation right now where I just won't boot until I complete some tasks, so I'll try it later. Once the new drive comes (tomorrow?), I'll unplug the damaged one. Heck, it will give me a chance to clean out the case.
I'm glad I managed to fix the corrupt E drive and installed a fresh 2T SDD. When I first turned it on, I went through the setup and worried I had made a mistake. After rebooting, it started up just like before, quickly and smoothly. It recognizes the C drive and the D drive but not the new one. Should I need to format it? How can I find its location? Thank you.
Hi. Yes, I noticed it in the system info section under storage/disks. In disk management, it appears as "disk 1" with a small red arrow and is marked unallocated. SkyNet, I'll attempt to initialize it. Thank you.