On 9/29/12, Martin Steigerwald wrote:
> Hi Albrecht!
>
> Am Samstag, 29. September 2012 schrieb Albretch Mueller:
>
> Two ideas:
>
> 1) floppy device activated in BIOS while no floppy device present
>
> 2) floppy emulation for USB mass storage activated in BIOS
~
that was it! Reset, checked and s
On 9/29/12, Jude DaShiell 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
~
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.676
> 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, e
~
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/mes
On Friday, September 28, 2012 08:58:47 PM Albretch Mueller wrote:
> > > >1 Raw_Read_Error_Rate 0x000f 115 082 006Pre-fail
> > > >
> > > > Always - 96695847
> > >
> > > Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
> > > low.
> >
> > Not nec
> > >1 Raw_Read_Error_Rate 0x000f 115 082 006Pre-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
On Friday, September 28, 2012 08:23:59 AM Dom wrote:
> >1 Raw_Read_Error_Rate 0x000f 115 082 006Pre-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?) p
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=`(tim
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
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 throu
Albretch Mueller writes:
>> Because your disk is sleeping?
> ~
> That I think may be the reason why. I did notice and check that it
> always seems to happen after suspending my box, even if you unmount
> all drives before, but what I don't get is that may people would be
> complaining about that
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 wort
On 28/09/12 12:27, Albretch Mueller wrote:
Failing boot sector?
Some other sector it has to read is failing?
Check the logs. Try (from smartmontools):
~
I don't know exactly which of your questions/suggestions running:
~
smartctl -A /dev/sda | egrep -i "sector|realloc"
~
relates to, but it
On 28/09/12 11:30, Karl E. Jorgensen wrote:
Hi
On Fri, Sep 28, 2012 at 03:52:26AM +0100, Albretch Mueller wrote:
$ date; fdisk -l; date
Thu Sep 27 22:48:21 UTC 2012
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors
> Failing boot sector?
> Some other sector it has to read is failing?
> Check the logs. Try (from smartmontools):
~
I don't know exactly which of your questions/suggestions running:
~
smartctl -A /dev/sda | egrep -i "sector|realloc"
~
relates to, but it didn't report any error message. Without g
Hi
On Fri, Sep 28, 2012 at 03:52:26AM +0100, Albretch Mueller wrote:
> $ date; fdisk -l; date
> Thu Sep 27 22:48:21 UTC 2012
>
> Disk /dev/sda: 250.1 GB, 250059350016 bytes
> 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector si
Could it be a missing swap partition is slowing down drive access? I
don't know if you were connected to the internet when you did this run,
but if so, you might disconnect from the internet and run fdisk -l again
and compare speeds. It could be fdisk is checking for remote disks as
well but
Because your disk is sleeping?
--
Debian testing amd64
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87k3ve4pyk@yun.yagibdah.de
On Thursday, September 27, 2012 10:52:26 PM Albretch Mueller wrote:
> $ date; fdisk -l; date
> Thu Sep 27 22:48:21 UTC 2012
> ...
> Thu Sep 27 22:48:59 UTC 2012
Failing boot sector? Some other sector it has to read is failing? Check the
logs. Try (from smartmontools):
smartctl -A /dev/sda | egr
$ date; fdisk -l; date
Thu Sep 27 22:48:21 UTC 2012
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes /
21 matches
Mail list logo
