[gentoo-user] [OT] Badblocks on my harddisk

[gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Hi,

After running smartctl for an extended offline test I got
a badblock (information extracted from the report):

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     14460         4288352511
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1

I found a explanation to map the LBA to a partition here:
http://smartmontools.sourceforge.net/badblockhowto.html

My partition layout is:
#> sudo fdisk -lu /dev/sda

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
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: 0x07ec16a2

Device     Boot      Start        End    Blocks  Id System
/dev/sda1  *          2048     104447     51200  83 Linux
/dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
/dev/sda3         12687360  222402559 104857600  83 Linux
/dev/sda4        222402560 1953525167 865561304   5 Extended
/dev/sda5        222404608  232890367   5242880  83 Linux
/dev/sda6        232892416  442607615 104857600  83 Linux
/dev/sda7        442609664  652324863 104857600  83 Linux
/dev/sda8        652326912  862042111 104857600  83 Linux
/dev/sda9        862044160 1071759359 104857600  83 Linux
/dev/sda10      1071761408 1281476607 104857600  83 Linux
/dev/sda11      1281478656 1491193855 104857600  83 Linux
/dev/sda12      1491195904 1953525167 231164632  83 Linux
                4288352511  <<< The number reported by smartctl


Following the linked document...
It seems the bad LBA is not on the checked harddisk.

Or (more obvious) I did something wrong...

How can I correctly identify the partition, which contains the bad
block?
How can I get a full list of all bad blocks (if any) from a mounted
file systems?
How severe is the problem?

Thank you very much for any help in advance!
Best regards,
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Dale]

meino.cramer@gmx.de wrote:
> Hi,
>
> After running smartctl for an extended offline test I got
> a badblock (information extracted from the report):
>
> SMART Self-test log structure revision number 1
> Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
> # 1  Extended offline    Completed: read failure       90%     14460         4288352511
> 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1
>
> I found a explanation to map the LBA to a partition here:
> http://smartmontools.sourceforge.net/badblockhowto.html
>
> My partition layout is:
> #> sudo fdisk -lu /dev/sda
>
> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> 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: 0x07ec16a2
>
> Device     Boot      Start        End    Blocks  Id System
> /dev/sda1  *          2048     104447     51200  83 Linux
> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> /dev/sda3         12687360  222402559 104857600  83 Linux
> /dev/sda4        222402560 1953525167 865561304   5 Extended
> /dev/sda5        222404608  232890367   5242880  83 Linux
> /dev/sda6        232892416  442607615 104857600  83 Linux
> /dev/sda7        442609664  652324863 104857600  83 Linux
> /dev/sda8        652326912  862042111 104857600  83 Linux
> /dev/sda9        862044160 1071759359 104857600  83 Linux
> /dev/sda10      1071761408 1281476607 104857600  83 Linux
> /dev/sda11      1281478656 1491193855 104857600  83 Linux
> /dev/sda12      1491195904 1953525167 231164632  83 Linux
>                 4288352511  <<< The number reported by smartctl
>
>
> Following the linked document...
> It seems the bad LBA is not on the checked harddisk.
>
> Or (more obvious) I did something wrong...
>
> How can I correctly identify the partition, which contains the bad
> block?
> How can I get a full list of all bad blocks (if any) from a mounted
> file systems?
> How severe is the problem?
>
> Thank you very much for any help in advance!
> Best regards,
> mcc
>

I ran into this recently on the drive that has my home partition on it. 
Someone posted that it *may* be fixable without moving data etc etc.  I
didn't have a backup at the time and nothing large enough to make one so
I just ordered a new drive.  When I got the new drive in and moved my
data over, then I played with the drive a bit.  I used dd to erase the
drive, then stuck a file system back on it and filled it up.  After
doing that, the drive seems to have marked that part as bad and doesn't
use it anymore.  It has passed every test since then. 

My point is this, backups for sure just in case but you may be able to
get the drive to mark that area as bad by moving that data off there. 
In my case, the files were corrupted and gone.  Yea, I might could have
sent it somewhere but I ain't into that.  To much money for files I can
replace if needed.  I think it was like 3 or 4 video files.  I'd find
out what files are there, see what damage has occurred so that you can
correct later, then find one really good howto and follow it.   From my
understanding, if you can move that data in the bad spot off there, the
drive sort of fixes itself.  If yours works like mine did, you should be
OK but I'd use it for stuff that ain't so important.  I use mine as a
backup drive and test it a lot.  ;-)  I may trust it again, one day. 

So, most likely you will have some files corrupted at least.  The drive
*may* be fixable if you can figure out what files to move so that the
drive can do its magic.  Key thing is, finding out what to move so that
the drive can do its work.  Two options, try to move files so the drive
can do its thing or move all the data to another drive, do like I did
mine with dd and give it a fresh start that way.   I didn't feel I had
the experience to try and move the files so I took the 2nd option.  Now
I wish I had done option #1 and took notes that I could pass on.  That
would likely help you more. 

BTW, my drive gave that error for weeks and never got worse.  I could be
lucky on that one so do what needs doing as soon as you can, just in
case.  The last drive that really failed on me years ago, I got a
serious warning from SMART.  It even said I had like 24 hours to get my
data off.  It needs attention in your case but hopefully you will have
the results I did in the end and you have time to deal with it.

Dale

