1 |
meino.cramer@×××.de wrote: |
2 |
> Hi, |
3 |
> |
4 |
> After running smartctl for an extended offline test I got |
5 |
> a badblock (information extracted from the report): |
6 |
> |
7 |
> SMART Self-test log structure revision number 1 |
8 |
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error |
9 |
> # 1 Extended offline Completed: read failure 90% 14460 4288352511 |
10 |
> 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 |
11 |
> |
12 |
> I found a explanation to map the LBA to a partition here: |
13 |
> http://smartmontools.sourceforge.net/badblockhowto.html |
14 |
> |
15 |
> My partition layout is: |
16 |
> #> sudo fdisk -lu /dev/sda |
17 |
> |
18 |
> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors |
19 |
> Units: sectors of 1 * 512 = 512 bytes |
20 |
> Sector size (logical/physical): 512 bytes / 512 bytes |
21 |
> I/O size (minimum/optimal): 512 bytes / 512 bytes |
22 |
> Disklabel type: dos |
23 |
> Disk identifier: 0x07ec16a2 |
24 |
> |
25 |
> Device Boot Start End Blocks Id System |
26 |
> /dev/sda1 * 2048 104447 51200 83 Linux |
27 |
> /dev/sda2 104448 12687359 6291456 82 Linux swap / Solaris |
28 |
> /dev/sda3 12687360 222402559 104857600 83 Linux |
29 |
> /dev/sda4 222402560 1953525167 865561304 5 Extended |
30 |
> /dev/sda5 222404608 232890367 5242880 83 Linux |
31 |
> /dev/sda6 232892416 442607615 104857600 83 Linux |
32 |
> /dev/sda7 442609664 652324863 104857600 83 Linux |
33 |
> /dev/sda8 652326912 862042111 104857600 83 Linux |
34 |
> /dev/sda9 862044160 1071759359 104857600 83 Linux |
35 |
> /dev/sda10 1071761408 1281476607 104857600 83 Linux |
36 |
> /dev/sda11 1281478656 1491193855 104857600 83 Linux |
37 |
> /dev/sda12 1491195904 1953525167 231164632 83 Linux |
38 |
> 4288352511 <<< The number reported by smartctl |
39 |
> |
40 |
> |
41 |
> Following the linked document... |
42 |
> It seems the bad LBA is not on the checked harddisk. |
43 |
> |
44 |
> Or (more obvious) I did something wrong... |
45 |
> |
46 |
> How can I correctly identify the partition, which contains the bad |
47 |
> block? |
48 |
> How can I get a full list of all bad blocks (if any) from a mounted |
49 |
> file systems? |
50 |
> How severe is the problem? |
51 |
> |
52 |
> Thank you very much for any help in advance! |
53 |
> Best regards, |
54 |
> mcc |
55 |
> |
56 |
|
57 |
I ran into this recently on the drive that has my home partition on it. |
58 |
Someone posted that it *may* be fixable without moving data etc etc. I |
59 |
didn't have a backup at the time and nothing large enough to make one so |
60 |
I just ordered a new drive. When I got the new drive in and moved my |
61 |
data over, then I played with the drive a bit. I used dd to erase the |
62 |
drive, then stuck a file system back on it and filled it up. After |
63 |
doing that, the drive seems to have marked that part as bad and doesn't |
64 |
use it anymore. It has passed every test since then. |
65 |
|
66 |
My point is this, backups for sure just in case but you may be able to |
67 |
get the drive to mark that area as bad by moving that data off there. |
68 |
In my case, the files were corrupted and gone. Yea, I might could have |
69 |
sent it somewhere but I ain't into that. To much money for files I can |
70 |
replace if needed. I think it was like 3 or 4 video files. I'd find |
71 |
out what files are there, see what damage has occurred so that you can |
72 |
correct later, then find one really good howto and follow it. From my |
73 |
understanding, if you can move that data in the bad spot off there, the |
74 |
drive sort of fixes itself. If yours works like mine did, you should be |
75 |
OK but I'd use it for stuff that ain't so important. I use mine as a |
76 |
backup drive and test it a lot. ;-) I may trust it again, one day. |
77 |
|
78 |
So, most likely you will have some files corrupted at least. The drive |
79 |
*may* be fixable if you can figure out what files to move so that the |
80 |
drive can do its magic. Key thing is, finding out what to move so that |
81 |
the drive can do its work. Two options, try to move files so the drive |
82 |
can do its thing or move all the data to another drive, do like I did |
83 |
mine with dd and give it a fresh start that way. I didn't feel I had |
84 |
the experience to try and move the files so I took the 2nd option. Now |
85 |
I wish I had done option #1 and took notes that I could pass on. That |
86 |
would likely help you more. |
87 |
|
88 |
BTW, my drive gave that error for weeks and never got worse. I could be |
89 |
lucky on that one so do what needs doing as soon as you can, just in |
90 |
case. The last drive that really failed on me years ago, I got a |
91 |
serious warning from SMART. It even said I had like 24 hours to get my |
92 |
data off. It needs attention in your case but hopefully you will have |
93 |
the results I did in the end and you have time to deal with it. |
94 |
|
95 |
Dale |
96 |
|
97 |
:-) :-) |