Your message dated Wed, 27 Jan 2010 10:09:01 +0000
with message-id <[email protected]>
and subject line Bug#558823: fixed in mdadm 3.1.1-1
has caused the Debian Bug report #558823,
regarding /dev/disk/by-uuid not populated in d-i with RAID
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
558823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558823
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: installation-reports
I installed to an ARM machine today with the daily image and towards
the installation there was a hang at: "Configuring flash memory to
boot the system: 33%". Looking at /var/log/syslog showed that
flash-kernel's initramfs hook waited for user input because the UUID
was not found.
"blkid /dev/md1" showed the same UUID that flash-kernel was
complaining about. Looking at /dev/disk, I noticed that the by-uuid
directory didn't exist at all!
When I did:
| echo change > /sys/block/sda/sda2/uevent
the by-uuid dir was added and the UUID for my swap partitioon showed
up. However, I couldn't make the UUID of my RAID partition show up
with
| echo change > /sys/block/md0/uevent
I ran into this bug once before but thought it was a glitch. But a
few days ago another user reported this issue to me and today I ran
into it again. Normally I don't use RAID but today I did, so I'm
wondering if it's related to that.
Colin, Md, others: any idea?
Here's a workaround for users who run into this issue: open another
SSH connection to the installer, open a shell and type:
ps aux | grep -i flash_kernel
then kill that PID. Then edit the file
/target/usr/share/initramfs-tools/hooks/flash_kernel_set_root
and remove the check that ensures the root device exists. The
installer will continue. Wait until it reaches
"Installation complete" and hit "Go Back". Then choose "Make
the system bootable" again.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 3.1.1-1
We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive:
mdadm-udeb_3.1.1-1_amd64.udeb
to main/m/mdadm/mdadm-udeb_3.1.1-1_amd64.udeb
mdadm_3.1.1-1.debian.tar.gz
to main/m/mdadm/mdadm_3.1.1-1.debian.tar.gz
mdadm_3.1.1-1.dsc
to main/m/mdadm/mdadm_3.1.1-1.dsc
mdadm_3.1.1-1_amd64.deb
to main/m/mdadm/mdadm_3.1.1-1_amd64.deb
mdadm_3.1.1.orig.tar.bz2
to main/m/mdadm/mdadm_3.1.1.orig.tar.bz2
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
martin f. krafft <[email protected]> (supplier of updated mdadm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Format: 1.8
Date: Wed, 27 Jan 2010 10:14:25 +1300
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.1.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <[email protected]>
Changed-By: martin f. krafft <[email protected]>
Description:
mdadm - tool to administer Linux MD arrays (software RAID)
mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 539103 544558 549083 558823
Changes:
mdadm (3.1.1-1) unstable; urgency=low
.
* New upstream release.
* Retire fixed/blkid-dev branch.
* Reword warning about unbootable system when mdadm is purged
(closes: #544558).
* Updated FAQ to include s2ram as one of the reasons that can prevent an
array from being stopped; thanks to Pascal Hambourg for writing in.
* Install udev rules into udeb package (closes: #558823).
* Update mdadd.sh (formerly /usr/share/doc/mdadm/examples/newdisk.gz) from
Arno's website, refactoring the script into its own branch/patch
(closes: #539103).
* Do not single-quote homehost in initramfs script (closes: #549083).
Checksums-Sha1:
a46eb43b086abd6b7f39d52e39e69f343b1a206c 1264 mdadm_3.1.1-1.dsc
8902fd57eeb416455182bf0627a808275c5183ba 270338 mdadm_3.1.1.orig.tar.bz2
8a5690b6694f4ac15cfa9f7af4a581ffa70428f9 130649 mdadm_3.1.1-1.debian.tar.gz
ef3008337863daed2d6831a940f50d2d5014867f 443322 mdadm_3.1.1-1_amd64.deb
f78984080dacfa99116e861e2b6543d6a5ccc594 142072 mdadm-udeb_3.1.1-1_amd64.udeb
Checksums-Sha256:
170a8b5df6f572370186de7a9029880f7b252a1d0099499242854460af4e0d1d 1264
mdadm_3.1.1-1.dsc
31c0d3040774283b1e1fad7830cef53a3b89087b2021ec108696a7fad0eb005e 270338
mdadm_3.1.1.orig.tar.bz2
4fc26fa6a22c48274b2ad3c84d007d7beca01626093e187a911a932a91bf6c83 130649
mdadm_3.1.1-1.debian.tar.gz
de60e1b356d9097fd2db3ceac61cc18f8a7afe21b7342350ea1810305a6b7c8c 443322
mdadm_3.1.1-1_amd64.deb
53c04d0600e72f02b77f3613a09f1936bbe0a1d08aff6f4006034ae7cd800f9b 142072
mdadm-udeb_3.1.1-1_amd64.udeb
Files:
b5bfd366c92372625a9d0f513effdd18 1264 admin optional mdadm_3.1.1-1.dsc
4fd8e375a2ee314becd3196c1a250d98 270338 admin optional mdadm_3.1.1.orig.tar.bz2
4decd460d2cd8146bf3926d276fe427f 130649 admin optional
mdadm_3.1.1-1.debian.tar.gz
e5236180008c66690c26671050e7b737 443322 admin optional mdadm_3.1.1-1_amd64.deb
ccaf00bb6250c97c4ccb8365aad813ce 142072 debian-installer optional
mdadm-udeb_3.1.1-1_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAktfmjsACgkQIgvIgzMMSnWR+QCfSkAXCXMLRiofpqNznyG7EEyi
5/8An3YARsAmOkRpSk03x9y+ddiAYN9y
=LCh+
-----END PGP SIGNATURE-----
--- End Message ---