:-)  :-) 

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Dale <rdalek1967@gmail.com> [14-07-26 09:54]:
> meino.cramer@gmx.de wrote:
> > Hi,
> >
> > After running smartctl for an extended offline test I got
> > a badblock (information extracted from the report):
> >
> > SMART Self-test log structure revision number 1
> > Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
> > # 1  Extended offline    Completed: read failure       90%     14460         4288352511
> > 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1
> >
> > I found a explanation to map the LBA to a partition here:
> > http://smartmontools.sourceforge.net/badblockhowto.html
> >
> > My partition layout is:
> > #> sudo fdisk -lu /dev/sda
> >
> > Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> > 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: 0x07ec16a2
> >
> > Device     Boot      Start        End    Blocks  Id System
> > /dev/sda1  *          2048     104447     51200  83 Linux
> > /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> > /dev/sda3         12687360  222402559 104857600  83 Linux
> > /dev/sda4        222402560 1953525167 865561304   5 Extended
> > /dev/sda5        222404608  232890367   5242880  83 Linux
> > /dev/sda6        232892416  442607615 104857600  83 Linux
> > /dev/sda7        442609664  652324863 104857600  83 Linux
> > /dev/sda8        652326912  862042111 104857600  83 Linux
> > /dev/sda9        862044160 1071759359 104857600  83 Linux
> > /dev/sda10      1071761408 1281476607 104857600  83 Linux
> > /dev/sda11      1281478656 1491193855 104857600  83 Linux
> > /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >                 4288352511  <<< The number reported by smartctl
> >
> >
> > Following the linked document...
> > It seems the bad LBA is not on the checked harddisk.
> >
> > Or (more obvious) I did something wrong...
> >
> > How can I correctly identify the partition, which contains the bad
> > block?
> > How can I get a full list of all bad blocks (if any) from a mounted
> > file systems?
> > How severe is the problem?
> >
> > Thank you very much for any help in advance!
> > Best regards,
> > mcc
> >
> 
> I ran into this recently on the drive that has my home partition on it. 
> Someone posted that it *may* be fixable without moving data etc etc.  I
> didn't have a backup at the time and nothing large enough to make one so
> I just ordered a new drive.  When I got the new drive in and moved my
> data over, then I played with the drive a bit.  I used dd to erase the
> drive, then stuck a file system back on it and filled it up.  After
> doing that, the drive seems to have marked that part as bad and doesn't
> use it anymore.  It has passed every test since then. 
> 
> My point is this, backups for sure just in case but you may be able to
> get the drive to mark that area as bad by moving that data off there. 
> In my case, the files were corrupted and gone.  Yea, I might could have
> sent it somewhere but I ain't into that.  To much money for files I can
> replace if needed.  I think it was like 3 or 4 video files.  I'd find
> out what files are there, see what damage has occurred so that you can
> correct later, then find one really good howto and follow it.   From my
> understanding, if you can move that data in the bad spot off there, the
> drive sort of fixes itself.  If yours works like mine did, you should be
> OK but I'd use it for stuff that ain't so important.  I use mine as a
> backup drive and test it a lot.  ;-)  I may trust it again, one day. 
> 
> So, most likely you will have some files corrupted at least.  The drive
> *may* be fixable if you can figure out what files to move so that the
> drive can do its magic.  Key thing is, finding out what to move so that
> the drive can do its work.  Two options, try to move files so the drive
> can do its thing or move all the data to another drive, do like I did
> mine with dd and give it a fresh start that way.   I didn't feel I had
> the experience to try and move the files so I took the 2nd option.  Now
> I wish I had done option #1 and took notes that I could pass on.  That
> would likely help you more. 
> 
> BTW, my drive gave that error for weeks and never got worse.  I could be
> lucky on that one so do what needs doing as soon as you can, just in
> case.  The last drive that really failed on me years ago, I got a
> serious warning from SMART.  It even said I had like 24 hours to get my
> data off.  It needs attention in your case but hopefully you will have
> the results I did in the end and you have time to deal with it.
> 
> Dale
> 
> :-)  :-) 
> 


Hi Dale,

thank you very much for the explanations you gave...and for the hope
in it ;) :)

In the meanwhile I found ddrescue... :)

It took me five hours to copy the disk (1T) binaryly (this word looks
wrong...) to another identical one with ddrescue. This beast is
smart...it first copies all what it is able to read instantly and
writes out a logfile, which contains the informations, what is wrong
with the disk and where:


# Rescue Logfile. Created by GNU ddrescue version 1.16
# Command line: ddrescue -f -n /dev/sda /dev/sdb ddrescue.log
# current_pos  current_status
0x36220000     +
#      pos        size  status
0x00000000  0x3621F000  +
0x3621F000  0x00000E00  /
0x3621FE00  0x00000200  -
0x36220000  0xE8AAB96000  +

In my case it report one errornous read and a defective size of 4096
bytes.

After that it is called a second time with different parameters and
the name of the logfile.

It then tries to read the sector again and retries it several times.
after that the logfile looks like this:


# Rescue Logfile. Created by GNU ddrescue version 1.16
# Command line: ddrescue -d -f -r3 /dev/sda /dev/sdb ddrescue.log
# current_pos  current_status
0x3621FE00     +
#      pos        size  status
0x00000000  0x3621F000  +
0x3621F000  0x00001000  -
0x36220000  0xE8AAB96000  +

What has been fixed has gone from the logfile.

So there is something left...

I will start a complete smartctl scan again and will see, whether
the bad block has been mapped and replaced.

I *hope* that this is a single accident, because only one spot (and a
small one) one a 1T disk is affected...we will see (fingers crossed).

By the way: There are other tools similiar to ddrescue called
dd_rescue and similiar. I found dddrescue recommended over the others
on the net.

Now....will start a smartctl complete check...this will take hours...
I will report later, what happened...

Best regards and have a nice weekend!
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2561 bytes --]

On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> Hi,
> 
> After running smartctl for an extended offline test I got
> a badblock (information extracted from the report):
> 
> SMART Self-test log structure revision number 1
> Num  Test_Description    Status                  Remaining  LifeTime(hours)
>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
>  200   000    Old_age   Always       -       1
> 
> I found a explanation to map the LBA to a partition here:
> http://smartmontools.sourceforge.net/badblockhowto.html
> 
> My partition layout is:
> #> sudo fdisk -lu /dev/sda
> 
> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> 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: 0x07ec16a2
> 
> Device     Boot      Start        End    Blocks  Id System
> /dev/sda1  *          2048     104447     51200  83 Linux
> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> /dev/sda3         12687360  222402559 104857600  83 Linux
> /dev/sda4        222402560 1953525167 865561304   5 Extended
> /dev/sda5        222404608  232890367   5242880  83 Linux
> /dev/sda6        232892416  442607615 104857600  83 Linux
> /dev/sda7        442609664  652324863 104857600  83 Linux
> /dev/sda8        652326912  862042111 104857600  83 Linux
> /dev/sda9        862044160 1071759359 104857600  83 Linux
> /dev/sda10      1071761408 1281476607 104857600  83 Linux
> /dev/sda11      1281478656 1491193855 104857600  83 Linux
> /dev/sda12      1491195904 1953525167 231164632  83 Linux
>                 4288352511  <<< The number reported by smartctl
> 
> 
> Following the linked document...
> It seems the bad LBA is not on the checked harddisk.
> 
> Or (more obvious) I did something wrong...

