Re: Strangeness when booting raid1: md5 already running?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 22 Mar 2005, Neil Brown wrote:

On Monday March 21, Ruth.Ivimey-Cook@xxxxxxxxxx wrote:
...repeated several times....
md: export_rdev(hda9)
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: recovery complete.

Now this was the first time the string "md5" appears in the log. And
indeed, it appears that hda9 has been kicked out of the array:

So was md5 actually running (what did /proc/mdstat show? What about mdadm -D /dev/md5?).

mdstat and mdadm both report that md5 is running degraded - with hdc9 and hda9 removed.


which wasn't part of an array but couldn't be added to one.  Nothing
particularly interesting.

Ok. I'll just re-add the drive and see what happens.

Thanks

Ruth

--
Ruth Ivimey-Cook
Software engineer and technical writer.
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux