[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Hard drive bad sector warning



On 11/09/11 23:27, consul tores wrote:
> Adding Slackware test information:
> 
> bash-4.1# fdisk -l
> 
> Disk /dev/sda: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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
> Disk identifier: 0x7221e240
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *        2048     2457599     1227776    7  HPFS/NTFS/exFAT
> /dev/sda2         2457600   311173119   154357760    7  HPFS/NTFS/exFAT
> /dev/sda3       956293120   976771071    10238976    7  HPFS/NTFS/exFAT
> /dev/sda4       311175166   663324926   176074880+   5  Extended
> /dev/sda5       311175168   319571967     4198400   82  Linux swap
> /dev/sda6       319574016   565665791   123045888   83  Linux
> /dev/sda7       565665855   663324926    48829536   83  Linux
> 
> Partition table entries are not in disk order
> bash-4.1# sfdisk -l
> 
> Disk /dev/sda: 60801 cylinders, 255 heads, 63 sectors/track
> Warning: extended partition does not start at a cylinder boundary.
> DOS and Linux will interpret the contents differently.
> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
> 
>    Device Boot Start     End   #cyls    #blocks   Id  System
> /dev/sda1   *      0+    152-    153-   1227776    7  HPFS/NTFS/exFAT
> /dev/sda2        152+  19369-  19217- 154357760    7  HPFS/NTFS/exFAT
> /dev/sda3      59526+  60801-   1275-  10238976    7  HPFS/NTFS/exFAT
> /dev/sda4      19369+  41290-  21921- 176074880+   5  Extended
> /dev/sda5      19369+  19892-    523-   4198400   82  Linux swap
> /dev/sda6      19892+  35211-  15319- 123045888   83  Linux
> /dev/sda7      35211+  41290-   6079-  48829536   83  Linux
> 
>                            cfdisk (util-linux 2.19)
> 
>                               Disk Drive: /dev/sda
>                        Size: 500107862016 bytes, 500.1 GB
>              Heads: 255   Sectors per Track: 63   Cylinders: 60801
> 
>     Name        Flags      Part Type  FS Type          [Label]        Size (MB)
>  ------------------------------------------------------------------------------
>                                       Unusable                             1.05*
>     sda1        Boot        Primary   ntfs            [SYSTEM_DRV]      1257.25*
>     sda2                       Primary   ntfs           [Windows7_OS]
>   158062.35*
>                             Logical   Free Space                           1.05*
>     sda5        NC          Logical   swap                              4299.17*
>     sda6        NC          Logical   ext4             [Debian]       126000.04*
>     sda7                      Logical   reiserfs         [Slackware]
>   50001.48*
>                             Logical   Free Space                      149999.72*
>     sda3                      Primary   ntfs       [Lenovo_Recovery]
>   10484.72*
>                                       Unusable                             1.08*
> 
> 
>      [   Help   ]  [  Print   ]  [   Quit   ]  [  Units   ]  [  Write   ]
> 
> 
>                                Print help screen
> 
> 


When you let MS have first bite at the partitioning, GNU/Linux can only
work with the scraps. And fdisk/sfdisk,and, cfdisk can display sectors
[*1] - which is what Debian "sees" *not* CHS.

[*1] -u,-uS,and,-Ps respectively


I'm unclear as to why display/list/print partitions (in CHS) of your
hard drives has any bearing on the ability of those tools to align
sectors and partitions (the OP already knows it's a manual process ie,
look at sectors and divide by 8).

NOTE: fdisk -b 4096 /dev/whatever will deal with 4K sectors. That
shouldn't be necessary with post-Squeeze releases though.

You may already know this, but I found it instructive, from man fdisk:-

There are several *fdisk programs around. Each has its problems and
strengths. Try them in the order cfdisk, fdisk, sfdisk.
Indeed, cfdisk is a beautiful program that has strict requirements on
the partition tables it accepts, and produces high quality partition
tables. Use it if you can.
fdisk is a buggy program that does fuzzy  things - usually it happens to
produce reasonable results. Its single advantage is that it has some
support for BSD disk labels and  other non-DOS partition tables. Avoid
it if you can.
sfdisk is for hackers only - the user interface is terrible, but it is
more correct than fdisk and more powerful than both fdisk and cfdisk.
Moreover, it can be used noninteractively.)
These days there also is parted. The cfdisk interface is nicer, but
parted does much more: it not only resizes partitions, but also the
filesystems that live in them.


Cheers

-- 
"They proved that if you quit smoking, it will prolong your life. What
they haven’t proved is that a prolonged life is a good thing. I haven’t
seen the stats on that yet."
— Bill Hicks


Reply to: