Peter Zijlstra wrote:
>
> but I have an increasing seek error rate as well. I got the ST disk
> because thinkwiki suggested it.
>
Apparently Seagate has their own definition of seek error rate.
Large numbers are normal, or at least very common.
Now I wonder if they have their own way of doing r
On Wed, 2007-04-18 at 17:27 -0400, Chuck Ebbert wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Wednesday 18 April 2007, Chuck Ebbert wrote:
> >> Mark Lord wrote:
> >>> Mark Lord wrote:
> With the patch applied, I don't see *any* new activity in those
> S.M.A.R.T.
> attributes over
Jan,
mine does not pop running Linux but only during the shutdown. As I
wrote before, switching from PATA to IDE has solved the problem for
me.
Regards,
Fabio
On 4/21/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>On Apr 20 2007 21:57, Fabio Comolli wrote:
>
> hda: TOSHIBA MK8025GAS, ATA DISK
>On Apr 20 2007 21:57, Fabio Comolli wrote:
>
> hda: TOSHIBA MK8025GAS, ATA DISK drive
MK...? These sort of disks do that stupid pop. Mine -- a MK2003GAH --
does it even while running Linux, if the disk is _idle_.
See http://lkml.org/lkml/2006/11/15/413 - hope it provides some pointers.
Regards,
Hi.
On 4/21/07, emisca <[EMAIL PROTECTED]> wrote:
So, removing -d halt option solves this problem?
According to the halt manpage, -n implies -d (in other words, -d is
not removed at all).
Regards,
Fabio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
So, removing -d halt option solves this problem?
2007/4/20, Fabio Comolli <[EMAIL PROTECTED]>:
Bingo!
I switched from ata_piix.c to piix_ide.c and the "pop" disappeared.
I must say that the "pop" also disappeared after suspending to disk
using suspend2 (obviously without executing halt -n -h -p
Bingo!
I switched from ata_piix.c to piix_ide.c and the "pop" disappeared.
I must say that the "pop" also disappeared after suspending to disk
using suspend2 (obviously without executing halt -n -h -p) . In both
cases it was present with the previous setup.
This is with a pure PATA setup with no
Chuck Ebbert wrote:
Stephen Clark wrote:
Mark Lord wrote:
Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those
S.M.A.R.T.
attributes over multiple hibernates (Linux "suspend-to-disk").
Scratch that -- operator failure. ;)
The patch ma
Stephen Clark wrote:
> Mark Lord wrote:
>
>> Mark Lord wrote:
>>
>>
>>> With the patch applied, I don't see *any* new activity in those
>>> S.M.A.R.T.
>>> attributes over multiple hibernates (Linux "suspend-to-disk").
>>>
>>
>> Scratch that -- operator failure. ;)
>> The patch makes no diffe
Stephen Clark wrote:
It is definitely the disk drive. It is located in the right front corner
of my laptop so I put my ear
by it during shutdown and that is where the click is coming from.
Isn't there also a speaker located there?
-
To unsubscribe from this list: send the line "unsubscribe l
From the debian etch 4.0 /etc/init.d/halt script:
# Don't shut down drives if we're using RAID.
hddown="-h"
if grep -qs '^md.*active' /proc/mdstat
then
hddown=""
fi
# If INIT_HALT=HALT don't poweroff.
poweroff="-p"
if [ "$IN
Jan Engelhardt wrote:
On Apr 18 2007 09:39, Stephen Clark wrote:
So this is the pop I hear on my new laptop that is using
libata=combined_mode when I shut my system down. I didn't get the
pop with the same disk drive in an older laptop that was only ide.
It sounds like a relay closing or ope
On Apr 18 2007 09:39, Stephen Clark wrote:
>>
> So this is the pop I hear on my new laptop that is using
> libata=combined_mode when I shut my system down. I didn't get the
> pop with the same disk drive in an older laptop that was only ide.
> It sounds like a relay closing or opening, but is real
Mark Lord wrote:
Tejun Heo wrote:
1. shutdown(8) issues SYNCHRONIZE_CACHE followed by STANDBY_NOW
2. kernel shutdown starts
3. libata shutdown issues SYNCHRONIZE_CACHE
4. power goes off
Okay, after some experimentatino, it's the STANDBY_NOW that
is causing the Power-Off_Retract_Count to incre
Tejun Heo wrote:
1. shutdown(8) issues SYNCHRONIZE_CACHE followed by STANDBY_NOW
2. kernel shutdown starts
3. libata shutdown issues SYNCHRONIZE_CACHE
4. power goes off
Okay, after some experimentatino, it's the STANDBY_NOW that
is causing the Power-Off_Retract_Count to increment on my machine
Robert Hancock wrote:
> Tejun Heo wrote:
>> This really isn't a regression. It's been always like that with libata.
>> libata doesn't make devices go into standby mode and shutdown(8) does
>> it for libata. The problem here is that libata does issue
>> SYNCHRONIZE_CACHE on shutdown. So, the seq
Tejun Heo wrote:
This really isn't a regression. It's been always like that with libata.
libata doesn't make devices go into standby mode and shutdown(8) does
it for libata. The problem here is that libata does issue
SYNCHRONIZE_CACHE on shutdown. So, the sequence of event is...
1. shutdown(
Stephen Clark wrote:
So this is the pop I hear on my new laptop that is using
libata=combined_mode
when I shut my system down. I didn't get the pop with the same disk
drive in an older
laptop that was only ide. It sounds like a relay closing or opening, but
is really my
drive head doing an eme
Stephen Clark wrote:
I tried this on 2.6.20.2 it applied to libata with some fuzz and I had
to manually edit libata.h
When I did a shutdown I still got the click/pop.
I also noticed the last thing displayed on the lcd before it goes blank is
Synchronizing SCSI Disks - then the click/pop.
HTH,
On 4/18/07, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
On Wednesday 18 April 2007, Chuck Ebbert wrote:
> Mark Lord wrote:
> > Mark Lord wrote:
> >>
> >> With the patch applied, I don't see *any* new activity in those
> >> S.M.A.R.T.
> >> attributes over multiple hibernates (Linux "susp
Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 18 April 2007, Chuck Ebbert wrote:
>> Mark Lord wrote:
>>> Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those
S.M.A.R.T.
attributes over multiple hibernates (Linux "suspend-to-disk").
>>> Scratch that -- op
On Wednesday 18 April 2007, Tejun Heo wrote:
> Mark Lord wrote:
> > Chuck Ebbert wrote:
> >> Mark Lord wrote:
> >>> I'll patch it locally on my own machines, but what about the tens
> >>> of thousands of other Seagate notebook drive owners out there?
> >>>
> >>
> >> This is a problem with Seagate
On Wednesday 18 April 2007, Chuck Ebbert wrote:
> Mark Lord wrote:
> > Mark Lord wrote:
> >>
> >> With the patch applied, I don't see *any* new activity in those
> >> S.M.A.R.T.
> >> attributes over multiple hibernates (Linux "suspend-to-disk").
> >
> > Scratch that -- operator failure. ;)
> > T
Mark Lord wrote:
> Mark Lord wrote:
>>
>> With the patch applied, I don't see *any* new activity in those
>> S.M.A.R.T.
>> attributes over multiple hibernates (Linux "suspend-to-disk").
>
> Scratch that -- operator failure. ;)
> The patch makes no difference over hibernates in the SMART logs.
>
Mark Lord wrote:
Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those S.M.A.R.T.
attributes over multiple hibernates (Linux "suspend-to-disk").
Scratch that -- operator failure. ;)
The patch makes no difference over hibernates in the SMART logs.
It's stil
Mark Lord wrote:
With the patch applied, I don't see *any* new activity in those S.M.A.R.T.
attributes over multiple hibernates (Linux "suspend-to-disk").
Scratch that -- operator failure. ;)
The patch makes no difference over hibernates in the SMART logs.
It's still logging extra Power-Off_
Tejun Heo wrote:
Mark Lord wrote:
..
It would be nice if somebody who can hear the "pop" would also test this,
as it will confirm that this is a complete fix for the problem.
You'll probably be able to here the "pop" on sleep-to-disk.
My "pop" drives are busy elsewhere right now.
The syste
Mark Lord wrote:
Alan Cox wrote:
+ if (dev->needs_flush && ata_try_flush_cache(dev)) {
return ata_scsi_flush_xlat;
+ dev->needs_flush = 0;
Works better if you swap the dev-> and return lines
Heh, yeah, I noticed that!
Mark Lord wrote:
> Alan Cox wrote:
>>> +if (dev->needs_flush && ata_try_flush_cache(dev)) {
>>> return ata_scsi_flush_xlat;
>>> +dev->needs_flush = 0;
>>
>> Works better if you swap the dev-> and return lines
>
> Heh, yeah, I noticed that!
>
> Here it is, *tested*
Alan Cox wrote:
+ if (dev->needs_flush && ata_try_flush_cache(dev)) {
return ata_scsi_flush_xlat;
+ dev->needs_flush = 0;
Works better if you swap the dev-> and return lines
Heh, yeah, I noticed that!
Here it is, *tested* now, with
> + if (dev->needs_flush && ata_try_flush_cache(dev)) {
> return ata_scsi_flush_xlat;
> + dev->needs_flush = 0;
Works better if you swap the dev-> and return lines
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Mark Lord wrote:
Alan Cox wrote:
If you see a synchronize cache succeed and you then see the drive
shutdown succeed then you know that a sync cache can be faked as ok
safely. Any other command in between or after and it doesn't get faked
This seems pretty easy to deal with at command issue.
Alan Cox wrote:
If you see a synchronize cache succeed and you then see the drive
shutdown succeed then you know that a sync cache can be faked as ok
safely. Any other command in between or after and it doesn't get faked
This seems pretty easy to deal with at command issue.
Yup. It could be
Alan Cox wrote:
Thought about that and querying power state before doing shutdown
sequence but things get somewhat ugly because shutdown sequence is
driven from sd->shutdown(). We'll have to snoop both sync and shutdown
commands and check whether the system is shutting down. Also, I felt
ve
Alan Cox wrote:
Thought about that and querying power state before doing shutdown
sequence but things get somewhat ugly because shutdown sequence is
driven from sd->shutdown(). We'll have to snoop both sync and shutdown
commands and check whether the system is shutting down. Also, I felt
ver
> Thought about that and querying power state before doing shutdown
> sequence but things get somewhat ugly because shutdown sequence is
> driven from sd->shutdown(). We'll have to snoop both sync and shutdown
> commands and check whether the system is shutting down. Also, I felt
> very uneas
Tejun Heo wrote:
Alan Cox wrote:
Not that simple. Most disks don't spin up on SYNCHRONIZE_CACHE if
its cache is clean. Sadly some disks actually spin up when it
receives spin down command while spun down to immediately spin down
again, so we would be fixing problem for some number of disks w
Alan Cox wrote:
Not that simple. Most disks don't spin up on SYNCHRONIZE_CACHE if its
cache is clean. Sadly some disks actually spin up when it receives spin
down command while spun down to immediately spin down again, so we would
be fixing problem for some number of disks while breaking othe
> Not that simple. Most disks don't spin up on SYNCHRONIZE_CACHE if its
> cache is clean. Sadly some disks actually spin up when it receives spin
> down command while spun down to immediately spin down again, so we would
> be fixing problem for some number of disks while breaking others. :-(
Bodo Eggert wrote:
SCSI part of the fix is queued in scsi-misc-2.6 tree and libata-dev part
is acked and waiting to be merged, so the fix will be available in
2.6.22. However, it's disabled by default to remain compatible with the
^
Tejun Heo <[EMAIL PROTECTED]> wrote:
> This really isn't a regression. It's been always like that with libata.
> libata doesn't make devices go into standby mode and shutdown(8) does
> it for libata. The problem here is that libata does issue
> SYNCHRONIZE_CACHE on shutdown. So, the sequence o
Mark Lord wrote:
> Chuck Ebbert wrote:
>> Mark Lord wrote:
>>> I'll patch it locally on my own machines, but what about the tens
>>> of thousands of other Seagate notebook drive owners out there?
>>>
>>
>> This is a problem with Seagate specifically, spinning back up
>> on receipt of some command a
Chuck Ebbert wrote:
Mark Lord wrote:
I'll patch it locally on my own machines, but what about the tens
of thousands of other Seagate notebook drive owners out there?
This is a problem with Seagate specifically, spinning back up
on receipt of some command after spindown?
No, they just seem t
Mark Lord wrote:
>
> I'll patch it locally on my own machines, but what about the tens
> of thousands of other Seagate notebook drive owners out there?
>
This is a problem with Seagate specifically, spinning back up
on receipt of some command after spindown?
-
To unsubscribe from this list: sen
emisca wrote:
I can confirm this, I have a Seagate Momentus 5400.3 sata disk, and it
spins off, respin up and again off when I halt my notebook.
I had before this disk an IBM/Hitachi one, and it doesn't have this
behaviour.
Take a look at this bug report:
https://bugs.launchpad.net/ubuntu/+sou
On Mon, 16 Apr 2007, Chuck Ebbert wrote:
> It looks like there are two problems here:
>
> (1) Some notebooks power off and back on when restarting.
If it happens just under Linux, this is something that really needs to be
addressed post-haste. Maybe someone should open a bug in bugzilla to help
Hi.
On 4/17/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
(2) Linux (alone) gives a very muted pop on shutdown. This could
be from bad interaction with the shutdown command, or some
other reason (drive not given enough time to shut down?)
The noise is not very loud, maybe the head di
2007/4/17, Chuck Ebbert <[EMAIL PROTECTED]>:
Jan Engelhardt wrote:
> On Apr 15 2007 12:53, Henrique de Moraes Holschuh wrote:
>> On Sat, 14 Apr 2007, Pavel Machek wrote:
>>> How common are notebooks that cut power to disks during reboot?
>> Assuming it also does this when running Windows, I'd rep
Jan Engelhardt wrote:
> On Apr 15 2007 12:53, Henrique de Moraes Holschuh wrote:
>> On Sat, 14 Apr 2007, Pavel Machek wrote:
>>> How common are notebooks that cut power to disks during reboot?
>> Assuming it also does this when running Windows, I'd report it as a grave
>> bug to the vendor and dema
On Sunday 15 April 2007 19:07, emisca wrote:
> I can confirm this, I have a Seagate Momentus 5400.3 sata disk, and it
> spins off, respin up and again off when I halt my notebook.
> I had before this disk an IBM/Hitachi one, and it doesn't have this
> behaviour.
>
> Take a look at this bug report:
On Apr 15 2007 12:53, Henrique de Moraes Holschuh wrote:
>On Sat, 14 Apr 2007, Pavel Machek wrote:
>> How common are notebooks that cut power to disks during reboot?
>
>Assuming it also does this when running Windows, I'd report it as a grave
>bug to the vendor and demand it to be fixed, or the ma
I can confirm this, I have a Seagate Momentus 5400.3 sata disk, and it
spins off, respin up and again off when I halt my notebook.
I had before this disk an IBM/Hitachi one, and it doesn't have this behaviour.
Take a look at this bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-source-
On Sat, 14 Apr 2007, Pavel Machek wrote:
> How common are notebooks that cut power to disks during reboot?
Not common at all. Given that it wears the electronics a lot, it must be
either a defect (of the kinds Brazilian law forces the manufacturer to
either fix or give you your money back).
Assu
Hi!
> When I reboot my notebook, it powers off and powers back on.
> On poweroff a loud snapping noise seems to be coming from the
> hard drive. Today I noticed there is no "shutdown: hda" on
> the console when I reboot. Whne I do a normal poweroff the
> message is displayed and there is no noise
Chuck Ebbert wrote:
When I reboot my notebook, it powers off and powers back on.
On poweroff a loud snapping noise seems to be coming from the
hard drive. Today I noticed there is no "shutdown: hda" on
the console when I reboot. Whne I do a normal poweroff the
message is displayed and there is no
Bartlomiej Zolnierkiewicz wrote:
>>
>> There is no noise and the retract count does not increase when I boot
>> and then shutdown/power off the other OS.
>
> What about shutdown/reboot?
Very loud noise and the count goes up.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
On 4/13/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
Bartlomiej Zolnierkiewicz wrote:
>> Now we're getting somewhere. There is some other OS on here because
>> it's required for doing BIOS updates. I booted it and shut down.
>> The power cycle count increased but the power off retract count did no
Bartlomiej Zolnierkiewicz wrote:
>> Now we're getting somewhere. There is some other OS on here because
>> it's required for doing BIOS updates. I booted it and shut down.
>> The power cycle count increased but the power off retract count did not.
>>
>> The counts are:
>>
>> power cycle ... 111
>>
On Thursday 12 April 2007, Chuck Ebbert wrote:
> Jan Engelhardt wrote:
> > On Apr 11 2007 17:35, Chuck Ebbert wrote:
> >> Jan Engelhardt wrote:
> >>> On Apr 11 2007 17:07, Chuck Ebbert wrote:
> When I reboot my notebook, it powers off and powers back on.
> On poweroff a loud snapping nois
Jan Engelhardt wrote:
> On Apr 11 2007 17:35, Chuck Ebbert wrote:
>> Jan Engelhardt wrote:
>>> On Apr 11 2007 17:07, Chuck Ebbert wrote:
When I reboot my notebook, it powers off and powers back on.
On poweroff a loud snapping noise seems to be coming from the
hard drive. Today I noti
On Apr 11 2007 17:35, Chuck Ebbert wrote:
>Jan Engelhardt wrote:
>> On Apr 11 2007 17:07, Chuck Ebbert wrote:
>>> When I reboot my notebook, it powers off and powers back on.
>>> On poweroff a loud snapping noise seems to be coming from the
>>> hard drive. Today I noticed there is no "shutdown: hd
Jan Engelhardt wrote:
> On Apr 11 2007 17:07, Chuck Ebbert wrote:
>> When I reboot my notebook, it powers off and powers back on.
>> On poweroff a loud snapping noise seems to be coming from the
>> hard drive. Today I noticed there is no "shutdown: hda" on
>> the console when I reboot. Whne I do a
On Apr 11 2007 17:07, Chuck Ebbert wrote:
>
>When I reboot my notebook, it powers off and powers back on.
>On poweroff a loud snapping noise seems to be coming from the
>hard drive. Today I noticed there is no "shutdown: hda" on
>the console when I reboot. Whne I do a normal poweroff the
>message
When I reboot my notebook, it powers off and powers back on.
On poweroff a loud snapping noise seems to be coming from the
hard drive. Today I noticed there is no "shutdown: hda" on
the console when I reboot. Whne I do a normal poweroff the
message is displayed and there is no noise. Should the IDE
64 matches
Mail list logo