You are probably comparing different units.  The Start and End of fdisk are 
reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
reported by smartctl in bytes, you have:

4,288,352,511 ÷ 512 = 8,375,688.5

which would place it within your swap partition.

I would do this:

 swapoff /dev/sda2

 dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc

 mkswap -L swap -c /dev/sda2

 swapon /dev/sda2

and hopefully the problem will be gone when you run the next smartctl test.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> > Hi,
> > 
> > After running smartctl for an extended offline test I got
> > a badblock (information extracted from the report):
> > 
> > SMART Self-test log structure revision number 1
> > Num  Test_Description    Status                  Remaining  LifeTime(hours)
> >  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> > 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
> >  200   000    Old_age   Always       -       1
> > 
> > I found a explanation to map the LBA to a partition here:
> > http://smartmontools.sourceforge.net/badblockhowto.html
> > 
> > My partition layout is:
> > #> sudo fdisk -lu /dev/sda
> > 
> > Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> > 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: 0x07ec16a2
> > 
> > Device     Boot      Start        End    Blocks  Id System
> > /dev/sda1  *          2048     104447     51200  83 Linux
> > /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> > /dev/sda3         12687360  222402559 104857600  83 Linux
> > /dev/sda4        222402560 1953525167 865561304   5 Extended
> > /dev/sda5        222404608  232890367   5242880  83 Linux
> > /dev/sda6        232892416  442607615 104857600  83 Linux
> > /dev/sda7        442609664  652324863 104857600  83 Linux
> > /dev/sda8        652326912  862042111 104857600  83 Linux
> > /dev/sda9        862044160 1071759359 104857600  83 Linux
> > /dev/sda10      1071761408 1281476607 104857600  83 Linux
> > /dev/sda11      1281478656 1491193855 104857600  83 Linux
> > /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >                 4288352511  <<< The number reported by smartctl
> > 
> > 
> > Following the linked document...
> > It seems the bad LBA is not on the checked harddisk.
> > 
> > Or (more obvious) I did something wrong...
> 
> You are probably comparing different units.  The Start and End of fdisk are 
> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
> reported by smartctl in bytes, you have:
> 
> 4,288,352,511 ÷ 512 = 8,375,688.5
> 
> which would place it within your swap partition.
> 
> I would do this:
> 
>  swapoff /dev/sda2
> 
>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> 
>  mkswap -L swap -c /dev/sda2
> 
>  swapon /dev/sda2
> 
> and hopefully the problem will be gone when you run the next smartctl test.
> 
> -- 
> Regards,
> Mick

Hi MIck, 

thanks a lot for the clearification!

It also solves "the problem", that fsck does not report any problem
for the partitions...because there is none ;)
Which are good news.

I will clear the swap and report later what happens!

Best regards and have a nice weekend!
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> > Hi,
> > 
> > After running smartctl for an extended offline test I got
> > a badblock (information extracted from the report):
> > 
> > SMART Self-test log structure revision number 1
> > Num  Test_Description    Status                  Remaining  LifeTime(hours)
> >  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> > 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
> >  200   000    Old_age   Always       -       1
> > 
> > I found a explanation to map the LBA to a partition here:
> > http://smartmontools.sourceforge.net/badblockhowto.html
> > 
> > My partition layout is:
> > #> sudo fdisk -lu /dev/sda
> > 
> > Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> > 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: 0x07ec16a2
> > 
> > Device     Boot      Start        End    Blocks  Id System
> > /dev/sda1  *          2048     104447     51200  83 Linux
> > /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> > /dev/sda3         12687360  222402559 104857600  83 Linux
> > /dev/sda4        222402560 1953525167 865561304   5 Extended
> > /dev/sda5        222404608  232890367   5242880  83 Linux
> > /dev/sda6        232892416  442607615 104857600  83 Linux
> > /dev/sda7        442609664  652324863 104857600  83 Linux
> > /dev/sda8        652326912  862042111 104857600  83 Linux
> > /dev/sda9        862044160 1071759359 104857600  83 Linux
> > /dev/sda10      1071761408 1281476607 104857600  83 Linux
> > /dev/sda11      1281478656 1491193855 104857600  83 Linux
> > /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >                 4288352511  <<< The number reported by smartctl
> > 
> > 
> > Following the linked document...
> > It seems the bad LBA is not on the checked harddisk.
> > 
> > Or (more obvious) I did something wrong...
> 
> You are probably comparing different units.  The Start and End of fdisk are 
> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
> reported by smartctl in bytes, you have:
> 
> 4,288,352,511 ÷ 512 = 8,375,688.5
> 
> which would place it within your swap partition.
> 
> I would do this:
> 
>  swapoff /dev/sda2
> 
>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> 
>  mkswap -L swap -c /dev/sda2
> 
>  swapon /dev/sda2
> 
> and hopefully the problem will be gone when you run the next smartctl test.
> 
> -- 
> Regards,
> Mick

Hi Mick,

got this:

#> /root>mkswap -L swap -c /dev/sda2
1 bad page
Setting up swapspace version 1, size = 6291448 KiB
LABEL=swap, UUID=71686035-fad3-427c-a3a5-c86ac6aefa2f


...so the dd-command hasn't triggered the remapping?

What do you suggest how to proceed?
New harddrive?
Or?

