Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3761 - mdadm 2.2-1 fails on boot

Attached to Project: Arch Linux
Opened by Constantinos Laitsas (osigen) - Friday, 13 January 2006, 09:41 GMT
Last edited by Dale Blount (dale) - Wednesday, 01 February 2006, 00:26 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading to recent mdadm (2.2-1) my raid 1 PC failed on boot with the follow messages:
:: Mounting local filesystems
mount: wrong fs type, bad option, bad superblock on /dev/md1
(some generic suggestions here)
mount: special device /dev/array/home does not exist

I revert back to mdadm 2.1 and my system is healthy again.

I use ARCHLINUX 7.1 with kernel 2.6.14
This task depends upon

Closed by  Judd Vinet (judd)
Monday, 06 February 2006, 19:03 GMT
Reason for closing:  Fixed
Additional comments about closing:  Thanks Dale.
Comment by Constantinos Laitsas (osigen) - Friday, 13 January 2006, 09:42 GMT
with reiserfs
Comment by Dale Blount (dale) - Friday, 13 January 2006, 13:45 GMT
hrm, happened to me this morning too, it made one hell of an upgrade problem.

"mdadm --assemble --scan" segfaults after boot, and only / (defined in mkinitrd.conf) gets mounted.
Comment by Dale Blount (dale) - Friday, 13 January 2006, 13:46 GMT
changed priority low->high because it's not quite as easy to recover if / and /var are on MD as it is if /home only is.
Comment by Dale Blount (dale) - Wednesday, 01 February 2006, 00:25 GMT
patch can be found here from mdadm's author:

linux-raid@vger.kernel.org/msg03639.html"> http://www.mail-archive.com/linux-raid@vger.kernel.org/msg03639.html

Loading...