Jason,
see below.
Leidner, Jason (JLEIDNER) wrote:
>
> <config>
>
> <disk dev="/dev/sda" label_type="msdos" unit_of_measurement="MB">
> <!--
> This disk's output was brought to you by the partition tool
> "parted",
> and by the numbers 4 and 5 and the letter Q.
> -->
> <part num="1" size="101.944" p_type="primary" p_name="-"
> flags="boot" />
> <part num="2" size="*" p_type="primary" p_name="-" flags="lvm"
> />
> </disk>
Here is the first problem: partition #2 must have the attribute
lvm_group="VolGroup00" that is missing. Adding it manually is the quick
& dirty solution to resolve this problem.
However the code from 3.6.3 to get the right volume group and put that
attribute in the autoinstallscript.conf is the following:
# Get physical volume information -AR-
my $cmd = "pvs --noheadings --separator : /dev/$part 2>/dev/null";
open (PV_INFO, "$cmd|");
unless (eof(PV_INFO)) {
my @pv_data = split(/:/, <PV_INFO>);
my $vg_name = $pv_data[1];
# This partition will become part to the volume group
$vg_name -AR-
print DISK_FILE qq( lvm_group="$vg_name");
}
close(PV_INFO);
As you can see it simply gets the info with a `pvs --noheadings
--separator : /dev/sda2`... so again... could you run also this command
in your golden client?
BTW in the release 3.7.3 we've changed the previous code into this (it's
more reliable and supports also LVM1):
# Get physical volume information -AR-
my $cmd = "pvdisplay -c /dev/$part 2>/dev/null";
open (PV_INFO, "$cmd|");
unless (eof(PV_INFO)) {
my @pv_data = split(/:/, <PV_INFO>);
my $vg_name = $pv_data[1];
# This partition will become part to the volume group
$vg_name -AR-
print DISK_FILE qq( lvm_group="$vg_name");
}
close(PV_INFO);
So to be sure if it'll work in 3.7.3 you could run also a `pvdisplay -c
/dev/sda2` and post the output...
> Here is the output of the other commands you listed on my goldenclient.
>
>
> #pvs -o pv_fmt
> Fmt
> Lvm2
OK, so you're using LVM2... that's good! ;-)
>
> #fdisk -l
> Disk /dev/sda: 218.9GB, 218999291904bytes
> 255heads, 63 sectors/track, 26625 cylinders
>
> Units=cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks ID System
> /dev/sda1 * 1 13 104391 83 Linux
> /dev/sda2 14 26625 213760890 8e Linux LVM
>
> #pvs
> PG VG Fmt Attr Psize Pfree
> /dev/sda2 VolGroup00 lvm2 a- 203.84G 128.00M
>
> #vgs
> VG #PV #LV #SN Attr Vsize Vfree
> VolGroup00 1 2 0 wz--n 203.84G 128.00M
>
> #lvs
> LV VG Attr Lsize Origin Snap% Move
> Log Copy%
> LogVol00 VolGroup00 -wi-ao 201.78G
> LogVol01 VolGroup00 -wi-ao 1.94G
>
> As far as the commands you wanted me to run on my client when the
> autoinstall fails... Here they are:
>
> #blockdev --getro /dev/sda
> 0
>
> #cat /proc/diskstats
> 1 0 ram0 0 0 0 0 0 0
> 0 0 0 0 0
> 1 1 ram1 0 0 0 0 0 0
> 0 0 0 0 0
> 1 2 ram2 0 0 0 0 0 0
> 0 0 0 0 0
> 1 3 ram3 0 0 0 0 0 0
> 0 0 0 0 0
> 1 4 ram4 0 0 0 0 0 0
> 0 0 0 0 0
> 1 5 ram5 0 0 0 0 0 0
> 0 0 0 0 0
> 1 6 ram6 0 0 0 0 0 0
> 0 0 0 0 0
> 1 7 ram7 0 0 0 0 0 0
> 0 0 0 0 0
> 1 8 ram8 0 0 0 0 0 0
> 0 0 0 0 0
> 1 9 ram9 0 0 0 0 0 0
> 0 0 0 0 0
> 1 10 ram10 0 0 0 0 0 0
> 0 0 0 0 0
> 1 11 ram11 0 0 0 0 0 0
> 0 0 0 0 0
> 1 12 ram12 0 0 0 0 0 0
> 0 0 0 0 0
> 1 13 ram13 0 0 0 0 0 0
> 0 0 0 0 0
> 1 14 ram14 0 0 0 0 0 0
> 0 0 0 0 0
> 1 15 ram15 0 0 0 0 0 0
> 0 0 0 0 0
> 22 0 hdc 0 0 0 0 0 0
> 0 0 0 0 0
> 9 0 md0 0 0 0 0 0 0
> 0 0 0 0 0
> 8 0 sda 7 15 176 75 1 0
> 8 0 0 75 75
> 7 0 loop0 0 0 0 0 0 0
> 0 0 0 0 0
> 7 1 loop1 0 0 0 0 0 0
> 0 0 0 0 0
> 7 2 loop2 0 0 0 0 0 0
> 0 0 0 0 0
> 7 3 loop3 0 0 0 0 0 0
> 0 0 0 0 0
> 7 4 loop4 0 0 0 0 0 0
> 0 0 0 0 0
> 7 5 loop5 0 0 0 0 0 0
> 0 0 0 0 0
> 7 6 loop6 0 0 0 0 0 0
> 0 0 0 0 0
> 7 7 loop7 0 0 0 0 0 0
> 0 0 0 0 0
>
All seems ok about this problem. Honestly dunno why dd fails to write to
your disk... what happens if you run for example a `dd if=/dev/zero
of=/dev/sda bs=512 count=1` in the console (after the autoinstallation
fails)? what's the return code?
Regards,
-Andrea
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