Best regards,
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> > Hi,
> > 
> > After running smartctl for an extended offline test I got
> > a badblock (information extracted from the report):
> > 
> > SMART Self-test log structure revision number 1
> > Num  Test_Description    Status                  Remaining  LifeTime(hours)
> >  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> > 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
> >  200   000    Old_age   Always       -       1
> > 
> > I found a explanation to map the LBA to a partition here:
> > http://smartmontools.sourceforge.net/badblockhowto.html
> > 
> > My partition layout is:
> > #> sudo fdisk -lu /dev/sda
> > 
> > Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> > 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: 0x07ec16a2
> > 
> > Device     Boot      Start        End    Blocks  Id System
> > /dev/sda1  *          2048     104447     51200  83 Linux
> > /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> > /dev/sda3         12687360  222402559 104857600  83 Linux
> > /dev/sda4        222402560 1953525167 865561304   5 Extended
> > /dev/sda5        222404608  232890367   5242880  83 Linux
> > /dev/sda6        232892416  442607615 104857600  83 Linux
> > /dev/sda7        442609664  652324863 104857600  83 Linux
> > /dev/sda8        652326912  862042111 104857600  83 Linux
> > /dev/sda9        862044160 1071759359 104857600  83 Linux
> > /dev/sda10      1071761408 1281476607 104857600  83 Linux
> > /dev/sda11      1281478656 1491193855 104857600  83 Linux
> > /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >                 4288352511  <<< The number reported by smartctl
> > 
> > 
> > Following the linked document...
> > It seems the bad LBA is not on the checked harddisk.
> > 
> > Or (more obvious) I did something wrong...
> 
> You are probably comparing different units.  The Start and End of fdisk are 
> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
> reported by smartctl in bytes, you have:
> 
> 4,288,352,511 ÷ 512 = 8,375,688.5
> 
> which would place it within your swap partition.
> 
> I would do this:
> 
>  swapoff /dev/sda2
> 
>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> 
>  mkswap -L swap -c /dev/sda2
> 
>  swapon /dev/sda2
> 
> and hopefully the problem will be gone when you run the next smartctl test.
> 
> -- 
> Regards,
> Mick


Sorry for stuutering postings...overlocked this one:
#>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
dd: error writing ‘/dev/sda2’: Input/output error

Hrrrmpfff...

Why does it nt remap those ones?

Best regards,
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Volker Armin Hemmann]

Am 26.07.2014 03:49, schrieb meino.cramer@gmx.de:
> How severe is the problem?
>
first bad block? Not at all. Your drive's firmware knows about it, so
all read/write access should either generate an error your system can
deal with or will be mapped tranparently to a working reserve block.

Since it is swap, no fs error occured and no data was lost. So... be happy.

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Volker Armin Hemmann]

Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
> Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
>> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
>>> Hi,
>>>
>>> After running smartctl for an extended offline test I got
>>> a badblock (information extracted from the report):
>>>
>>> SMART Self-test log structure revision number 1
>>> Num  Test_Description    Status                  Remaining  LifeTime(hours)
>>>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
>>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
>>>  200   000    Old_age   Always       -       1
>>>
>>> I found a explanation to map the LBA to a partition here:
>>> http://smartmontools.sourceforge.net/badblockhowto.html
>>>
>>> My partition layout is:
>>> #> sudo fdisk -lu /dev/sda
>>>
>>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
>>> 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: 0x07ec16a2
>>>
>>> Device     Boot      Start        End    Blocks  Id System
>>> /dev/sda1  *          2048     104447     51200  83 Linux
>>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
>>> /dev/sda3         12687360  222402559 104857600  83 Linux
>>> /dev/sda4        222402560 1953525167 865561304   5 Extended
>>> /dev/sda5        222404608  232890367   5242880  83 Linux
>>> /dev/sda6        232892416  442607615 104857600  83 Linux
>>> /dev/sda7        442609664  652324863 104857600  83 Linux
>>> /dev/sda8        652326912  862042111 104857600  83 Linux
>>> /dev/sda9        862044160 1071759359 104857600  83 Linux
>>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
>>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
>>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
>>>                 4288352511  <<< The number reported by smartctl
>>>
>>>
>>> Following the linked document...
>>> It seems the bad LBA is not on the checked harddisk.
>>>
>>> Or (more obvious) I did something wrong...
>> You are probably comparing different units.  The Start and End of fdisk are 
>> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
>> reported by smartctl in bytes, you have:
>>
>> 4,288,352,511 ÷ 512 = 8,375,688.5
>>
>> which would place it within your swap partition.
>>
>> I would do this:
>>
>>  swapoff /dev/sda2
>>
>>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>
>>  mkswap -L swap -c /dev/sda2
>>
>>  swapon /dev/sda2
>>
>> and hopefully the problem will be gone when you run the next smartctl test.
>>
>> -- 
>> Regards,
>> Mick
>
> Sorry for stuutering postings...overlocked this one:
> #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> dd: error writing ‘/dev/sda2’: Input/output error
>
> Hrrrmpfff...
>
> Why does it nt remap those ones?
>
> Best regards,
> mcc
>
>
>
>
>
>
>
smartctl -a /dev/sda

without those information: crystal ball.

that said: it is swap. You shouldn't have to do anything. Don't touch dd.

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Dale]

Volker Armin Hemmann wrote:
> Am 26.07.2014 03:49, schrieb meino.cramer@gmx.de:
>> How severe is the problem?
>>
> first bad block? Not at all. Your drive's firmware knows about it, so
> all read/write access should either generate an error your system can
> deal with or will be mapped tranparently to a working reserve block.
>
> Since it is swap, no fs error occured and no data was lost. So... be happy.
>
> .
>

I wish I could have been that lucky.  ;-)

Dale

:-)  :-)

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 14:08]:
> Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
> > Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
> >> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> >>> Hi,
> >>>
> >>> After running smartctl for an extended offline test I got
> >>> a badblock (information extracted from the report):
> >>>
> >>> SMART Self-test log structure revision number 1
> >>> Num  Test_Description    Status                  Remaining  LifeTime(hours)
> >>>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> >>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
> >>>  200   000    Old_age   Always       -       1
> >>>
> >>> I found a explanation to map the LBA to a partition here:
> >>> http://smartmontools.sourceforge.net/badblockhowto.html
> >>>
> >>> My partition layout is:
> >>> #> sudo fdisk -lu /dev/sda
> >>>
> >>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> >>> 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: 0x07ec16a2
> >>>
> >>> Device     Boot      Start        End    Blocks  Id System
> >>> /dev/sda1  *          2048     104447     51200  83 Linux
> >>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> >>> /dev/sda3         12687360  222402559 104857600  83 Linux
> >>> /dev/sda4        222402560 1953525167 865561304   5 Extended
> >>> /dev/sda5        222404608  232890367   5242880  83 Linux
> >>> /dev/sda6        232892416  442607615 104857600  83 Linux
> >>> /dev/sda7        442609664  652324863 104857600  83 Linux
> >>> /dev/sda8        652326912  862042111 104857600  83 Linux
> >>> /dev/sda9        862044160 1071759359 104857600  83 Linux
> >>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
> >>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
> >>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >>>                 4288352511  <<< The number reported by smartctl
> >>>
> >>>
> >>> Following the linked document...
> >>> It seems the bad LBA is not on the checked harddisk.
> >>>
> >>> Or (more obvious) I did something wrong...
> >> You are probably comparing different units.  The Start and End of fdisk are 
> >> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
> >> reported by smartctl in bytes, you have:
> >>
> >> 4,288,352,511 ÷ 512 = 8,375,688.5
> >>
> >> which would place it within your swap partition.
> >>
> >> I would do this:
> >>
> >>  swapoff /dev/sda2
> >>
> >>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> >>
> >>  mkswap -L swap -c /dev/sda2
> >>
> >>  swapon /dev/sda2
> >>
> >> and hopefully the problem will be gone when you run the next smartctl test.
> >>
> >> -- 
> >> Regards,
> >> Mick
> >
> > Sorry for stuutering postings...overlocked this one:
> > #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> > dd: error writing ‘/dev/sda2’: Input/output error
> >
> > Hrrrmpfff...
> >
> > Why does it nt remap those ones?
> >
> > Best regards,
> > mcc
> >
> >
> >
> >
> >
> >
> >
> smartctl -a /dev/sda
> 
> without those information: crystal ball.
> 
> that said: it is swap. You shouldn't have to do anything. Don't touch dd.
> 
> 
> 


Hi Volker,

what happens if swapped is used and the write access tapped on the
bad area?

Here is the output of smartctl:


smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.13-RT] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (AF)
Device Model:     WDC WD10EARS-00Y5B1
Serial Number:    WD-WMAV51276611
LU WWN Device Id: 5 0014ee 001f5fb47
Firmware Version: 80.00A80
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sat Jul 26 14:16:19 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(19380) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 223) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3031)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   129   113   021    Pre-fail  Always       -       6508
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3957
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       14476
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       3808
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       324
193 Load_Cycle_Count        0x0032   196   196   000    Old_age   Always       -       14602
194 Temperature_Celsius     0x0022   115   101   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0032   200   197   000    Old_age   Always       -       13300
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       1

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Completed: read failure       90%     14472         4288352511
# 2  Extended offline    Completed: read failure       90%     14460         4288352511
# 3  Extended offline    Completed without error       00%     13954         -
# 4  Short offline       Completed without error       00%     13935         -
# 5  Extended offline    Completed without error       00%      7051         -
# 6  Extended offline    Completed without error       00%      2205         -
# 7  Short offline       Completed without error       00%       463         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


Best regards,
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 788 bytes --]

On Saturday 26 Jul 2014 11:26:54 meino.cramer@gmx.de wrote:

> got this:
> 
> #> /root>mkswap -L swap -c /dev/sda2
> 1 bad page

OK, so we know for sure now that the bad block was on your swap.  :-)


> Sorry for stuutering postings...overlocked this one:
> #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> dd: error writing ‘/dev/sda2’: Input/output error
> 
> Hrrrmpfff...
> 
> Why does it nt remap those ones?


As Volker posted since you don't even get a "records in" / "records out" from 
dd, it seems that it is the first block.  You can verify with badblocks -c 1  
-e 1 -o my_bad_blocks.txt if this is so.

The mkswap -c command will identify and mark the badblock so that this is not 
used again for allocating data to it.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 14:08]:
> Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
> > Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
> >> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> >>> Hi,
> >>>
> >>> After running smartctl for an extended offline test I got
> >>> a badblock (information extracted from the report):
> >>>
> >>> SMART Self-test log structure revision number 1
> >>> Num  Test_Description    Status                  Remaining  LifeTime(hours)
> >>>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> >>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
> >>>  200   000    Old_age   Always       -       1
> >>>
> >>> I found a explanation to map the LBA to a partition here:
> >>> http://smartmontools.sourceforge.net/badblockhowto.html
> >>>
> >>> My partition layout is:
> >>> #> sudo fdisk -lu /dev/sda
> >>>
> >>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> >>> 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: 0x07ec16a2
> >>>
> >>> Device     Boot      Start        End    Blocks  Id System
> >>> /dev/sda1  *          2048     104447     51200  83 Linux
> >>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> >>> /dev/sda3         12687360  222402559 104857600  83 Linux
> >>> /dev/sda4        222402560 1953525167 865561304   5 Extended
> >>> /dev/sda5        222404608  232890367   5242880  83 Linux
> >>> /dev/sda6        232892416  442607615 104857600  83 Linux
> >>> /dev/sda7        442609664  652324863 104857600  83 Linux
> >>> /dev/sda8        652326912  862042111 104857600  83 Linux
> >>> /dev/sda9        862044160 1071759359 104857600  83 Linux
> >>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
> >>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
> >>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >>>                 4288352511  <<< The number reported by smartctl
> >>>
> >>>
> >>> Following the linked document...
> >>> It seems the bad LBA is not on the checked harddisk.
> >>>
> >>> Or (more obvious) I did something wrong...
> >> You are probably comparing different units.  The Start and End of fdisk are 
> >> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
> >> reported by smartctl in bytes, you have:
> >>
> >> 4,288,352,511 ÷ 512 = 8,375,688.5
> >>
> >> which would place it within your swap partition.
> >>
> >> I would do this:
> >>
> >>  swapoff /dev/sda2
> >>
> >>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> >>
> >>  mkswap -L swap -c /dev/sda2
> >>
> >>  swapon /dev/sda2
> >>
> >> and hopefully the problem will be gone when you run the next smartctl test.
> >>
> >> -- 
> >> Regards,
> >> Mick
> >
> > Sorry for stuutering postings...overlocked this one:
> > #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> > dd: error writing ‘/dev/sda2’: Input/output error
> >
> > Hrrrmpfff...
> >
> > Why does it nt remap those ones?
> >
> > Best regards,
> > mcc
> >
> >
> >
> >
> >
> >
> >
> smartctl -a /dev/sda
> 
> without those information: crystal ball.
> 
> that said: it is swap. You shouldn't have to do anything. Don't touch dd.
> 
> 
> 

