[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as Won't Fix. ** Changed in: mdadm (Ubuntu Lucid) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/550131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
Does this bug still require an sru to Lucid/Maverick? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/550131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
Well, not for maverick; we won't take any more SRUs to maverick. At this point, we probably want this issue fixed for quantal,precise,lucid. ** Changed in: mdadm (Ubuntu Maverick) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/550131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
@Steve, Sorry for the delay in my reply. As far as I can remember, the map is lost when we pivot to the *new* rootfs. The lost map is then reconstructed by calling the rebuild code. This map is what is needed for the proper reconstruction of the raid array. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/550131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
Surbhi, I'm afraid I don't understand the fix for this bug in https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/2139759/+files/mdadm_lp_bug_fixes.debdiff. The changelog comments say that the map will be rebuilt - but isn't this bug about needing to preserve the *state* from /var/run in the initramfs? How does rebuilding the map accomplish this? I understand that this is a backport from mdadm 3.1.4; I just am not sure how this change addresses the issue reported here. A test case for this particular bug would also be helpful for the SRU process, if someone can describe how to reproduce the original error (presumably in a test environment). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
** Also affects: mdadm (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: mdadm (Ubuntu Maverick) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
** Changed in: mdadm (Ubuntu Lucid) Status: New = In Progress ** Changed in: mdadm (Ubuntu Maverick) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550131 Title: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
Surbhi you're very welcome. I am glad if some of our analysing and comments turned out to be helpful for you, and you are actually about to get ubuntu's raid setup into shape. https://wiki.ubuntu.com/ReliableRaid I think with adopting the upstream version and mechanisms you're already clearing the way of many of the noted points for a reliable (cold hotplug) raid setup in ubuntu (and debian when they switch to an event based boot process). -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
Call for testing mdadm 2.7.1 autoassembly. For hitherto Ubuntu releases the mdadm package shall stay at 2.7.1 However Natty would have mdadm at 3.4.1. This document is intended to test the mdadm fixes for 2.7.1. Here is the rough procedure that needs to be followed: Testing auto-assembly of your md array when your rootfs lies on it: 1)Install the mdadm package and initramfs package kept at: https://edge.launchpad.net/~csurbhi/+archive/mdadm-autoassembly 2)Run /usr/share/mdadm/mkconf and ensure that your /etc/mdadm/mdadm.conf has the array definition. a) Save your original initramfs in /boot itself by say /boot/initrd-old.img. b) Then run update-initramfs -c -k your-kernel-version. Store this iniramfs as /boot/initrd-new.img. We shall use this initramfs as a safety net. If you cannot boot with the auto-assembly fixes, then you should not land in a foot in your mouth situation. Through grub's edit menu, you can then resort to this safety net by editing the initrd=initrd-new.img (or if this does not work for some random reason then resort back to your older initrd=initrd-old.img) This way you will be sure that you can still boot your precious system. c) Now comment or remove the ARRAY definitions from your /etc/mdadm/mdadm.conf and once again run the same “update-initramfs -c -k your-kernel-version” to generate a brand new initramfs. 3)Run mdadm –detail –scan and note the UUIDs in the array. Note the hostname stored in your array. Does it not match with your real hostname? Then we can fix that at the initramfs prompt that you inevitably will land at if you try auto-assembly. Also note the device components that form the root md-device. Keep this paper for cross checking when you reboot 4)Reboot. 5)If you are at the initramfs prompt here are the things that you should first ensure: a) ls /bin/hostname /etc/hostname - are these files present? b) run “hostname”. Does this show you the hostname that your system is intended to have? Is it the same as the contents of /etc/hostname. c) ls /var/run – Is this dir there? If you answer yes to the above three questions, then things are so far so good. Now run the following command: mdadm –assemble -U uuid /dev/md-name dev-components-listed here Your mdadm –detail –scan that you ran previously should have given you the component names if you dont know it right now. Hopefully you have them listed on your paper. Eg in my case I ran: mdadm –assemble -U uuid /dev/md0 /dev/sda1 /dev/sdb1 Again run: mdadm –detail –scan md-device and verify that the uuids are indeed updated and the hostname reflects the hostname that is stored /etc/hostname. You can now press Ctr+D and you should come back to the root prompt. However you still need to test auto-assembly of your root md device. To do that simple reboot and you should not see the face of initramfs this time. You should land gently on your root prompt as you expected. If you do not see the light of the rootfs prompt this way or using this initramfs, then as mentioned earlier, please avail your saved initrd images through grub. Skip the further steps in this case. Update the launchpad bugs, saying you could not get to the root prompt with manual assembly as well. First we need to get manual assembly fixed for you before worrying about auto-assembly. But hopefully this wont be the case. 6)If in the first place your uuid matched with that of the hostname, because you already had updated the array meta data with the -U uuid command, then with these packages, ideally, you should directly see the root prompt without any problem. 7)If either way, you still see initramfs and are not seeing the root prompt, then kindly upload the following on the respective launchpad bugs related to mdadm: a) output of /var/run/mdadm.map b) output of /proc/mdstat. c) output of hostname (in initramfs) d) output of mdadm –detail –scan root-md-device (once you have assembled the array manually and have got at the root prompt) In order to save this output when you are the initramfs prompt you should copy these files in /dev/ and then manually assemble your array. Once you get to the root prompt, you would find these files in /dev/. Please attach these to the launchpad bugs and we can start debugging from there. For auto-assembly of your non root devices, this should not bring you to initramfs, unless you have the device mounted with a fs using fstab and are not using “nobootwait” in the options section for your fs. Once you are in the root fs, and your non -root array is not up with auto-assembly, then you can very easily attach the output of the /var/run/mdadm.map and /proc/mdstat. If needed, I will also post a mdadm package which will output a lot of verbose information, to find out what is exactly going wrong. Thanks very much for your help. Remember that this is a test package and your help is extremely appreciated :) I have tested these packages on test virtual machines. --
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
@Jools, @ceg, Thanks a lot for your insightful comments and making Ubuntu better. I have done the fixes mostly, based on these comments. The patches are based on the source code in neil-browns git repository and a few initramfs fixes which are applicable to Ubuntu (which are again based on the bugs on launchpad). Do let me know the output of the test ppas. At present these are only for maverick. I shall be uploading the ones based for lucid soon enough! Thanks again :-) -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
@Stephan B, Yes, you are absolutely correct. I have done something similar in initramfs kept at the above mentioned ppa. Thanks a lot for the valuable suggestion. Please do let me know if the ppa works for you or not :) -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
** Branch linked: lp:~csurbhi/+junk/mdadm.fixes -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
Thank you for getting into this, Surhbi. I managed to hack a solution
into my initramfs scripts, maybe you can extract something useful for
the good solution : )
In /usr/share/initramfs/hooks/mdadm: Create /var/run/mdadm in initramfs
mkdir -p ${DESTDIR}/var/run/mdadm
Create /usr/share/initramfs/scripts/init-bottom/mdadm: Script that copies
/var/run/mdadm to the real /var/run/
#! /bin/sh
case $1 in
prereqs)
exit 0
;;
esac
if [ -r /var/run/mdadm/map ]; then
mkdir -p /dev/.initramfs/varrun/mdadm
cp /var/run/mdadm/map /dev.initramfs/varrun/mdadm/
fi
Using 10.04 / Lucid, /etc/init/mounted-varrun.conf then copies the
mapfile to the newly created /var tmpfs. HTH
--
maps file not getting copied from initramfs to real rootfs (loosing state,
race, misconfig)
https://bugs.launchpad.net/bugs/550131
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
just to note with new mdadm 3.1.4+ it uses /dev/.mdadm/map for the location which is available from the initramfs stage and once root is mounted. -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)
** Summary changed: - initramfs missing /var/run/mdadm/ dir (loosing state, race, misconfig) + maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) ** Changed in: mdadm (Ubuntu) Status: Confirmed = In Progress ** Changed in: mdadm (Ubuntu) Assignee: (unassigned) = Surbhi Palande (csurbhi) -- maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig) https://bugs.launchpad.net/bugs/550131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
