If SMART status is good (no bad sectors or other serious issues) it may be an issue with so-called “logical” bad sector(s), a sector (or a few contiguous sectors) in an inconsistent state (because of the unprepared shutdown), which happens to belong to a crucial filesystem structure. It can make the whole drive unresponsive, as described here.
I once had such an issue ; I imaged the drive using ddrescue, there was only a very small area that could not be read (53248 bytes or 104 sectors), so then I specifically overwrote that small area with a custom ddrescue command :
Code:
ddrescue -o 312881152 -s 53248 -f /dev/zero /dev/sdb /media/lubuntu/354E48E260FCFD84/dev_zero_dev_sdb.log
-o = offset
-s = size
-f = force (required to write to a physical device)
And the problem was solved – it no longer froze, the (HFS+) partition could be mounted with no hiccup.
In this case, based on the analysis by ddru_findbad (from ddr_utility), the unreadable area belonged to a file called “.journal”, which is apparently essential to the integrity of the HFS+ filesystem.
@ BGman
Quote:
Don't be naive. Nobody is going to help you for free.
Well, then, what are forums like this for exactly ?