I ask since only the FIRST bad sector is reported...:

...Since I have a read error in te very beginning of my hardisk...
Does this mean, that all coming smartcontrol tests will fail early and
the rest of the disc is NOT tested then?


best regards,
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Volker Armin Hemmann]

Am 26.07.2014 14:16, schrieb meino.cramer@gmx.de:
> Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 14:08]:
>> Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
>>> Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
>>>> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
>>>>> Hi,
>>>>>
>>>>> After running smartctl for an extended offline test I got
>>>>> a badblock (information extracted from the report):
>>>>>
>>>>> SMART Self-test log structure revision number 1
>>>>> Num  Test_Description    Status                  Remaining  LifeTime(hours)
>>>>>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
>>>>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
>>>>>  200   000    Old_age   Always       -       1
>>>>>
>>>>> I found a explanation to map the LBA to a partition here:
>>>>> http://smartmontools.sourceforge.net/badblockhowto.html
>>>>>
>>>>> My partition layout is:
>>>>> #> sudo fdisk -lu /dev/sda
>>>>>
>>>>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
>>>>> 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: 0x07ec16a2
>>>>>
>>>>> Device     Boot      Start        End    Blocks  Id System
>>>>> /dev/sda1  *          2048     104447     51200  83 Linux
>>>>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
>>>>> /dev/sda3         12687360  222402559 104857600  83 Linux
>>>>> /dev/sda4        222402560 1953525167 865561304   5 Extended
>>>>> /dev/sda5        222404608  232890367   5242880  83 Linux
>>>>> /dev/sda6        232892416  442607615 104857600  83 Linux
>>>>> /dev/sda7        442609664  652324863 104857600  83 Linux
>>>>> /dev/sda8        652326912  862042111 104857600  83 Linux
>>>>> /dev/sda9        862044160 1071759359 104857600  83 Linux
>>>>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
>>>>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
>>>>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
>>>>>                 4288352511  <<< The number reported by smartctl
>>>>>
>>>>>
>>>>> Following the linked document...
>>>>> It seems the bad LBA is not on the checked harddisk.
>>>>>
>>>>> Or (more obvious) I did something wrong...
>>>> You are probably comparing different units.  The Start and End of fdisk are 
>>>> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
>>>> reported by smartctl in bytes, you have:
>>>>
>>>> 4,288,352,511 ÷ 512 = 8,375,688.5
>>>>
>>>> which would place it within your swap partition.
>>>>
>>>> I would do this:
>>>>
>>>>  swapoff /dev/sda2
>>>>
>>>>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>>>
>>>>  mkswap -L swap -c /dev/sda2
>>>>
>>>>  swapon /dev/sda2
>>>>
>>>> and hopefully the problem will be gone when you run the next smartctl test.
>>>>
>>>> -- 
>>>> Regards,
>>>> Mick
>>> Sorry for stuutering postings...overlocked this one:
>>> #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>> dd: error writing ‘/dev/sda2’: Input/output error
>>>
>>> Hrrrmpfff...
>>>
>>> Why does it nt remap those ones?
>>>
>>> Best regards,
>>> mcc
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> smartctl -a /dev/sda
>>
>> without those information: crystal ball.
>>
>> that said: it is swap. You shouldn't have to do anything. Don't touch dd.
>>
>>
>>
>
> Hi Volker,
>
> what happens if swapped is used and the write access tapped on the
> bad area?

nothing. As soon as someone tries to write on that sector, the drive
will map it out.

That means 'pending'. Nobody tried to write on it yet, so the drive had
no reason to 'reallocate' it so far.

