Member Avatar for hayuff_cao

Hi friends, Im newbie here and I dont know if this thread suppose to be in this cat sorry for that...so here is my problem, my laptop was broke last week and wont boot anymore. Now, the only thing that I could recover files is by extracting my hard disk and put it into hdd enclosure but the problem is that I could not access some localdisk. It was actually 3 drive partition c,d,e,f the two of them were fine while the other are not accessible(drive c and f) and right clicking them will only result crushing my desktop(win8). Is there any way to resolve t his?? any thoughts and suggestions are much appreciated thank you in advanced ..oops, sorry for my badenglish :)

  • 2 Contributors
  • 1 Reply
  • 340 Views
  • 10 Hours Discussion Span
  • Latest Post Latest Post by rubberman

Dani AI

Generated

— short summary of the situation and a safe, practical workflow.

Problem recap: the removed laptop disk in an enclosure shows some NTFS partitions fine while two (including the former C:) are inaccessible; right‑clicking them makes the Windows desktop/Explorer crash. That pattern most often points to filesystem or metadata corruption, a drive with failing sectors, or a compatibility/driver issue from the USB<>SATA bridge. It can also be caused by encryption (BitLocker) or a Windows dynamic volume that the host system won’t mount cleanly.

Recommended approach (preserve first, repair later). As noted, working from an offline environment is sensible — but before attempting any repairs, make a full sector image of the drive so recovery attempts can be repeated safely:

# identify the disk (example)
lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT

# create a first-pass image (ddrescue keeps a log for retries)
sudo ddrescue -f -n /dev/sdX /media/recovery/drive-image.img /media/recovery/ddrescue.log

# follow-up pass to try bad sectors
sudo ddrescue -d -r3 /dev/sdX /media/recovery/drive-image.img /media/recovery/ddrescue.log

After an image exists, analyze the original and the image copy:

  • Run a SMART check to see if the drive is failing (sudo smartctl -a /dev/sdX).
  • Use TestDisk on the image to search/restore lost partitions or the partition table.
  • Mount the image read‑only under Linux (ntfs-3g or mount -o ro) and copy important files off before attempting writable repairs.
  • If the partition shows as encrypted or “dynamic/foreign” in Disk Management, recovery requires the BitLocker key or specialized tools.

Quick practical checks: try a powered USB adapter or connect the drive directly to a desktop SATA port (some enclosures hide disk quirks). If Explorer crashes only on that machine, browse the partition from Linux or a portable file manager that won’t invoke shell extensions. If the data is irreplaceable and SMART indicates hardware failure, stop further DIY repairs and consult a professional recovery service.

Member Avatar for rubberman

Burn and boot a live Linux CD/DVD image disc (a recent distribution that supports NTFS partitions). Then, assuming the disc is /dev/sdb (your normal system disc should be /dev/sda, but use fdisk -l to see for sure), use this command: fsck -f /dev/sdbN where N is the number of the bad partition. That should fix (as much as is possible) the bad partition. Alternatively, you can boot into Windows, and mark the bad partition to be checked and recovered on reboot. Then, reboot, and the Windows chkdsk tool should recover anything that is possible. Myself, I prefer the Linux tools - I generally find them more reliable when a disc and/or partition is really munged up.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.