On 09/10/24 at 21:10, Jochen Spieker wrote:
Andy Smith:
Hi,
On Wed, Oct 09, 2024 at 08:41:38PM +0200, Franco Martelli wrote:
Do you know whether MD is clever enough to send an email to root when it
fails the device? Or have I to keep an eye on /proc/mdstat?
For more than a decade mdadm has s
Andy Smith:
> Hi,
>
> On Wed, Oct 09, 2024 at 08:41:38PM +0200, Franco Martelli wrote:
>> Do you know whether MD is clever enough to send an email to root when it
>> fails the device? Or have I to keep an eye on /proc/mdstat?
>
> For more than a decade mdadm has shipped with a service that runs i
Hi,
On Wed, Oct 09, 2024 at 08:41:38PM +0200, Franco Martelli wrote:
> Do you know whether MD is clever enough to send an email to root when it
> fails the device? Or have I to keep an eye on /proc/mdstat?
For more than a decade mdadm has shipped with a service that runs in
monitor mode to do thi
On 08/10/24 at 20:40, Andy Smith wrote:
Hi,
On Tue, Oct 08, 2024 at 04:58:46PM +0200, Jochen Spieker wrote:
Why is the RAID still considered healthy? At some point I
would expect the disk to be kicked from the RAID.
This will happen when/if MD can't compensate by reading data from other
m
yours does, but I would definitely question a value of 0 for failed
> (current pending and offline uncorrectable) _and_ reallocated sectors
> for a disk that's reporting I/O errors, for example. _At least_ one of
> those should be >0 for a truthful storage device in that situation.
e...@gmx.us:
> On 10/8/24 16:07, Jochen Spieker wrote:
>>| Oct 06 14:27:11 jigsaw kernel: I/O error, dev sdb, sector 9361257600 op
>>0x0:(READ) flags 0x0 phys_seg 150 prio class 3
>>| Oct 06 14:27:30 jigsaw kernel: I/O error, dev sdb, sector 9361275264 op
>>0x0:(READ) flags 0x4000 phys_seg 161 pr
a
storage. Yes, servo tracks and such things are supposed to catch and
compensate for that; but it might not be quite that bad yet.
Sometimes HDDs fail with a bang, and sometimes they fail with a
whimper.
Also note that some disks actually lie in SMART data. I don't know if
yours does, but I
On 10/8/24 16:07, Jochen Spieker wrote:
| Oct 06 14:27:11 jigsaw kernel: I/O error, dev sdb, sector 9361257600 op
0x0:(READ) flags 0x0 phys_seg 150 prio class 3
| Oct 06 14:27:30 jigsaw kernel: I/O error, dev sdb, sector 9361275264 op
0x0:(READ) flags 0x4000 phys_seg 161 prio class 3
| Oct 06 1
Andy Smith:
> On Tue, Oct 08, 2024 at 04:58:46PM +0200, Jochen Spieker wrote:
>> The way I understand these messages is that some sectors cannot be read
>> from sdb at all and the disk is unable to reallocate the data somewhere
>> else (probably because it doesn't know what the data should be in th
Dan Ritter:
> Jochen Spieker wrote:
>
>> The sector number mentioned at the bottom is increasing during the
>> check.
>
> So it repeats, and it's contiguous. That suggests a flaw in the
> drive itself.
It definitely looks like that:
| Oct 06 14:27:11 jigsaw kernel: I/O error, dev sdb, sector 9
Hi,
On Tue, Oct 08, 2024 at 04:58:46PM +0200, Jochen Spieker wrote:
> The way I understand these messages is that some sectors cannot be read
> from sdb at all and the disk is unable to reallocate the data somewhere
> else (probably because it doesn't know what the data should be in the
> first pl
Jochen Spieker wrote:
> I have two disks in a RAID-1:
>
> | $ cat /proc/mdstat
> | Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5]
> [raid4] [raid10]
> | md0 : active raid1 sdb1[2] sdc1[0]
> | 5860390400 blocks super 1.2 [2/2] [UU]
> | bitmap: 5/44 pages [20KB],
Hey,
please forgive me for posting a question that is not Debian-specific,
but maybe somebody here can explain this to me. Ten years ago I would
have posted to Usenet instead.
I have two disks in a RAID-1:
| $ cat /proc/mdstat
| Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5
Hi George,
It would be useful if you paste here full smart attribute stats, command:
sudo smartctl /dev/sda --all
replace sda with correct name as needed
Do "long" SMART test on this drive. It should be able to map out bad
sectors so Linux doesn't see the errors any more. Unless bad sectors are
On 10 Aug 2024 18:20 +1000, from c...@goproject.info (George at Clug):
> I have changed the port it is connected to, and the SATA cable, but
> still the errors follow the disk drive.
So that potentially leaves things like the SATA controller (unlikely),
the power supply (possible) and the drive it
On Sat, 10 Aug 2024 18:20:36 +1000
George at Clug wrote:
> I case there might be a known, fixable, fault that could cause this,
> anyone know what the following errors indicate?
I suspect you have a drive getting ready to die on you, which it may do
at any time.
> Sadly "Unrecovered read error"
Hi,
I case there might be a known, fixable, fault that could cause this,
anyone know what the following errors indicate?
Aug 10 17:30:51 srv01 kernel: ata6: EH complete
Aug 10 17:30:54 srv01 kernel: ata6.00: exception Emask 0x0 SAct 0x4000
SErr 0xc action 0x0
Aug 10 17:30:54 srv01 kernel: a
On Sun, Feb 12, 2017 at 09:36:16PM -0500, Bob Weber wrote:
> I use a program called ossec. It watches logs of all my linux boxes so I get
> email messages about disk problems. I also do periodic self tests on all my
> drives controlled by smartd from the smartmontools package. I also use a
> pa
On 02/12/2017 06:36 PM, Bob Weber wrote:
After writing this I wonder if I am over doing this. I just don't want to loose
data from a failing drive. I lived through 3.5 inch floppies which seemed to
always fail. And tape drives that were painfully slow. Not to mention back in
the mid 70s savi
On 02/12/2017 01:59 PM, Marc Shapiro wrote:
> On 02/12/2017 08:30 AM, Marc Auslander wrote:
>> I do not use LVM over raid 1. I think it can be made to work,
>> although IIRC booting from an LVM over RAID partion has caused issues.
> my boot partitions are separate. They are not under LVM.
>> LVM
Marc Shapiro writes:
> BTW, what is your third partition, and why would you not separate it
> now if starting from scratch?
My third partition is for backups which I make to protect against
software or operator error. At one point it was on a separate disk
since disks were small and without LVM
On 02/12/2017 08:30 AM, Marc Auslander wrote:
I do not use LVM over raid 1. I think it can be made to work,
although IIRC booting from an LVM over RAID partion has caused issues.
my boot partitions are separate. They are not under LVM.
LVM is useful when space requirements are changing over t
Marc Shapiro writes:
> the past couple of weeks. AIUI you can use LVM over raid. Is there
> any actual advantage to this? I was trying to determine the
> advantages of using straight raid, straight LVM, or LVM over raid. If
> I decide, later, to use raid, how dificult is it to add to a curren
I use raid 1 also for the redundancy it provides. If I need a backup I just
connect a disk, grow each array and add it to the array (I have 3 arrays for /,
/home and swap). It syncs up in a couple hours (depending on size of the
array). If you have grub install itself on the added disk you have
On 02/11/2017 05:22 PM, Marc Auslander wrote:
You didn't ask for advice so take it or ignore it.
IMHO, in this day and age, there is no reason not to run raid 1. Two
disks, identially partitioned, each parition set up as a raid 1
partition with two copies.
When a disk dies, you remove it from
Marc Auslander composed on 2017-02-11 20:22 (UTC-0500):
IMHO, in this day and age, there is no reason not to run raid 1.
Are you sure? Laptops have been outselling desktops for years.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living
You didn't ask for advice so take it or ignore it.
IMHO, in this day and age, there is no reason not to run raid 1. Two
disks, identially partitioned, each parition set up as a raid 1
partition with two copies.
When a disk dies, you remove it from all the raid partitions, pop in a
new disk, part
On 02/10/17 23:39, Marc Shapiro wrote:
On 02/08/2017 05:32 PM, David Christensen wrote:
On 02/08/17 15:59, Marc Shapiro wrote:
So how do I lay down a low level format on [the new 1 TB] drive?
I would use the SeaTools bootable CD to fill the drive with zeroes:
On 02/03/17 23:13, David Christens
On 02/08/2017 05:32 PM, David Christensen wrote:
On 02/08/17 15:59, Marc Shapiro wrote:
So how do I lay down a low level format on [the new 1 TB] drive?
I would use the SeaTools bootable CD to fill the drive with zeroes:
On 02/03/17 23:13, David Christensen wrote:
> Sometimes you get lucky an
On 02/09/2017 12:13 PM, Greg Wooledge wrote:
You shared your philosophy ("tear it all down and rebuild it from scratch
every two years")
I don't know where you got this. The OP was having one helluva time with
a harddrive. I suggested that he create a partition to store his
personal files "m
On Thu, Feb 09, 2017 at 12:03:18PM -0500, Ric Moore wrote:
> How so?? Don't "many other operating systems" have different
> configuration files in many other locations?? I wouldn't expect BSD
> config files to migrate to Linux, or Windows to do anything useful.
When I shared my $HOME between Ope
On 02/09/2017 08:10 AM, Greg Wooledge wrote:
On Wed, Feb 08, 2017 at 06:06:34PM -0500, Ric Moore wrote:
Careful there, I would not copy any of the /home/username/dot-files or
dot directories over, except like .mozilla and .thunderbird, so you
don't carry over some old and crufty setting that mig
On Wed, Feb 08, 2017 at 06:06:34PM -0500, Ric Moore wrote:
> Careful there, I would not copy any of the /home/username/dot-files or
> dot directories over, except like .mozilla and .thunderbird, so you
> don't carry over some old and crufty setting that might have been
> problematic.
I have the
On Wednesday, February 08, 2017 06:37:55 PM Marc Shapiro wrote:
> On 02/08/2017 03:06 PM, Ric Moore wrote:
> > On 02/08/2017 04:38 PM, Marc Shapiro wrote:
> > Careful there, I would not copy any of the /home/username/dot-files or
> > dot directories over, except like .mozilla and .thunderbird, so y
On 02/08/17 15:59, Marc Shapiro wrote:
So how do I lay down a low level format on [the new 1 TB] drive?
I would use the SeaTools bootable CD to fill the drive with zeroes:
On 02/03/17 23:13, David Christensen wrote:
> Sometimes you get lucky and the tool is a live CD:
>
>
www.seagate.com/file
On 02/08/2017 03:37 PM, Marc Shapiro wrote:
On 02/08/2017 03:06 PM, Ric Moore wrote:
On 02/08/2017 04:38 PM, Marc Shapiro wrote:
On 02/08/2017 01:26 PM, Ric Moore wrote:
On 02/08/2017 02:37 AM, Marc Shapiro wrote:
How it went is not well. I tested the new drive with SeagateTools
and
it was f
On 02/08/2017 03:06 PM, Ric Moore wrote:
On 02/08/2017 04:38 PM, Marc Shapiro wrote:
On 02/08/2017 01:26 PM, Ric Moore wrote:
On 02/08/2017 02:37 AM, Marc Shapiro wrote:
How it went is not well. I tested the new drive with SeagateTools and
it was fine. Then I made a clonezilla live CD and bo
On 02/08/2017 04:38 PM, Marc Shapiro wrote:
On 02/08/2017 01:26 PM, Ric Moore wrote:
On 02/08/2017 02:37 AM, Marc Shapiro wrote:
How it went is not well. I tested the new drive with SeagateTools and
it was fine. Then I made a clonezilla live CD and booted from it. It
stopped on the first rea
On 02/07/17 23:37, Marc Shapiro wrote:
> How it went is not well.
> David Christensen wrote:
>> Run memtest86+ for 24+ hours to verify that you don't have a memory
>> problem.
Did you test the memory? If not, test it now just to be sure.
>> Use SeaTools to wipe the new 1 TB drive and run the
How it went is not well. I tested the new drive with SeagateTools and it
was fine. Then I made a clonezilla live CD and booted from it. It stopped
on the first read error with a message saying to restart using the rescue
option. I did that. After 5 hours it finished without mentioning any
erro
On Fri, Feb 03, 2017 at 01:38:58PM -0800, Marc Shapiro wrote:
> I had been trying as root (see above). I do not have smartmontools
> currently installed. If I remember correctly, that is only going to be
> useful if it was already installed so the daemon could be capturing data
> when the problem
On 02/06/17 13:15, Marc Shapiro wrote:
I am pasting the result of smartctl -x /dev/sda below as I have no real
clue what to do with the information, but I have a few questions first.
1) I have purchased a new, very similar, Seagate 1TB drive and I plan to
install it and copy the whole system to
Gene Heskett composed on 2017-02-06 12:28 (UTC-0500):
That cold spare will eventually develop stiction, seizing the parked haed
to the surface of the disk solidly enough that the disk motor cannot
break it loose to spin the disk up. Such is best treated by hooking up
the cables, but holding the
On 02/06/17 09:28, Gene Heskett wrote:
That cold spare will eventually develop stiction, seizing the parked haed
to the surface of the disk solidly enough that the disk motor cannot
break it loose to spin the disk up. Such is best treated by hooking up
the cables, but holding the drive in your h
On 02/06/17 07:22, Joe Pfeiffer wrote:
David Christensen writes:
I've found (and heard) that the worst thing I can do to a HDD is put
it on the shelf and let it rot. I've had more than a few that failed
shortly after being put into a computer.
I hadn't heard this... I've got a drive I've be
On 02/03/2017 11:13 PM, David Christensen wrote:
On 02/03/17 13:47, Marc Shapiro wrote:
On 02/02/2017 10:23 PM, David Christensen wrote:
Have you downloaded and run the manufacturer diagnostic utilities for
all your drives? What do they say?
I have now downloaded and run Seagate's tools and
On Monday 06 February 2017 10:22:54 Joe Pfeiffer wrote:
> David Christensen writes:
> > On 02/04/17 07:18, Ric Moore wrote:
> >> I'm looking at a Seagate 750 gig drive that went south on me with a
> >> pile of errors. Good luck getting Seagate to give a good gosh darn.
> >> In the past I have had
David Christensen writes:
> On 02/04/17 07:18, Ric Moore wrote:
>> I'm looking at a Seagate 750 gig drive that went south on me with a pile
>> of errors. Good luck getting Seagate to give a good gosh darn. In the
>> past I have had mixed results replacing the drive motherboard. I saved
>> two out
On 02/04/17 07:18, Ric Moore wrote:
I'm looking at a Seagate 750 gig drive that went south on me with a pile
of errors. Good luck getting Seagate to give a good gosh darn. In the
past I have had mixed results replacing the drive motherboard. I saved
two out of three. I doubt I will buy anything S
On 02/03/2017 04:47 PM, Marc Shapiro wrote:
On 02/02/2017 10:23 PM, David Christensen wrote:
Have you downloaded and run the manufacturer diagnostic utilities for
all your drives? What do they say?
I have now downloaded and run Seagate's tools and it does show a does
show a disk error. Sinc
On 02/03/17 13:47, Marc Shapiro wrote:
On 02/02/2017 10:23 PM, David Christensen wrote:
Have you downloaded and run the manufacturer diagnostic utilities for
all your drives? What do they say?
I have now downloaded and run Seagate's tools and it does show a does
show a disk error. Since it
On 02/02/2017 10:23 PM, David Christensen wrote:
Have you downloaded and run the manufacturer diagnostic utilities for
all your drives? What do they say?
I have now downloaded and run Seagate's tools and it does show a does
show a disk error. Since it stops on the first error I do not know
On 02/03/2017 06:50 AM, Mark Fletcher wrote:
On Thu, Feb 02, 2017 at 11:34:03PM -0800, Marc Shapiro wrote:
Have you looked at the SMART reports? Please paste the following command
into a root shell, run it once for each drive (replacing /dev/sdX with the
corresponding device name), and paste bo
On Thu, Feb 02, 2017 at 11:34:03PM -0800, Marc Shapiro wrote:
>
> >Have you looked at the SMART reports? Please paste the following command
> >into a root shell, run it once for each drive (replacing /dev/sdX with the
> >corresponding device name), and paste both the command and the output into
>
On 02/02/2017 10:23 PM, David Christensen wrote:
On 02/02/17 13:05, Marc Shapiro wrote:
I apologize for this being so long, but since the problem occurs
sporadically I wanted to get as much information in this post as
possible because I don't know when it will happen again.
...
What operating
On 02/02/17 13:05, Marc Shapiro wrote:
I apologize for this being so long, but since the problem occurs
sporadically I wanted to get as much information in this post as
possible because I don't know when it will happen again.
...
What operating system are you running? Please paste the followin
On 02/02/2017 04:20 PM, Marc Auslander wrote:
A few observations.
Are your filesystems journaled. They say ext3, which IIRC does
support journaling?
the flashplayer should not be able to trash the file system.
/var/log/syslog is a place to look for io errors. If you are having
them you likel
A few observations.
Are your filesystems journaled. They say ext3, which IIRC does
support journaling?
the flashplayer should not be able to trash the file system.
/var/log/syslog is a place to look for io errors. If you are having
them you likely have a failing disk and need to replace it ASA
On 02/02/2017 01:40 PM, Marc Shapiro wrote:
On 02/02/2017 01:19 PM, to...@tuxteam.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 02, 2017 at 01:05:47PM -0800, Marc Shapiro wrote:
I apologize for this being so long, but since the problem occurs
sporadically I wanted to get
On 02/02/2017 01:19 PM, to...@tuxteam.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 02, 2017 at 01:05:47PM -0800, Marc Shapiro wrote:
I apologize for this being so long, but since the problem occurs
sporadically I wanted to get as much information in this post as
possible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 02, 2017 at 01:05:47PM -0800, Marc Shapiro wrote:
> I apologize for this being so long, but since the problem occurs
> sporadically I wanted to get as much information in this post as
> possible because I don't know when it will happen agai
I apologize for this being so long, but since the problem occurs
sporadically I wanted to get as much information in this post as
possible because I don't know when it will happen again.
This problem started a bout two weeks ago. I woke up to find a black
screen and a kernel panic. I reboote
Le jour de la Récompense, an CCXXIV, Lisi Reisz a écrit :
> Well, that's a better excuse than many. Beats "I can't be bothered" any day.
If you think about it a few more seconds, you realize this is the same
issue: the MUA not selecting the correct recipients by default. Neither
unwanted CCs nor
On Monday 19 September 2016 15:17:29 Tony Baldwin wrote:
> I just keep forgetting to
> list reply (old age, and a brain tumor).
Well, that's a better excuse than many. Beats "I can't be bothered" any day.
I'm so sorry to hear it. Old age is unfortunately incurable. I know someone
who was "cur
On 09/19/2016 09:57 AM, Dan Ritter wrote:
On Mon, Sep 19, 2016 at 09:27:43AM -0400, Tony Baldwin wrote:
On 09/19/2016 09:07 AM, Dan Ritter wrote:
Go make a backup of everything you care about, today. Copy to a
new disk, check it, then disconnect and label your backup.
After that, go look at /v
On Sun, Sep 18, 2016 at 10:46:02AM -0400, Tony Baldwin wrote:
> Yesterday I was getting random I/O errors for stuff as simple as clear (to
> clear a terminal),
> and I got one for halt, even (I manually shut the machine off, and rebooted)
> haven't seen the problem since th
Yesterday I was getting random I/O errors for stuff as simple as clear
(to clear a terminal),
and I got one for halt, even (I manually shut the machine off, and
rebooted) haven't seen the problem since then but things are sluggish
and weird.
Is this a warning I should heed?
This is on a
Hi,
I have an HP LaserJet 3330 AIO, connected via USB. Running Sid, hplip,
CUPS & friends installed. Printing works fine, scanning doesn't. Using
either the sane ([x]scanimage) or xsane frontends, the PC initiates a
scan, begins acquiring data, and then fails with an 'I/O error',
usually between 6
methanks in advance!
Does anyone have any experience with a Dell PowerVault 122T Autoloader?
I'm trying to get one set up on a Dell PowerEdge 1750 server running
Sarge, but I'm getting I/O errors.
Here's what I've done so far:
1. I've confirmed that the o/s recog
Does anyone have any experience with a Dell PowerVault 122T Autoloader?
I'm trying to get one set up on a Dell PowerEdge 1750 server running
Sarge, but I'm getting I/O errors.
Here's what I've done so far:
1. I've confirmed that the o/s recognizes the autoloader. Afte
CW Harris wrote:
On Fri, Jul 30, 2004 at 09:04:07AM +1200, Steven Jones wrote:
see if the manufacturer has a disk diagnostic program available, but I would suggest
the disk is stuffed.
I could be wrong, but isn't dev 0b:00 /dev/scd0 ? So it's having
trouble reading a scsi cdrom?
CW,
Y
ing errors on the console (tty01) prior to
> > rebooting:
> >
> > I/O error: dev 0b:00, sector 0
> > I/O error: dev 0b:00, sector 64
> > I/O error: dev 0b:00, sector 0
> > I/O error: dev 0b:00, sector 64
> >
> > Are these disk I/O errors? What furth
On Fri, Jul 30, 2004 at 09:04:07AM +1200, Steven Jones wrote:
> see if the manufacturer has a disk diagnostic program available, but I would suggest
> the disk is stuffed.
>
I could be wrong, but isn't dev 0b:00 /dev/scd0 ? So it's having
trouble reading a scsi cdrom?
--
Chris Harris <[EMAIL
see if the manufacturer has a disk diagnostic program available, but I would suggest
the disk is stuffed.
regards
S
-Original Message-
From: Michael G. Morey [mailto:[EMAIL PROTECTED]
Sent: Friday, 30 July 2004 8:50 a.m.
To: Debian User List
Subject: I/O Errors
All,
I'm ru
Are these disk I/O errors? What further diagnostics can I run, to help
troubleshoot the problem?
Thanks.
Michael
--
Michael Morey
Consultant
Optivel
Phone: 317.275.2306
E-mail: [EMAIL PROTECTED]
Web: www.optivel.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
on Fri, Feb 21, 2003 at 12:42:25PM -0500, Caleb Chaplin ([EMAIL PROTECTED]) wrote:
> I've recently installed woody in my home office and I'm trying to set it
> up as a general-purpose server to play and learn from. It's running a
> number of services (apache, ftp, nfs, samba).
>
> This morning I
I've recently installed woody in my home office and I'm trying to set it
up as a general-purpose server to play and learn from. It's running a
number of services (apache, ftp, nfs, samba).
This morning I start the computer and find that running certain commands
like apt, locate, whereis, etc prod
Jessica Blank said:
> The problem seems to happen whenever I'm working (reading/writing) on the
> second or third drive. I get I/O errors, and kernelspam like this:
luckily, according to the logs you posted this does not appear to be
a SCSI issue, or a hardware issue. it looks to be a
I am having some weird, weird SCSI I/O errors. I'm running Debian/PowerPC
on an "Old World" (beige) Mac-- namely, a Power Mac 7300/180 (the 7300s
were sold overseas, and are uncommon in the USA; they are roughly on par
with the 7500s, I believe.. if not a bit higher-end) wi
> HOLD IT! STOP THE PRESSES!
>
> Oh, that's too weird...
>
> I just up-arrowed to recall the last time I tried it, and this time it
> worked!
> I had been trying it as root all this time because of the mount point
> not being mountable by westk. So as another test I tried mounting it
> using /ho
I upgraded my hamm installation to slink smoothly (I think) but now I get
numerous I/O errors when running dselect from the CD-Rom.
Is this a hardware problem or is there something I can do about it in
slink?
Anthony
--
Anthony Campbell - running Linux Debian 2.1
[EMAIL PROTECTED] http
81 matches
Mail list logo
