Quote:
Originally Posted by Arnulf
This looks bad. This value should be 0.
This SSD has run over 3465 hours and not only "used less than 1000 hours".
|
Eh, ok. But this is 140 days or less than 5 months because it work day and night.
I hope that this "Reallocated_Sector_Ct" mean that max 8 files will be corrupted, right?
Or may be this sectors are where partition table is stored and this is the reason
to have corrupt partition table?
Quote:
Originally Posted by BW-userx
for that magic number thing, it may have lost its partition info, I tired doing that recover thing, now I got a look it up... how to recover partition table. but that did not work for me. I ended up wiping that partition, but everything I had on it was something that I can replace. sometimes you just lose stuff and have to carry on.
|
it did not sound good.
but from fdisk -l i have this info:
Disk /dev/sdb: 223,57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: Patriot Burst El
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x393a909f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 1126399 1124352 549M 7 HPFS/NTFS/exFAT
/dev/sdb2 1126400 183175167 182048768 86,8G 7 HPFS/NTFS/exFAT
/dev/sdb3 183175168 184262655 1087488 531M 27 Hidden NTFS WinRE
/dev/sdb4 184262656 468862127 284599472 135,7G 5 Extended
/dev/sdb5 184264704 188166143 3901440 1,9G 82 Linux swap / Solaris
/dev/sdb6 188168192 468860927 280692736 133,8G 83 Linux
can this help recover partition and try to read info?