Bug#433210: marked as done (Debian-installer should include /dev/md0, /dev/md1 (plus mdadm, MAKEDEV?))
Your message dated Sun, 15 Jul 2007 17:50:24 +0200
with message-id <200707151750.25182.elendil@planet.nl>
and subject line Bug#433210: Debian-installer should include /dev/md0, /dev/md1 (plus mdadm, MAKEDEV?)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debian-installer
Version: 20070308
While trying to perform some rescuing of a Debian Etch x86 system running
with root-on-md (RAID1) (plus some other partitions with md RAID5),
I tried to use the USB Debian Installer.
This was not as easy as I'd think it would be, because there's no
/dev/md0 accessible from the installer shell. I actually got mdadm
installed by starting the manual partition editor (guess I pulled in
some md installer package) but there were still no /dev/md[0-9] device
nodes around. Also I couldn't find any MAKEDEV script so creating them
were not trivial. Finally I managed to put the correct md device files
on a mountable file system and "cp -a" them into the running installer
shell.
So in summary, I'm submitting this bug report in the hopes that rescuing
md systems can be made easier with the next version of the debian
installer.
PS: I also got a whole lot of scary messages in 'dmesg' when the
debian-installer automatically tried to mount every partition to look
for the .ISO file (it tried to mount the raw devices, which are part of
undetected MD arrays). Hopefully the mounting done by the .ISO detector
doesn't un-sync the arrays (does that make sense?)
--- End Message ---
--- Begin Message ---
On Sunday 15 July 2007 15:46, debbug.mddev@sub.noloop.net wrote:
> While trying to perform some rescuing of a Debian Etch x86 system
> running with root-on-md (RAID1) (plus some other partitions with md
> RAID5), I tried to use the USB Debian Installer.
>
> This was not as easy as I'd think it would be, because there's no
> /dev/md0 accessible from the installer shell.
You seem to be somewhat confused about how /dev/md* devices are created.
They are never created manually, but are instead created automatically by
the kernel when RAID devices are activated.
What you need to do to rescue a software RAID system is:
- manually load the needed kernel modules ('modprobe raid1')
- run mdadm to assemble existing arrays:
# mdadm --examine --scan --config=partitions > /tmp/mdadm.conf
# mdadm --assemble --scan --run --config=/tmp/mdadm.conf --auto=yes
Closing your report as this is not a bug, although we do agree that better
support for software RAID in rescue mode would be nice, but that is a
known issue.
Note: you can still reply to this message if you have further questions.
Cheers,
FJP
--- End Message ---
Reply to: