FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 09-28-2012, 02:36 PM
Albretch Mueller
 
Default why would fdisk -l take so long?

I just backed up all the data
~
Yet, it seems something else may be (also?) somehow relating to those
delays. Since I start knoppix 7.0.2 as:
~
knoppix no3d fromhd=/dev/sda9
~
could these issues/problems relate to the fact that /dev/sda9 is
mounted read-only and knoppix keeps it to itself throughout its
running time?
~
See bellow the fdisk -l timings when I run knoppix from the dvd
~
lbrtchx

// __ fdisk -l

$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:26 UTC 2012
real 0m0.014s
$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:28 UTC 2012
real 0m0.012s
$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:29 UTC 2012
real 0m0.012s
$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:29 UTC 2012
real 0m0.013s

// __ fdisk -l /dev/sda

$ date; X=`(time fdisk -l /dev/sda) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:35 UTC 2012
real 0m0.002s
$ date; X=`(time fdisk -l /dev/sda) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:36 UTC 2012
real 0m0.002s
$ date; X=`(time fdisk -l /dev/sda) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:37 UTC 2012
real 0m0.002s
$ date; X=`(time fdisk -l /dev/sda) 2>&1 | grep real`; echo $X
Fri Sep 28 10:20:38 UTC 2012
real 0m0.002s


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAFakBwhnYgFAoEuuCFf-3oCsKJ+HiN=y4cgxcPeFHNwM_VBB_w@mail.gmail.com
 
Old 09-28-2012, 03:10 PM
Dom
 
Default why would fdisk -l take so long?

On 28/09/12 13:52, Jon Dowland wrote:

On Fri, Sep 28, 2012 at 01:23:59PM +0100, Dom wrote:

It *is* possible that smartctl is mis-interpretting the status of
your disk, but given your slow fdisk command I suspect not.

Time to backup, backup, backup, buy a new disk and transfer the data
over asap.


YES to backup, but it's worth changing your SATA cable before investing
in a new disk, or at least ensuring your current one is seated properly.
Try to measure the *rate* that Hardware_ECC_Recovered is increasing over
a set period of time, check/replace cable, measure again.



Good points, which I did think of *after* I'd posted my comment.

Good catch. :-)

--
Dom


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 5065BDF9.1040500@rpdom.net">http://lists.debian.org/5065BDF9.1040500@rpdom.net
 
Old 09-28-2012, 03:21 PM
Albretch Mueller
 
Default why would fdisk -l take so long?

in a box in which I use the fromhd stanza using a disk which smartclt
reports as being fine the results before and after suspending are the
same
~
this is what the dying disk reports
~
$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:52:58 UTC 2012
real 0m0.191s
$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:52:59 UTC 2012
real 0m0.055s
$ date; X=`(time fdisk -l) 2>&1 | grep real`; echo $X
Fri Sep 28 10:53:00 UTC 2012
real 0m0.052s
~
it then stabilize around 0.050s
~
For the good ones time consistently reports 0.003s
~
the thing is (for more than one reason) I use a crappy box to go online
~
Also, any comprehensive documentation regarding hd's health?
smartctl's is OK to get by, but you are telling me about logs I don't
know about and I would like to know more about the physics of it
~
lbrtchx


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAFakBwjq=rD5G_SRLx=J7WakOcTyp2nuA9xgK-yEYgEXdS1bNQ@mail.gmail.com
 
Old 09-28-2012, 06:48 PM
Neal Murphy
 
Default why would fdisk -l take so long?

On Friday, September 28, 2012 08:23:59 AM Dom wrote:
> > 1 Raw_Read_Error_Rate 0x000f 115 082 006 Pre-fail
> >
> > Always - 96695847
>
> Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
> low.


Not necessarily. At least one disk mfr (Seagate?) puts large values in these
fields. Cause me a few moments' consternation the first time I saw it on my
own drives....


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201209281448.32568.neal.p.murphy@alum.wpi.edu">htt p://lists.debian.org/201209281448.32568.neal.p.murphy@alum.wpi.edu
 
Old 09-29-2012, 12:58 AM
Albretch Mueller
 
Default why would fdisk -l take so long?

> > > 1 Raw_Read_Error_Rate 0x000f 115 082 006 Pre-fail
> > >
> > > Always - 96695847
> >
> > Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
> > low.

> Not necessarily. At least one disk mfr (Seagate?) puts large values in these
> fields. Cause me a few moments' consternation the first time I saw it on my
> own drives....
~
Indeed! Something "spooky" may be going on. After taking the drive
out in order to back it up, I have run "fdisk -l" with no disk and
sometimes with a pen drive inserted and these bellow are the results I
got.
~
Don't you find all of this downright weird?
~
I don't believe in ghosts ;-) What do you think I could do to
troubleshoot this further?
~
lbrtchx
~

$ time fdisk -l

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m38.106s
user 0m0.000s
sys 0m0.000s

$ mount /media/sda1

$ time fdisk -l
konqueror(2828)/kdecore (KLibrary) findLibraryInternal: plugins should
not have a 'lib' prefix: "libkhtmlpart.so"
konqueror(2828)/kdecore (KLibrary) kde4Factory: The library
"/usr/lib/kde4/khtml_kget.so" does not offer a qt_plugin_instance
function.

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m38.107s
user 0m0.000s
sys 0m0.000s

$ sudo umount /media/sda1

$ time fdisk -l

real 0m38.314s
user 0m0.000s
sys 0m0.000s

$ _DT=`date +%Y%m%d%H%M%S`; dmesg > dmesg_${_DT}.log

$ date; time fdisk -l; date
Fri Sep 28 20:51:09 UTC 2012

real 0m38.097s
user 0m0.000s
sys 0m0.000s
Fri Sep 28 20:51:47 UTC 2012

$ _DT=`date +%Y%m%d%H%M%S`; dmesg > dmesg_${_DT}.log

$ ls -l dmesg_*.log
-rw-r--r-- 1 knoppix knoppix 15493 Sep 28 20:50 dmesg_20120928205055.log
-rw-r--r-- 1 knoppix knoppix 15490 Sep 28 20:51 dmesg_20120928205157.log

$ wc -l dmesg_*.log
298 dmesg_20120928205055.log
299 dmesg_20120928205157.log
597 total

$ diff dmesg_20120928205055.log dmesg_20120928205157.log
1c1
< 090] ehci_hcd 0000:00:13.2: wake-up capability enabled by ACPI
---
> PI
298a299
> [26607.877660] end_request: I/O error, dev fd0, sector 0
$

$ cat dmesg_20120928205055.log
090] ehci_hcd 0000:00:13.2: wake-up capability enabled by ACPI
[ 4008.172988] ohci_hcd 0000:00:13.1: wake-up capability enabled by ACPI
[ 4008.173025] ohci_hcd 0000:00:13.0: wake-up capability enabled by ACPI
[ 4008.173066] PM: late suspend of devices complete after 13.416 msecs
[ 4008.173239] ACPI: Preparing to enter system sleep state S3
[ 4008.173322] PM: Saving platform NVS memory
[ 4008.173361] Disabling non-boot CPUs ...
[ 4008.173361] ACPI: Low-level resume complete
[ 4008.173361] PM: Restoring platform NVS memory
[ 4008.173361] ACPI: Waking up from system sleep state S3
[ 4008.173361] ohci_hcd 0000:00:13.0: wake-up capability disabled by ACPI
[ 4008.173361] ohci_hcd 0000:00:13.1: wake-up capability disabled by ACPI
[ 4008.173361] ehci_hcd 0000:00:13.2: wake-up capability disabled by ACPI
[ 4008.173361] PM: early resume of devices complete after 0.718 msecs
[ 4008.176363] pci0000:00: wake-up capability disabled by ACPI
[ 4008.176442] radeon 0000:01:00.0: f529d800 unpin not necessary
[ 4008.178326] serial 00:08: activated
[ 4008.178771] parport_pc 00:09: activated
[ 4008.189307] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[ 4008.201519] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 4008.201531] radeon 0000:01:00.0: WB enabled
[ 4008.201534] [drm] fence driver on ring 0 use gpu addr 0x10000000
and cpu addr 0xff885000
[ 4008.201621] [drm] radeon: ring at 0x0000000010001000
[ 4008.201651] [drm] ring test succeeded in 7 usecs
[ 4008.201667] [drm] ib test succeeded in 0 usecs
[ 4008.496304] ata2: SATA link down (SStatus 0 SControl 300)
[ 4008.496352] ata1: SATA link down (SStatus 0 SControl 300)
[ 4008.600352] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 4008.600356] ata3.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES)
filtered out
[ 4008.600360] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
LOCK) filtered out
[ 4008.606911] ata3.00: configured for UDMA/33
[ 4013.233591] psmouse serio1: hgpk: ID: 10 00 64
[ 4015.679626]
[ 4015.679628] floppy driver state
[ 4015.679629] -------------------
[ 4015.679637] now=1114704 last interrupt=1109734 diff=4970 last
called handler=recal_interrupt
[ 4015.679639] timeout_message=lock fdc
[ 4015.679641] last output bytes:
[ 4015.679642] 18 80 4294884748
[ 4015.679644] 8 80 4294884748
[ 4015.679646] 8 80 4294884748
[ 4015.679647] 8 80 4294884748
[ 4015.679649] 8 80 4294884748
[ 4015.679650] 12 80 1109103
[ 4015.679652] 0 90 1109103
[ 4015.679654] 13 90 1109103
[ 4015.679655] 0 90 1109103
[ 4015.679657] 1a 90 1109103
[ 4015.679658] 0 90 1109103
[ 4015.679660] 3 80 1109103
[ 4015.679661] c1 90 1109103
[ 4015.679663] 10 90 1109103
[ 4015.679664] 7 80 1109103
[ 4015.679666] 0 90 1109103
[ 4015.679667] 8 81 1109416
[ 4015.679669] 7 80 1109422
[ 4015.679670] 0 90 1109422
[ 4015.679672] 8 81 1109734
[ 4015.679673] last result at 1109734
[ 4015.679675] last redo_fd_request at 1109734
[ 4015.679678] 70 00 p.
[ 4015.679688] status=0
[ 4015.679690] fdc_busy=1
[ 4015.679693] do_floppy=reset_interrupt
[ 4015.679695] cont=f85786c8
[ 4015.679696] current_req= (null)
[ 4015.679698] command_status=-1
[ 4015.679699]
[ 4015.679702] floppy0: floppy timeout called
[ 4015.679728] PM: resume of devices complete after 7505.422 msecs
[ 4015.679993] Restarting tasks ... done.
[ 4016.344219] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4017.991261] tg3 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex
[ 4017.991265] tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX
[ 4017.991444] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 4022.384998] VFS: busy inodes on changed media or resized disk sr0
[ 4028.243349] pci0000:00: wake-up capability enabled by ACPI
[ 4029.510195] PM: Syncing filesystems ... done.
[ 4029.549399] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 4029.562992] Freezing remaining freezable tasks ... (elapsed 0.01
seconds) done.
[ 4029.576323] Suspending console(s) (use no_console_suspend to debug)
[ 4029.592049] parport_pc 00:09: disabled
[ 4029.592094] serial 00:08: disabled
[ 4029.592101] serial 00:08: wake-up capability disabled by ACPI
[ 4029.686307] PM: suspend of devices complete after 109.713 msecs
[ 4029.686769] ehci_hcd 0000:00:13.2: wake-up capability enabled by ACPI
[ 4029.699653] ohci_hcd 0000:00:13.1: wake-up capability enabled by ACPI
[ 4029.699691] ohci_hcd 0000:00:13.0: wake-up capability enabled by ACPI
[ 4029.699748] PM: late suspend of devices complete after 13.436 msecs
[ 4029.699903] ACPI: Preparing to enter system sleep state S3
[ 4029.699986] PM: Saving platform NVS memory
[ 4029.700025] Disabling non-boot CPUs ...
[ 4029.700025] ACPI: Low-level resume complete
[ 4029.700025] PM: Restoring platform NVS memory
[ 4029.700025] ACPI: Waking up from system sleep state S3
[ 4029.700025] ohci_hcd 0000:00:13.0: wake-up capability disabled by ACPI
[ 4029.700025] ohci_hcd 0000:00:13.1: wake-up capability disabled by ACPI
[ 4029.700025] ehci_hcd 0000:00:13.2: wake-up capability disabled by ACPI
[ 4029.700025] PM: early resume of devices complete after 0.718 msecs
[ 4029.702970] pci0000:00: wake-up capability disabled by ACPI
[ 4029.703782] radeon 0000:01:00.0: f529d800 unpin not necessary
[ 4029.705666] serial 00:08: activated
[ 4029.706117] parport_pc 00:09: activated
[ 4029.715986] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[ 4029.728227] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 4029.728238] radeon 0000:01:00.0: WB enabled
[ 4029.728242] [drm] fence driver on ring 0 use gpu addr 0x10000000
and cpu addr 0xff885000
[ 4029.728323] [drm] radeon: ring at 0x0000000010001000
[ 4029.728353] [drm] ring test succeeded in 7 usecs
[ 4029.728369] [drm] ib test succeeded in 0 usecs
[ 4030.022968] ata1: SATA link down (SStatus 0 SControl 300)
[ 4030.023023] ata2: SATA link down (SStatus 0 SControl 300)
[ 4030.123682] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 4030.123686] ata3.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES)
filtered out
[ 4030.123690] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
LOCK) filtered out
[ 4030.130246] ata3.00: configured for UDMA/33
[ 4034.742160] psmouse serio1: hgpk: ID: 10 00 64
[ 4037.159610]
[ 4037.159611] floppy driver state
[ 4037.159612] -------------------
[ 4037.159621] now=1121148 last interrupt=1109734 diff=11414 last
called handler=recal_interrupt
[ 4037.159623] timeout_message=lock fdc
[ 4037.159624] last output bytes:
[ 4037.159626] 18 80 4294884748
[ 4037.159627] 8 80 4294884748
[ 4037.159629] 8 80 4294884748
[ 4037.159631] 8 80 4294884748
[ 4037.159632] 8 80 4294884748
[ 4037.159634] 12 80 1109103
[ 4037.159635] 0 90 1109103
[ 4037.159637] 13 90 1109103
[ 4037.159638] 0 90 1109103
[ 4037.159640] 1a 90 1109103
[ 4037.159641] 0 90 1109103
[ 4037.159643] 3 80 1109103
[ 4037.159644] c1 90 1109103
[ 4037.159646] 10 90 1109103
[ 4037.159648] 7 80 1109103
[ 4037.159649] 0 90 1109103
[ 4037.159651] 8 81 1109416
[ 4037.159652] 7 80 1109422
[ 4037.159654] 0 90 1109422
[ 4037.159655] 8 81 1109734
[ 4037.159656] last result at 1109734
[ 4037.159658] last redo_fd_request at 1114709
[ 4037.159661] 70 00 p.
[ 4037.159671] status=0
[ 4037.159672] fdc_busy=1
[ 4037.159676] do_floppy=reset_interrupt
[ 4037.159677] cont=f85786c8
[ 4037.159679] current_req= (null)
[ 4037.159680] command_status=-1
[ 4037.159682]
[ 4037.159685] floppy0: floppy timeout called
[ 4037.159710] PM: resume of devices complete after 7458.742 msecs
[ 4037.159974] Restarting tasks ... done.
[ 4037.841340] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4039.516162] tg3 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex
[ 4039.516167] tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX
[ 4039.516372] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 4045.722015] VFS: busy inodes on changed media or resized disk sr0
[ 4049.776279] eth0: no IPv6 routers present
[11748.795912] pci0000:00: wake-up capability enabled by ACPI
[11750.060904] PM: Syncing filesystems ... done.
[11750.098608] Freezing user space processes ... (elapsed 0.01 seconds) done.
[11750.112218] Freezing remaining freezable tasks ... (elapsed 0.01
seconds) done.
[11750.125548] Suspending console(s) (use no_console_suspend to debug)
[11750.140643] parport_pc 00:09: disabled
[11750.140689] serial 00:08: disabled
[11750.140695] serial 00:08: wake-up capability disabled by ACPI
[11750.235535] PM: suspend of devices complete after 109.713 msecs
[11750.236002] ehci_hcd 0000:00:13.2: wake-up capability enabled by ACPI
[11750.248880] ohci_hcd 0000:00:13.1: wake-up capability enabled by ACPI
[11750.248918] ohci_hcd 0000:00:13.0: wake-up capability enabled by ACPI
[11750.248981] PM: late suspend of devices complete after 13.440 msecs
[11750.249142] ACPI: Preparing to enter system sleep state S3
[11750.249224] PM: Saving platform NVS memory
[11750.249263] Disabling non-boot CPUs ...
[11750.249263] ACPI: Low-level resume complete
[11750.249263] PM: Restoring platform NVS memory
[11750.249263] ACPI: Waking up from system sleep state S3
[11750.249263] ohci_hcd 0000:00:13.0: wake-up capability disabled by ACPI
[11750.249263] ohci_hcd 0000:00:13.1: wake-up capability disabled by ACPI
[11750.249263] ehci_hcd 0000:00:13.2: wake-up capability disabled by ACPI
[11750.249263] PM: early resume of devices complete after 0.718 msecs
[11750.252257] pci0000:00: wake-up capability disabled by ACPI
[11750.252335] radeon 0000:01:00.0: f529d800 unpin not necessary
[11750.254216] serial 00:08: activated
[11750.254648] parport_pc 00:09: activated
[11750.265199] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[11750.277411] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[11750.277423] radeon 0000:01:00.0: WB enabled
[11750.277427] [drm] fence driver on ring 0 use gpu addr 0x10000000
and cpu addr 0xff885000
[11750.277511] [drm] radeon: ring at 0x0000000010001000
[11750.277541] [drm] ring test succeeded in 7 usecs
[11750.277557] [drm] ib test succeeded in 0 usecs
[11750.572197] ata2: SATA link down (SStatus 0 SControl 300)
[11750.572245] ata1: SATA link down (SStatus 0 SControl 300)
[11750.676244] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[11750.676248] ata3.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES)
filtered out
[11750.676252] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
LOCK) filtered out
[11750.682804] ata3.00: configured for UDMA/33
[11755.300321] psmouse serio1: hgpk: ID: 10 00 64
[11757.745503]
[11757.745504] floppy driver state
[11757.745505] -------------------
[11757.745513] now=3437324 last interrupt=1109734 diff=2327590 last
called handler=recal_interrupt
[11757.745515] timeout_message=lock fdc
[11757.745517] last output bytes:
[11757.745518] 18 80 4294884748
[11757.745520] 8 80 4294884748
[11757.745522] 8 80 4294884748
[11757.745523] 8 80 4294884748
[11757.745525] 8 80 4294884748
[11757.745527] 12 80 1109103
[11757.745528] 0 90 1109103
[11757.745530] 13 90 1109103
[11757.745531] 0 90 1109103
[11757.745533] 1a 90 1109103
[11757.745534] 0 90 1109103
[11757.745536] 3 80 1109103
[11757.745537] c1 90 1109103
[11757.745539] 10 90 1109103
[11757.745540] 7 80 1109103
[11757.745542] 0 90 1109103
[11757.745544] 8 81 1109416
[11757.745545] 7 80 1109422
[11757.745547] 0 90 1109422
[11757.745548] 8 81 1109734
[11757.745550] last result at 1109734
[11757.745551] last redo_fd_request at 1121152
[11757.745554] 70 00 p.
[11757.745564] status=0
[11757.745566] fdc_busy=1
[11757.745569] do_floppy=reset_interrupt
[11757.745571] cont=f85786c8
[11757.745572] current_req= (null)
[11757.745574] command_status=-1
[11757.745575]
[11757.745578] floppy0: floppy timeout called
[11757.745604] PM: resume of devices complete after 7495.396 msecs
[11757.745866] Restarting tasks ... done.
[11758.374389] VFS: busy inodes on changed media or resized disk sr0
[11758.376145] ADDRCONF(NETDEV_UP): eth0: link is not ready
[11760.048064] tg3 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex
[11760.048068] tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX
[11760.048247] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[11770.228921] eth0: no IPv6 routers present
[11952.768836] usb 1-8: new high-speed USB device number 4 using ehci_hcd
[11952.898331] usb 1-8: New USB device found, idVendor=0930, idProduct=6545
[11952.898334] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11952.898337] usb 1-8: Product: DT 101 G2
[11952.898340] usb 1-8: Manufacturer: Kingston
[11952.898342] usb 1-8: SerialNumber: 001CC0C83B35EB61142A011A
[11952.899440] scsi6 : usb-storage 1-8:1.0
[11953.948116] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2
PMAP PQ: 0 ANSI: 0 CCS
[11953.948296] sd 6:0:0:0: Attached scsi generic sg1 type 0
[11954.607947] sd 6:0:0:0: [sda] 15638528 512-byte logical blocks:
(8.00 GB/7.45 GiB)
[11954.610064] sd 6:0:0:0: [sda] Write Protect is off
[11954.610068] sd 6:0:0:0: [sda] Mode Sense: 23 00 00 00
[11954.612344] sd 6:0:0:0: [sda] No Caching mode page present
[11954.612347] sd 6:0:0:0: [sda] Assuming drive cache: write through
[11954.619566] sd 6:0:0:0: [sda] No Caching mode page present
[11954.619569] sd 6:0:0:0: [sda] Assuming drive cache: write through
[11954.641593] sda: sda1
[11954.647337] sd 6:0:0:0: [sda] No Caching mode page present
[11954.647342] sd 6:0:0:0: [sda] Assuming drive cache: write through
[11954.647345] sd 6:0:0:0: [sda] Attached SCSI removable disk
[12011.869055] end_request: I/O error, dev fd0, sector 0
[12097.222509] end_request: I/O error, dev fd0, sector 0
[12150.892906] end_request: I/O error, dev fd0, sector 0
[12209.992320] end_request: I/O error, dev fd0, sector 0
[22999.715096] usb 1-8: USB disconnect, device number 4
[22999.974401] usb 1-8: new high-speed USB device number 5 using ehci_hcd
[23000.494403] usb 1-8: device not accepting address 5, error -71
[23000.547764] hub 1-0:1.0: unable to enumerate USB device on port 8
[23431.424360] usb 1-8: new high-speed USB device number 7 using ehci_hcd
[23431.553861] usb 1-8: New USB device found, idVendor=0930, idProduct=6545
[23431.553866] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23431.553869] usb 1-8: Product: DT 101 G2
[23431.553871] usb 1-8: Manufacturer: Kingston
[23431.553874] usb 1-8: SerialNumber: 001CC0C83B35EB61142A011A
[23431.555077] scsi7 : usb-storage 1-8:1.0
[23432.603528] scsi 7:0:0:0: Direct-Access Kingston DT 101 G2
PMAP PQ: 0 ANSI: 0 CCS
[23432.603703] sd 7:0:0:0: Attached scsi generic sg1 type 0
[23433.241968] sd 7:0:0:0: [sda] 15638528 512-byte logical blocks:
(8.00 GB/7.45 GiB)
[23433.244088] sd 7:0:0:0: [sda] Write Protect is off
[23433.244091] sd 7:0:0:0: [sda] Mode Sense: 23 00 00 00
[23433.246215] sd 7:0:0:0: [sda] No Caching mode page present
[23433.246218] sd 7:0:0:0: [sda] Assuming drive cache: write through
[23433.253714] sd 7:0:0:0: [sda] No Caching mode page present
[23433.253718] sd 7:0:0:0: [sda] Assuming drive cache: write through
[23433.275741] sda: sda1
[23433.281860] sd 7:0:0:0: [sda] No Caching mode page present
[23433.281865] sd 7:0:0:0: [sda] Assuming drive cache: write through
[23433.281869] sd 7:0:0:0: [sda] Attached SCSI removable disk
[25983.383683] usb 1-8: USB disconnect, device number 7
[26199.587825] end_request: I/O error, dev fd0, sector 0
$


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAFakBwgSAch+7UirbRdWw=-A+3dxBDb8GZHE4XvgRBf53PRoMw@mail.gmail.com
 
Old 09-29-2012, 01:34 AM
Neal Murphy
 
Default why would fdisk -l take so long?

On Friday, September 28, 2012 08:58:47 PM Albretch Mueller wrote:
> > > > 1 Raw_Read_Error_Rate 0x000f 115 082 006 Pre-fail
> > > >
> > > > Always - 96695847
> > >
> > > Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
> > > low.
> >
> > Not necessarily. At least one disk mfr (Seagate?) puts large values in
> > these fields. Cause me a few moments' consternation the first time I saw
> > it on my own drives....
>
> ~
> Indeed! Something "spooky" may be going on. After taking the drive
> out in order to back it up, I have run "fdisk -l" with no disk and
> sometimes with a pen drive inserted and these bellow are the results I
> got.
> ~
> Don't you find all of this downright weird?

Not yet.

> ~
> I don't believe in ghosts ;-) What do you think I could do to
> troubleshoot this further?

Have you tried "fdisk -l /dev/sda"? I think you did, to no avail. It might be
searching some other drive or type of drive first that is slow to respond.

Check the drive's power state:
hdparm -C /dev/sda

How about:
tail -f /var/log/messages # In a separate window
time dd if=/dev/sda of=/dev/null bs=1024k count=1
time fdisk -l /dev/sda
to see if the drive is dozing.

Or (from hdparm's man page: Disable the automatic power-saving
function of certain Seagate drives...):
hdparm -Z /dev/sda


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201209282134.29827.neal.p.murphy@alum.wpi.edu">htt p://lists.debian.org/201209282134.29827.neal.p.murphy@alum.wpi.edu
 
Old 09-29-2012, 02:14 AM
Albretch Mueller
 
Default why would fdisk -l take so long?

~
I think there may be a number of things going on here. Let me first
answer Neal's questions:
~
> Have you tried "fdisk -l /dev/sda"?
~
Well, there are no disk attached whatsoever to my box. I am using a
bear live CD (knoppix 7.0.2) right off the DVD drive
~
> How about:
> tail -f /var/log/messages # In a separate window
~
file seems to be empty
~
$ date; time sudo ls -l /KNOPPIX/var/log/messages
Fri Sep 28 21:55:38 UTC 2012
-rw-r----- 1 syslog adm 0 May 13 02:17 /KNOPPIX/var/log/messages

real 0m0.012s
user 0m0.000s
sys 0m0.007s
~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~ ~ ~ ~ ~ ~
~
Without having any drive attached I booted into init 2 using:
~
"boot: knoppix no3d init 2"
~
and fdisk -l was returning with timings bellow 0.010s. Then I
suspended the box (again no hard drives attached whatsoever) and after
awakening the box "fdisk -l" started giving me the "38+ seconds"
responses
~
So it may not be a hard drive dying issue after all. Am I the only
debian user suspending his box to whom that happens?
~
lbrtchx
~
$ date; time fdisk -l
Fri Sep 28 21:14:08 UTC 2012
real 0m0.009s

$ date; time fdisk -l
Fri Sep 28 21:14:10 UTC 2012
real 0m0.009s

$ date; time fdisk -l
Fri Sep 28 21:14:11 UTC 2012
real 0m0.009s
sys 0m0.003s

$ date; time fdisk -l
Fri Sep 28 21:14:12 UTC 2012
real 0m0.009s

$ sudo mount /media/sda1

$ date; time fdisk -l
Fri Sep 28 21:14:45 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.017s

$ date; time fdisk -l
Fri Sep 28 21:14:49 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.015s

$ date; time fdisk -l
Fri Sep 28 21:14:50 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.013s

$ date; time fdisk -l
Fri Sep 28 21:14:51 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.014s

$ sudo umount /media/sda1

$ date; time fdisk -l
Fri Sep 28 21:15:02 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.025s
user 0m0.003s

$ date; time fdisk -l
Fri Sep 28 21:15:03 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.022s

$ date; time fdisk -l
Fri Sep 28 21:15:04 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.024s

$ date; time fdisk -l
Fri Sep 28 21:15:04 UTC 2012

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 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: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sda1 * 8064 15638527 7815232 c W95 FAT32 (LBA)

real 0m0.023s

$ date; time fdisk -l
Fri Sep 28 21:17:47 UTC 2012
real 0m0.009s

$ date; time fdisk -l
Fri Sep 28 21:17:51 UTC 2012
real 0m0.009s

$ date; time fdisk -l
Fri Sep 28 21:17:54 UTC 2012
real 0m0.009s

$ date; time fdisk -l
Fri Sep 28 21:17:57 UTC 2012
real 0m0.011s

$ date; time fdisk -l
Fri Sep 28 21:19:58 UTC 2012
real 0m0.011s

$ date; time fdisk -l
Fri Sep 28 21:20:00 UTC 2012
real 0m0.009s

$ date; time fdisk -l
Fri Sep 28 21:20:01 UTC 2012
real 0m0.009s

~ ~ ~ ~ ~ ~ ~ after suspending box for about 10 seconds ~ ~ ~ ~ ~ ~ ~

$ date; time fdisk -l
Fri Sep 28 21:21:09 UTC 2012
real 0m38.089s

$ date; time fdisk -l
Fri Sep 28 21:22:23 UTC 2012
real 0m38.093s

$ date; time fdisk -l
Fri Sep 28 21:23:12 UTC 2012
real 0m38.095s

$ date; time fdisk -l
Fri Sep 28 21:23:58 UTC 2012
real 0m38.101s


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAFakBwh6PH3a2JN+FSW2OhnZrSa+AnAY74-wkZs9eSk_YANLMw@mail.gmail.com">http://lists.debian.org/CAFakBwh6PH3a2JN+FSW2OhnZrSa+AnAY74-wkZs9eSk_YANLMw@mail.gmail.com
 
Old 09-29-2012, 06:52 AM
Albretch Mueller
 
Default why would fdisk -l take so long?

> Or (from hdparm's man page: Disable the automatic power-saving
> function of certain Seagate drives...):
> hdparm -Z /dev/sda

# hdparm -Z /dev/sda

/dev/sda:
disabling Seagate auto powersaving mode
HDIO_DRIVE_CMD(seagatepwrsave) failed: Input/output error

lbrtchx


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAFakBwjz5c7LhwsegNnTLK4LDC2dsuURBExDLVJnfGuzN9Z8E Q@mail.gmail.com">http://lists.debian.org/CAFakBwjz5c7LhwsegNnTLK4LDC2dsuURBExDLVJnfGuzN9Z8E Q@mail.gmail.com
 
Old 09-29-2012, 10:29 AM
Martin Steigerwald
 
Default why would fdisk -l take so long?

Hi Albrecht!

Am Samstag, 29. September 2012 schrieb Albretch Mueller:
[…]
> [11750.572197] ata2: SATA link down (SStatus 0 SControl 300)
> [11750.572245] ata1: SATA link down (SStatus 0 SControl 300)
> [11750.676244] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
> filtered out
> [11750.676248] ata3.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES)
> filtered out
> [11750.676252] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
> LOCK) filtered out
> [11750.682804] ata3.00: configured for UDMA/33
> [11755.300321] psmouse serio1: hgpk: ID: 10 00 64
> [11757.745503]
> [11757.745504] floppy driver state
> [11757.745505] -------------------
> [11757.745513] now=3437324 last interrupt=1109734 diff=2327590 last
> called handler=recal_interrupt
> [11757.745515] timeout_message=lock fdc
> [11757.745517] last output bytes:
> [11757.745518] 18 80 4294884748
> [11757.745520] 8 80 4294884748
> [11757.745522] 8 80 4294884748
> [11757.745523] 8 80 4294884748
> [11757.745525] 8 80 4294884748
> [11757.745527] 12 80 1109103
> [11757.745528] 0 90 1109103
> [11757.745530] 13 90 1109103
> [11757.745531] 0 90 1109103
> [11757.745533] 1a 90 1109103
> [11757.745534] 0 90 1109103
> [11757.745536] 3 80 1109103
> [11757.745537] c1 90 1109103
> [11757.745539] 10 90 1109103
> [11757.745540] 7 80 1109103
> [11757.745542] 0 90 1109103
> [11757.745544] 8 81 1109416
> [11757.745545] 7 80 1109422
> [11757.745547] 0 90 1109422
> [11757.745548] 8 81 1109734
> [11757.745550] last result at 1109734
> [11757.745551] last redo_fd_request at 1121152
> [11757.745554] 70 00 p.
> [11757.745564] status=0
> [11757.745566] fdc_busy=1
> [11757.745569] do_floppy=reset_interrupt
> [11757.745571] cont=f85786c8
> [11757.745572] current_req= (null)
> [11757.745574] command_status=-1
> [11757.745575]
> [11757.745578] floppy0: floppy timeout called
> [11757.745604] PM: resume of devices complete after 7495.396 msecs
> [11757.745866] Restarting tasks ... done.
> [11758.374389] VFS: busy inodes on changed media or resized disk sr0
> [11758.376145] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [11760.048064] tg3 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex
> [11760.048068] tg3 0000:02:00.0: eth0: Flow control is on for TX and on for RX
> [11760.048247] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [11770.228921] eth0: no IPv6 routers present
> [11952.768836] usb 1-8: new high-speed USB device number 4 using ehci_hcd
> [11952.898331] usb 1-8: New USB device found, idVendor=0930, idProduct=6545
> [11952.898334] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [11952.898337] usb 1-8: Product: DT 101 G2
> [11952.898340] usb 1-8: Manufacturer: Kingston
> [11952.898342] usb 1-8: SerialNumber: 001CC0C83B35EB61142A011A
> [11952.899440] scsi6 : usb-storage 1-8:1.0
> [11953.948116] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2
> PMAP PQ: 0 ANSI: 0 CCS
> [11953.948296] sd 6:0:0:0: Attached scsi generic sg1 type 0
> [11954.607947] sd 6:0:0:0: [sda] 15638528 512-byte logical blocks:
> (8.00 GB/7.45 GiB)
> [11954.610064] sd 6:0:0:0: [sda] Write Protect is off
> [11954.610068] sd 6:0:0:0: [sda] Mode Sense: 23 00 00 00
> [11954.612344] sd 6:0:0:0: [sda] No Caching mode page present
> [11954.612347] sd 6:0:0:0: [sda] Assuming drive cache: write through
> [11954.619566] sd 6:0:0:0: [sda] No Caching mode page present
> [11954.619569] sd 6:0:0:0: [sda] Assuming drive cache: write through
> [11954.641593] sda: sda1
> [11954.647337] sd 6:0:0:0: [sda] No Caching mode page present
> [11954.647342] sd 6:0:0:0: [sda] Assuming drive cache: write through
> [11954.647345] sd 6:0:0:0: [sda] Attached SCSI removable disk
> [12011.869055] end_request: I/O error, dev fd0, sector 0
> [12097.222509] end_request: I/O error, dev fd0, sector 0
> [12150.892906] end_request: I/O error, dev fd0, sector 0
> [12209.992320] end_request: I/O error, dev fd0, sector 0
> [22999.715096] usb 1-8: USB disconnect, device number 4
> [22999.974401] usb 1-8: new high-speed USB device number 5 using ehci_hcd
> [23000.494403] usb 1-8: device not accepting address 5, error -71
> [23000.547764] hub 1-0:1.0: unable to enumerate USB device on port 8
> [23431.424360] usb 1-8: new high-speed USB device number 7 using ehci_hcd
> [23431.553861] usb 1-8: New USB device found, idVendor=0930, idProduct=6545
> [23431.553866] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [23431.553869] usb 1-8: Product: DT 101 G2
> [23431.553871] usb 1-8: Manufacturer: Kingston
> [23431.553874] usb 1-8: SerialNumber: 001CC0C83B35EB61142A011A
> [23431.555077] scsi7 : usb-storage 1-8:1.0
> [23432.603528] scsi 7:0:0:0: Direct-Access Kingston DT 101 G2
> PMAP PQ: 0 ANSI: 0 CCS
> [23432.603703] sd 7:0:0:0: Attached scsi generic sg1 type 0
> [23433.241968] sd 7:0:0:0: [sda] 15638528 512-byte logical blocks:
> (8.00 GB/7.45 GiB)
> [23433.244088] sd 7:0:0:0: [sda] Write Protect is off
> [23433.244091] sd 7:0:0:0: [sda] Mode Sense: 23 00 00 00
> [23433.246215] sd 7:0:0:0: [sda] No Caching mode page present
> [23433.246218] sd 7:0:0:0: [sda] Assuming drive cache: write through
> [23433.253714] sd 7:0:0:0: [sda] No Caching mode page present
> [23433.253718] sd 7:0:0:0: [sda] Assuming drive cache: write through
> [23433.275741] sda: sda1
> [23433.281860] sd 7:0:0:0: [sda] No Caching mode page present
> [23433.281865] sd 7:0:0:0: [sda] Assuming drive cache: write through
> [23433.281869] sd 7:0:0:0: [sda] Attached SCSI removable disk
> [25983.383683] usb 1-8: USB disconnect, device number 7
> [26199.587825] end_request: I/O error, dev fd0, sector 0

Two ideas:

1) floppy device activated in BIOS while no floppy device present

2) floppy emulation for USB mass storage activated in BIOS

Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201209291229.10912.Martin@lichtvoll.de">http://lists.debian.org/201209291229.10912.Martin@lichtvoll.de
 
Old 09-29-2012, 12:43 PM
Albretch Mueller
 
Default why would fdisk -l take so long?

On 9/29/12, Jude DaShiell <jdashiel@shellworld.net> wrote:
> run d-ban on the disk and do a thorough cleaning of the disk then try
~
The only "data erasure" I know of is shredding your hard drives to
pieces, smashing them to dust and melting them. This is by the way
what US gov does with their hard drives and monitors
~
lbrtchx
~
http://en.wikipedia.org/wiki/Hysteresis
~
http://en.wikipedia.org/wiki/Data_remanence
~
http://en.wikipedia.org/wiki/Coercivity
~
http://en.wikipedia.org/wiki/Degaussing
For certain forms of computer data storage, however, such as modern
hard drives and some tape backup drives, degaussing renders the
magnetic media completely unusable and damages the storage system.
This is due to the devices having an infinitely variable read/write
head positioning mechanism which relies on special servo control data
(e.g. Gray Code) that is meant to be permanently embedded into the
magnetic media. This servo data is written onto the media a single
time at the factory using special-purpose servo writing hardware.
The servo patterns are normally never overwritten by the device for
any reason and are used to precisely position the read/write heads
over data tracks on the media, to compensate for sudden jarring device
movements, thermal expansion, or changes in orientation. Degaussing
indiscriminately removes not only the stored data but also the servo
control data, and without the servo data the device is no longer able
to determine where data is to be read or written on the magnetic
medium. The medium must be low-level formatted to become usable again;
with modern hard drives, this is generally not possible without
manufacturer-specific and often model-specific service equipment.
~


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAFakBwj=pS0AT98ZjzPF1uVJ_X4NH=isxR4W1pAVamVOFd_oG g@mail.gmail.com
 

Thread Tools




All times are GMT. The time now is 10:36 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org