> -Original Message-
> From: Bruno Prior [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 22, 1999 8:30 AM
> To: Linux-Raid; Michel Pelletier
> Subject: RE: errors on boot
>
>
> Michel,
>
> Thanks for that. It makes things much clearer.
>
> &g
Michel,
Thanks for that. It makes things much clearer.
> Nov 16 13:36:28 korak kernel: sdb4's event counter: 0016
> Nov 16 13:36:28 korak kernel: sda4's event counter: 0017
> Nov 16 13:36:28 korak kernel: md: superblock update time inconsistency
> -- using
> the most recent one
> Nov 16
On Tue, Nov 16, 1999 at 03:46:56PM -0500, Michel Pelletier wrote:
> > -Original Message-
> physical? The other two partions on the same drive work dandy with
> their RAID, it looks like just this one partition on the drive is bad.
> How, in a nutshell, do I fix this sucker?
>
try raidhot
> At boot time, I have the following error messages in /var/log/messages:
>
> kernel: raid1: md2, not all disks are operational -- trying to recover
> array
> kernel: raid1: raid set md2 active with 1 out of 2 mirrors
> kernel: md: updating md2 RAID superblock on device
> kernel: sda4 [events:
> -Original Message-
> From: Luca Berra [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 16, 1999 2:45 PM
> To: '[EMAIL PROTECTED]'
> Subject: Re: errors on boot
>
>
> On Tue, Nov 16, 1999 at 03:14:42PM -0500, Michel Pelletier wrote:
> > It l
On Tue, Nov 16, 1999 at 03:14:42PM -0500, Michel Pelletier wrote:
> It looks to me like the [2/1] means only one of my two 'low level'
> partitions below /dev/md2 is working. I don't know what the [U_] means,
it means the second partiotion is gone
U=ok
_=fubar
--
Luca Berra -- [EMAIL PROTECTE
Howdy folks,
I got some errors about 'writing beyond the end of a device' so I
decided to reboot the machine cleanly.
It came back up, and all data is still there and good, but my
/proc/mdstat looks like this:
[root@korak /root]# cat < /proc/mdstat
Personalities : [linear] [raid1]
read_ahead
>I tried that also. In fact, I tried all combinations, sorry I wasn't
>explicit about that. I get an error that /dev/sdb4 is not in the array,
>and /dev/sda4 is busy.
>
>I'm not even sure which one is the good one! I'm assuming that since
>/proc/mdstat tells me the second on is bad, and that /d
Michel,
On Thu, 18 Nov 1999 11:00:36 -0500, Michel Pelletier wrote:
>> >> > physical? The other two partions on the same drive work
>> dandy with
>> >> > their RAID, it looks like just this one partition on the
>> >> drive is bad.
>> >> > How, in a nutshell, do I fix this sucker?
>> >> >
>>
Michel,
At 10:27 Uhr -0500 18.11.1999, Michel Pelletier wrote:
>Ok, there are three groups of messages for each of the three md devices.
>Here is the group for the failed device:
>
>...
>
>Nov 16 13:36:28 korak kernel: running:
>Nov 16 13:36:28 korak kernel: now!
>Nov 16 13:36:28 korak kernel: s
> -Original Message-
> From: Robert Dahlem [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 18, 1999 10:23 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Michel Pelletier
> Subject: RE: errors on boot
>
>
> Michel,
>
> On Thu, 18 Nov 1999 10:24:15
Michel,
On Thu, 18 Nov 1999 10:24:15 -0500, Michel Pelletier wrote:
>> > physical? The other two partions on the same drive work dandy with
>> > their RAID, it looks like just this one partition on the
>> drive is bad.
>> > How, in a nutshell, do I fix this sucker?
>> >
>> try raidhotremove /
> -Original Message-
> From: Bruno Prior [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 17, 1999 7:14 AM
> To: Linux-Raid; Michel Pelletier
> Subject: RE: errors on boot
>
>
> > At boot time, I have the following error messages in
> /var/log/me
> -Original Message-
> From: Luca Berra [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 17, 1999 8:57 AM
> To: '[EMAIL PROTECTED]'
> Subject: Re: errors on boot
>
>
> On Tue, Nov 16, 1999 at 03:46:56PM -0500, Michel Pelletier wrote:
> > &
14 matches
Mail list logo
