<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Michael Tautschnig a écrit :
<blockquote cite="mid:20090428093858.GM27744@l04.local" type="cite">
<blockquote type="cite">
<pre wrap="">Executing: /lib/udev/vol_id -u /dev/sda2
Command /lib/udev/vol_id -u /dev/sda2 had exit code 4
Failed to obtain UUID for /dev/sda2
I originally wanted to have one swap slice on each disk, but in this
case the error is on the sdb swap partition:
Executing: /lib/udev/vol_id -u /dev/sdb2
Command /lib/udev/vol_id -u /dev/sdb2 had exit code 4
Failed to obtain UUID for /dev/sdb2
Any clue?
</pre>
</blockquote>
<pre wrap=""><!---->
That should only occur with some old mkswap versions that did not set up the
UUID, but that doesn't seem to be the case here:
Executing: udevsettle --timeout=10 && mkswap /dev/sda2
(STDOUT) Setting up swapspace version 1, size = 1069281 kB
(STDOUT) no label, UUID=3aa0ad8c-b7c9-428d-a2be-3511298c86af
So, mysteriously, that information is lost afterwards. Hmm, looking at the code
of vol_id it seems that parted might have overridden the volume id for
/dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run that failing
installation and, once it aborts, do
parted -s /dev/sda print
</pre>
</blockquote>
<br>
This looks ok:<br>
<br>
# parted -s /dev/sda print<br>
[...]<br>
Number Start End Size Type File system Flags<br>
1 32.3kB 535MB 535MB primary ext2 raid <br>
2 535MB 1604MB 1069MB primary linux-swap <br>
3 1604MB 320GB 318GB primary raid <br>
<br>
<br>
No raid on sda2, but vol_id disagrees:<br>
<br>
# /lib/udev/vol_id --export /dev/sda2<br>
ID_FS_USAGE=raid<br>
ID_FS_TYPE=linux_raid_member<br>
[...]<br>
<br>
So vol_id needs the --skip-raid option to return the uuid; a small
patch of setup-storage makes the installation work much better:<br>
<br>
--- Fstab.pm.~1~ 2009-04-22 11:41:56.000000000 +0000<br>
+++ Fstab.pm 2009-04-27 12:41:55.000000000 +0000<br>
@@ -94,7 +94,7 @@<br>
# or labels, use these if available<br>
my @uuid = ();<br>
&FAI::execute_ro_command(<br>
- "/lib/udev/vol_id -u $device_name", \@uuid, 0);<br>
+ "/lib/udev/vol_id --skip-raid -u $device_name", \@uuid, 0);<br>
<br>
# every device must have a uuid, otherwise this is an error (unless
we<br>
# are testing only)<br>
<br>
I don't know if this patch is a good idea, though, or if this behavior
of vol_id should be considered as a feature or a bug.<br>
<br>
-- <br>
Nicolas<br>
</body>
</html>