Robert Millan wrote, on 06/01/08 02:48:
...
You can use gdb to determine. Try building a debug grub-mkdevicemap
(DEB_BUILD_OPTIONS=nostrip,noopt,debug), run it with gdb and interrupt it
where it has hung, then obtain a backtrace ("bt").
If you could give me the precise debuild or dpkg-buildpackage commands
to run after running
apt-get source grub2
I will at least know how to do this.
Thanks for the suggestion... I'm not sure how to reproduce the problem
condition as I had done a week's worth of twice-daily upgrades to Debian
unstable before this lock-up.
What does grub-mkdevicemap do?
It scans your devices and generates /boot/grub/device.map.
Even after scanning through /usr/share/doc/grub-pc including the
changelog and reading the last few months of the grub-devel mailing list
didn't tell me this. Should there be any manual pages or a README that
lists the executables and what they do?
As a general advice, when you find a problem like this one, try to obtain some
debugging output before trying to work around it. Otherwise it's almost
impossible to fix unreproducible problems :-(
Yes I know /-:
Please see if you can get into the same situation again. If not, we'll
probably have to close this bug..
My guess is that one of the upgrades in the previous week had been
playing with device files, and since udev is active in my set-up, had
created new device files in /dev/.static/dev but since udev hadn't been
restarted by a reboot, something went wrong with the device scan.
The only files in /dev/.static/dev that looked like they might have been
installed between my last reboot and the grub-pc upgrade were sg0 to
sg16 - I have no idea what package would have created them, and they
don't end up under /dev outside of /dev/.static/dev after a reboot.
As Debian is put together to reduce the need to reboot as much as
possible, your message about building a debug build will give the next
person who may encounter the problem and uses reportbug a clue on what
to do to better identify the problem.
Do you think that the grub-pc upgrade script and /usr/sbin/update-grub
shell script should indicate that they are running grub-mkdevicemap (and
when they have finished running grub-mkdevicemap) in case anyone else
hits this problem?
Regards,
Arthur.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