> Here is the output of smartctl:
>
>
> smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.13-RT] (local build)
> Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family:     Western Digital Caviar Green (AF)
> Device Model:     WDC WD10EARS-00Y5B1
> Serial Number:    WD-WMAV51276611
> LU WWN Device Id: 5 0014ee 001f5fb47
> Firmware Version: 80.00A80
> User Capacity:    1,000,204,886,016 bytes [1.00 TB]
> Sector Size:      512 bytes logical/physical
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   ATA8-ACS (minor revision not indicated)
> SATA Version is:  SATA 2.6, 3.0 Gb/s
> Local Time is:    Sat Jul 26 14:16:19 2014 CEST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status:  (0x84)	Offline data collection activity
> 					was suspended by an interrupting command from host.
> 					Auto Offline Data Collection: Enabled.
> Self-test execution status:      ( 121)	The previous self-test completed having
> 					the read element of the test failed.
> Total time to complete Offline 
> data collection: 		(19380) seconds.
> Offline data collection
> capabilities: 			 (0x7b) SMART execute Offline immediate.
> 					Auto Offline data collection on/off support.
> 					Suspend Offline collection upon new
> 					command.
> 					Offline surface scan supported.
> 					Self-test supported.
> 					Conveyance Self-test supported.
> 					Selective Self-test supported.
> SMART capabilities:            (0x0003)	Saves SMART data before entering
> 					power-saving mode.
> 					Supports SMART auto save timer.
> Error logging capability:        (0x01)	Error logging supported.
> 					General Purpose Logging supported.
> Short self-test routine 
> recommended polling time: 	 (   2) minutes.
> Extended self-test routine
> recommended polling time: 	 ( 223) minutes.
> Conveyance self-test routine
> recommended polling time: 	 (   5) minutes.
> SCT capabilities: 	       (0x3031)	SCT Status supported.
> 					SCT Feature Control supported.
> 					SCT Data Table supported.
>
> SMART Attributes Data Structure revision number: 16
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
>   3 Spin_Up_Time            0x0027   129   113   021    Pre-fail  Always       -       6508
>   4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3957
>   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
>   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
>   9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       14476
>  10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
>  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
>  12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       3808
> 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       324
> 193 Load_Cycle_Count        0x0032   196   196   000    Old_age   Always       -       14602
> 194 Temperature_Celsius     0x0022   115   101   000    Old_age   Always       -       32
> 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
> 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1
> 198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
> 199 UDMA_CRC_Error_Count    0x0032   200   197   000    Old_age   Always       -       13300
> 200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       1

so you got one defective sector, the drive knows about it, it has 200
spares and will use one when the need arises.

>
> SMART Error Log Version: 1
> No Errors Logged
>
> SMART Self-test log structure revision number 1
> Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
> # 1  Conveyance offline  Completed: read failure       90%     14472         4288352511
> # 2  Extended offline    Completed: read failure       90%     14460         4288352511
> # 3  Extended offline    Completed without error       00%     13954         -
> # 4  Short offline       Completed without error       00%     13935         -
> # 5  Extended offline    Completed without error       00%      7051         -
> # 6  Extended offline    Completed without error       00%      2205         -
> # 7  Short offline       Completed without error       00%       463         -
>
> SMART Selective self-test log data structure revision number 1
>  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
>     1        0        0  Not_testing
>     2        0        0  Not_testing
>     3        0        0  Not_testing
>     4        0        0  Not_testing
>     5        0        0  Not_testing
> Selective self-test flags (0x0):
>   After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0 minute delay.
>
>
> Best regards,
> mcc
>
>
>
>

Re: [gentoo-user] [OT] Badblocks on my harddisk

[meino.cramer]

Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 18:00]:
> Am 26.07.2014 14:16, schrieb meino.cramer@gmx.de:
> > Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 14:08]:
> >> Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
> >>> Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
> >>>> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
> >>>>> Hi,
> >>>>>
> >>>>> After running smartctl for an extended offline test I got
> >>>>> a badblock (information extracted from the report):
> >>>>>
> >>>>> SMART Self-test log structure revision number 1
> >>>>> Num  Test_Description    Status                  Remaining  LifeTime(hours)
> >>>>>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
> >>>>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
> >>>>>  200   000    Old_age   Always       -       1
> >>>>>
> >>>>> I found a explanation to map the LBA to a partition here:
> >>>>> http://smartmontools.sourceforge.net/badblockhowto.html
> >>>>>
> >>>>> My partition layout is:
> >>>>> #> sudo fdisk -lu /dev/sda
> >>>>>
> >>>>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> >>>>> 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: 0x07ec16a2
> >>>>>
> >>>>> Device     Boot      Start        End    Blocks  Id System
> >>>>> /dev/sda1  *          2048     104447     51200  83 Linux
> >>>>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
> >>>>> /dev/sda3         12687360  222402559 104857600  83 Linux
> >>>>> /dev/sda4        222402560 1953525167 865561304   5 Extended
> >>>>> /dev/sda5        222404608  232890367   5242880  83 Linux
> >>>>> /dev/sda6        232892416  442607615 104857600  83 Linux
> >>>>> /dev/sda7        442609664  652324863 104857600  83 Linux
> >>>>> /dev/sda8        652326912  862042111 104857600  83 Linux
> >>>>> /dev/sda9        862044160 1071759359 104857600  83 Linux
> >>>>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
> >>>>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
> >>>>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
> >>>>>                 4288352511  <<< The number reported by smartctl
> >>>>>
> >>>>>
> >>>>> Following the linked document...
> >>>>> It seems the bad LBA is not on the checked harddisk.
> >>>>>
> >>>>> Or (more obvious) I did something wrong...
> >>>> You are probably comparing different units.  The Start and End of fdisk are 
> >>>> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
> >>>> reported by smartctl in bytes, you have:
> >>>>
> >>>> 4,288,352,511 ÷ 512 = 8,375,688.5
> >>>>
> >>>> which would place it within your swap partition.
> >>>>
> >>>> I would do this:
> >>>>
> >>>>  swapoff /dev/sda2
> >>>>
> >>>>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> >>>>
> >>>>  mkswap -L swap -c /dev/sda2
> >>>>
> >>>>  swapon /dev/sda2
> >>>>
> >>>> and hopefully the problem will be gone when you run the next smartctl test.
> >>>>
> >>>> -- 
> >>>> Regards,
> >>>> Mick
> >>> Sorry for stuutering postings...overlocked this one:
> >>> #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
> >>> dd: error writing ‘/dev/sda2’: Input/output error
> >>>
> >>> Hrrrmpfff...
> >>>
> >>> Why does it nt remap those ones?
> >>>
> >>> Best regards,
> >>> mcc
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >> smartctl -a /dev/sda
> >>
> >> without those information: crystal ball.
> >>
> >> that said: it is swap. You shouldn't have to do anything. Don't touch dd.
> >>
> >>
> >>
> >
> so you got one defective sector, the drive knows about it, it has 200
> spares and will use one when the need arises.
> 
> >


Unfortunaltely: No it doesnt.

I did a dd (as reported previously) of zeroes accross the affected
partition and dd fails to write ot the sector in question (IO error).

The selftest following again reports that sector as bad.

So...?

Best regards,
mcc

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Volker Armin Hemmann]

Am 26.07.2014 18:09, schrieb meino.cramer@gmx.de:
> Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 18:00]:
>> Am 26.07.2014 14:16, schrieb meino.cramer@gmx.de:
>>> Volker Armin Hemmann <volkerarmin@googlemail.com> [14-07-26 14:08]:
>>>> Am 26.07.2014 12:26, schrieb meino.cramer@gmx.de:
>>>>> Mick <michaelkintzios@gmail.com> [14-07-26 11:28]:
>>>>>> On Saturday 26 Jul 2014 02:49:15 meino.cramer@gmx.de wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> After running smartctl for an extended offline test I got
>>>>>>> a badblock (information extracted from the report):
>>>>>>>
>>>>>>> SMART Self-test log structure revision number 1
>>>>>>> Num  Test_Description    Status                  Remaining  LifeTime(hours)
>>>>>>>  LBA_of_first_error # 1  Extended offline    Completed: read failure      
>>>>>>> 90%     14460         4288352511 197 Current_Pending_Sector  0x0032   200 
>>>>>>>  200   000    Old_age   Always       -       1
>>>>>>>
>>>>>>> I found a explanation to map the LBA to a partition here:
>>>>>>> http://smartmontools.sourceforge.net/badblockhowto.html
>>>>>>>
>>>>>>> My partition layout is:
>>>>>>> #> sudo fdisk -lu /dev/sda
>>>>>>>
>>>>>>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
>>>>>>> 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: 0x07ec16a2
>>>>>>>
>>>>>>> Device     Boot      Start        End    Blocks  Id System
>>>>>>> /dev/sda1  *          2048     104447     51200  83 Linux
>>>>>>> /dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
>>>>>>> /dev/sda3         12687360  222402559 104857600  83 Linux
>>>>>>> /dev/sda4        222402560 1953525167 865561304   5 Extended
>>>>>>> /dev/sda5        222404608  232890367   5242880  83 Linux
>>>>>>> /dev/sda6        232892416  442607615 104857600  83 Linux
>>>>>>> /dev/sda7        442609664  652324863 104857600  83 Linux
>>>>>>> /dev/sda8        652326912  862042111 104857600  83 Linux
>>>>>>> /dev/sda9        862044160 1071759359 104857600  83 Linux
>>>>>>> /dev/sda10      1071761408 1281476607 104857600  83 Linux
>>>>>>> /dev/sda11      1281478656 1491193855 104857600  83 Linux
>>>>>>> /dev/sda12      1491195904 1953525167 231164632  83 Linux
>>>>>>>                 4288352511  <<< The number reported by smartctl
>>>>>>>
>>>>>>>
>>>>>>> Following the linked document...
>>>>>>> It seems the bad LBA is not on the checked harddisk.
>>>>>>>
>>>>>>> Or (more obvious) I did something wrong...
>>>>>> You are probably comparing different units.  The Start and End of fdisk are 
>>>>>> reporting sectors, each sector being 512 bytes.  Therefore if the LBA is 
>>>>>> reported by smartctl in bytes, you have:
>>>>>>
>>>>>> 4,288,352,511 ÷ 512 = 8,375,688.5
>>>>>>
>>>>>> which would place it within your swap partition.
>>>>>>
>>>>>> I would do this:
>>>>>>
>>>>>>  swapoff /dev/sda2
>>>>>>
>>>>>>  dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>>>>>
>>>>>>  mkswap -L swap -c /dev/sda2
>>>>>>
>>>>>>  swapon /dev/sda2
>>>>>>
>>>>>> and hopefully the problem will be gone when you run the next smartctl test.
>>>>>>
>>>>>> -- 
>>>>>> Regards,
>>>>>> Mick
>>>>> Sorry for stuutering postings...overlocked this one:
>>>>> #>dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc
>>>>> dd: error writing ‘/dev/sda2’: Input/output error
>>>>>
>>>>> Hrrrmpfff...
>>>>>
>>>>> Why does it nt remap those ones?
>>>>>
>>>>> Best regards,
>>>>> mcc
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> smartctl -a /dev/sda
>>>>
>>>> without those information: crystal ball.
>>>>
>>>> that said: it is swap. You shouldn't have to do anything. Don't touch dd.
>>>>
>>>>
>>>>
>> so you got one defective sector, the drive knows about it, it has 200
>> spares and will use one when the need arises.
>>
>
> Unfortunaltely: No it doesnt.
>
> I did a dd (as reported previously) of zeroes accross the affected
> partition and dd fails to write ot the sector in question (IO error).
>
> The selftest following again reports that sector as bad.
>
> So...?
>
> Best regards,
> mcc
>
>
>
>

you can try hdparm's write-sector command to force a reallocation. But I
would backup first. Just in case.

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

On Sat, Jul 26, 2014 at 10:13:25AM +0200, meino.cramer@gmx.de wrote:

> In the meanwhile I found ddrescue... :)
> 
> It took me five hours to copy the disk (1T) binaryly (this word looks
> wrong...)

hm... not a native speaker, but:
binarily?
in binary?

If in doubt, leave it out:
in a binary manner
on a binary level
;)

A friend of mine recently dismissed ddrescue for some reason I can’t
remember anymore. Perhaps because ddrescue is designed for reading optical
discs rather than HDDs.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

Just don’t ignore it.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] [OT] Badblocks on my harddisk

[Stroller]

On Thu, 31 July 2014, at 5:58 pm, Frank Steinmetzger <Warp_7@gmx.de> wrote:

> On Sat, Jul 26, 2014 at 10:13:25AM +0200, meino.cramer@gmx.de wrote:
> 
>> In the meanwhile I found ddrescue... :)
>> 
>> It took me five hours to copy the disk (1T) binaryly (this word looks
>> wrong...)
> 
> hm... not a native speaker, but:
> binarily?
> in binary?
> 
> If in doubt, leave it out:
> in a binary manner
> on a binary level

Bitwise.

Or, in this case, "a block copy".

Stroller.