[sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Hello, I'm trying to image an new (no OS installed) Dell PowerEdge SC1435 server with a CentOS5 UYOK image. The server has the Perc5i controller with two mirrored 80GB SATA drives. The imaging keeps failing with the following error: EXT3-fs: unable to read superblock and then the kernel goes into panic mode. I've built the client image with UYOK and CentOS 5 installs fine from scratch on a similar server. Any ideas on what can be done to overcome this? Thanks in advance. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee (now more about systemconfigurator)
On Wed, Feb 20, 2008 at 1:38 PM, Andrea Righi <[EMAIL PROTECTED]> wrote: > > 2008-2-20 11:42:27 [Boot::Grub :: Line 406] Mount = /boot; Path = > > /grub/splash.xpm.gz > > Probing devices to guess BIOS drives. This may take a long time. > > 2008-2-20 11:42:28 [Boot::Grub :: Line 290] generated device map file > > /tmp/grub.devices > > Maybe the problem here is grub, that is not able to create a valid > device.map with xvda devices. > > It would be interesting to see the content of the /tmp/grub.devices. > > You could be able to get this file running the following command at the > end of the imaging (inside a post-install script would be perfect): > > grub --no-floppy --batch --device-map=/tmp/grub.devices > cat /tmp/grub.devices Nothing ends up in the tmp file, and in fact that pretty much blocks the autoinstall script from moving forward as it puts itself into a grub shell. A d frees me :) So for now, i just don't bother with the systemconfigurator and things work (and for virtual's this is probably 100% okay, since there will be no hardware differences between them). I'm more than happy to work thru this a bit more. My next steps are to actually move the systemimager host piece local to the virtual host, so that I'm not going over the network to create an image.. Although Xen has some nice clone options that would work for like virtuals. Tory - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
Patch applied and yes this solves the problem. Have not yet had a chance
to image
to a client.
Thanks
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3050
Email: [EMAIL PROTECTED]
Andrea Righi <[EMAIL PROTECTED]>
2008/02/20 07:39
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED], Tory M Blue <[EMAIL PROTECTED]>
cc
sisuite-users@lists.sourceforge.net
Subject
Re: [sisuite-users] SI, XEN, FC6 wh
Andrea Righi wrote:
> Tory M Blue wrote:
>> note what it's in my grub.conf after the mess
>>
>> # This file is generated by System Configurator. #
>> ##
>> # The number of seconds to wait before booting.
>> timeout 5
>> # The default kernel image to boot.
>> default 0
>> # The splash image (this line will be empty if nothing was found)
>> splashimage=/grub/splash.xpm.gz
>>
>> # kernel0
>> title fc6xen-virt_
>> root
>> kernel ro root=LABEL=/ ro root=LABEL=/ console=xvc0
>> initrd
>>
>
> We also need to patch UYOK stuff. See create_systemconfig_conf() in
> sbin/si_prepareclient.
>
Tory, David,
could you check if the following patch fixes both your problems?
Thanks,
-Andrea
---
Index: lib/SystemImager/UseYourOwnKernel.pm
===
--- lib/SystemImager/UseYourOwnKernel.pm(revision 4390)
+++ lib/SystemImager/UseYourOwnKernel.pm(working copy)
@@ -345,18 +345,30 @@
#
# and not a directory
if( -d $file ) { return undef; }
+#
+# skip symlinks
+if( -l $file ) { return undef; }
+#
+# skip .bak files
+if( $file =~ /\.bak$/ ) { return undef; }
+#
+# eliminate vmlinux files on RH
+if( $file =~ m/^vmlinux$/ ) { return undef; }
+#
+# eliminate ramdisks
+if( $file =~ m/initrd/ ) { return undef; }
+#
+# eliminate memtest
+if( $file =~ m/^memtest/ ) { return undef; }
+#
+# eliminate message
+if( $file =~ m/^message/ ) { return undef; }
#
# Get output from "file" for elimination by identification tests
-my $cmd = "file -b $file";
+my $cmd = "file -bz $file";
open(INPUT,"$cmd|") or die("Couldn't run $cmd to get INPUT");
my ($input) = ();
-#
-# eliminate vmlinux files on RH
-if( $input =~ m/ELF (32|64)-bit LSB executable,/ ) {
return undef; }
-#
-# eliminate compressed data (eg. ramdisk)
-if( $input =~ m/gzip compressed data,/ ) { return undef;
}
# eliminate cpio archives (eg. ramdisk)
if( $input =~ m/cpio archive/ ) { return undef; }
# eliminate cramfs files (eg. ramdisk)
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee (now more about systemconfigurator)
Tory M Blue wrote: > Well I spoke too soon, > > Systemconfigurator completely borked things :) Wait.. one patch per time... ;-) [snip] > 2008-2-20 11:42:27 [Boot::Grub :: Line 406] Mount = /boot; Path = > /grub/splash.xpm.gz > Probing devices to guess BIOS drives. This may take a long time. > 2008-2-20 11:42:28 [Boot::Grub :: Line 290] generated device map file > /tmp/grub.devices Maybe the problem here is grub, that is not able to create a valid device.map with xvda devices. It would be interesting to see the content of the /tmp/grub.devices. You could be able to get this file running the following command at the end of the imaging (inside a post-install script would be perfect): grub --no-floppy --batch --device-map=/tmp/grub.devices cat /tmp/grub.devices -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee (now more about systemconfigurator)
Well I spoke too soon,
Systemconfigurator completely borked things :)
Editing files for actual disk configuration...
/etc/fstab
/etc/systemconfig/systemconfig.conf
/boot/grub/menu.lst
/etc/grub.conf
mount /dev /a/dev -o bind || shellout
Detecting systemconfigurator:
---
systemconfigurator - 2.2.11
Written by Sean Dague, Donghwa John Kim, et al.
Copyright (C) 2001-2002 International Business Machines
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
---
2008-2-20 11:42:27 [Network :: Line 58] Setting up network type
Network::LinuxConf
2008-2-20 11:42:27 [Boot::YaBoot :: Line 93] YaBoot executable is set to: .
2008-2-20 11:42:27 [Boot :: Line 66] Attempting to setup Boot::YaBoot
2008-2-20 11:42:27 [Boot :: Line 66] Attempting to setup Boot::Iseries
2008-2-20 11:42:27 [Boot :: Line 66] Attempting to setup Boot::EFI
2008-2-20 11:42:27 [Boot :: Line 66] Attempting to setup Boot::Elilo
2008-2-20 11:42:27 [Boot::Lilo :: Line 76] Lilo executable set to: .
2008-2-20 11:42:27 [Boot :: Line 66] Attempting to setup Boot::Lilo
2008-2-20 11:42:27 [Boot::Grub :: Line 132] grub supports --no-floppy argument.
2008-2-20 11:42:27 [Boot::Grub :: Line 107] Grub executable set to:
/sbin/grub-install.
2008-2-20 11:42:27 [Boot :: Line 66] Attempting to setup Boot::Grub
2008-2-20 11:42:27 [Boot::Grub :: Line 151] bootloader = /sbin/grub-install
2008-2-20 11:42:27 [Boot::Label :: Line 105] Loading labels for all devices...
2008-2-20 11:42:27 [Boot::Label :: Line 72] getting label for /dev/xvda1
2008-2-20 11:42:27 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda1
= /dev/xvda1: LABEL="/boot"
2008-2-20 11:42:27 [Boot::Label :: Line 75] label is /boot
2008-2-20 11:42:27 [Boot::Label :: Line 72] getting label for /dev/xvda2
2008-2-20 11:42:27 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda2
= /dev/xvda2: LABEL="/tmp"
2008-2-20 11:42:27 [Boot::Label :: Line 75] label is /tmp
2008-2-20 11:42:27 [Boot::Label :: Line 72] getting label for /dev/xvda3
2008-2-20 11:42:27 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda3
= /dev/xvda3: LABEL="SWAP-xvda3"
2008-2-20 11:42:27 [Boot::Label :: Line 75] label is SWAP-xvda3
2008-2-20 11:42:27 [Boot::Label :: Line 72] getting label for /dev/xvda4
2008-2-20 11:42:27 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda4 =
2008-2-20 11:42:27 [Boot::Label :: Line 72] getting label for /dev/xvda5
2008-2-20 11:42:27 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda5
= /dev/xvda5: LABEL="/var"
2008-2-20 11:42:27 [Boot::Label :: Line 75] label is /var
2008-2-20 11:42:27 [Boot::Label :: Line 72] getting label for /dev/xvda6
2008-2-20 11:42:27 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda6
= /dev/xvda6: LABEL="/"
2008-2-20 11:42:27 [Boot::Label :: Line 75] label is /
2008-2-20 11:42:27 [Boot::Label :: Line 107] Label structure is as
follows: $VAR1 = {
'/var' => '/dev/xvda5',
'/' => '/dev/xvda6',
'SWAP-xvda3' => '/dev/xvda3',
'/tmp' => '/dev/xvda2',
'/boot' => '/dev/xvda1'
};
2008-2-20 11:42:27 [Boot::Grub :: Line 406] Mount = /boot; Path =
/grub/splash.xpm.gz
Probing devices to guess BIOS drives. This may take a long time.
2008-2-20 11:42:28 [Boot::Grub :: Line 290] generated device map file
/tmp/grub.devices
2008-2-20 11:42:28 [Boot::Grub :: Line 247] d = /dev/xvda1
2008-2-20 11:42:28 [Boot::Grub :: Line 250] Device: xvda; Part: 1
Use of uninitialized value in concatenation (.) or string at
/usr/lib/systemconfig/Boot/Grub.pm line 252.
2008-2-20 11:42:28 [Boot::Grub :: Line 252] Biosdev:
Use of uninitialized value in substitution (s///) at
/usr/lib/systemconfig/Boot/Grub.pm line 256.
Use of uninitialized value in concatenation (.) or string at
/usr/lib/systemconfig/Boot/Grub.pm line 409.
2008-2-20 11:42:28 [Boot::Label :: Line 105] Loading labels for all devices...
2008-2-20 11:42:28 [Boot::Label :: Line 72] getting label for /dev/xvda1
2008-2-20 11:42:28 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda1
= /dev/xvda1: LABEL="/boot"
2008-2-20 11:42:28 [Boot::Label :: Line 75] label is /boot
2008-2-20 11:42:28 [Boot::Label :: Line 72] getting label for /dev/xvda2
2008-2-20 11:42:28 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda2
= /dev/xvda2: LABEL="/tmp"
2008-2-20 11:42:28 [Boot::Label :: Line 75] label is /tmp
2008-2-20 11:42:28 [Boot::Label :: Line 72] getting label for /dev/xvda3
2008-2-20 11:42:28 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda3
= /dev/xvda3: LABEL="SWAP-xvda3"
2008-2-20 11:42:28 [Boot::Label :: Line 75] label is SWAP-xvda3
2008-2-20 11:42:28 [Boot::Label :: Line 72] getting label for /dev/xvda4
2008-2-20 11:42:28 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda4 =
2008-2-20 11:42:28 [Boot::Label :: Line 72] getting label for /dev/xvda5
2008-2-20 11:42:28 [Boot::Label :: Line 49] blkid -s LABEL /dev/xvda5
= /dev/xvda5: LABEL="/var"
2008-2-20 11:42:28 [Boot::Label :: Line 75] label is /var
2008-2-20 11:42:28 [Boot::Label :: Line 72] getting label for /dev/xvda6
2008-2-2
[sisuite-users] SI, XEN, FC6 wheeee
On Feb 20, 2008 11:21 AM, Tory M Blue <[EMAIL PROTECTED]> wrote: > On Feb 20, 2008 6:38 AM, Andrea Righi <[EMAIL PROTECTED]> wrote: > > Andrea Righi wrote: > Tory, David, > > > > could you check if the following patch fixes both your problems? > > > > Thanks, > > -Andrea > Seems to have worked for me. Didn't have to specify kernel and it > didn't seem to have any issues. In fact my systemconfig.conf file > "looks right". Okay, ran a standard image thru and it appears that it works (even without the xda added to 2 locations) DISKORDER=sd,cciss,ida,rd,hd,xvd -and- hd | sd | xvd ) for dev in `cat $diskfile | sed -ne "s/.*\($type[a-z]\+\).*/\1/p" | sort -u` ; do It was able to drop back to the file created by prepareclient and understand that the xvd was the device to use (very nice). Interesting though is that ext3 was not loaded in my prepareclient kernel, so it failed at ext3 type unknown. Switching everything to ext2 (fine for development virtuals), worked fine. (But I know how to fix this). I would like to clean some of this up though. Not sure we should really need to run modprobe after the first failure :) -Tory run_autoinstall_script >>> /scripts/devmtx.master get_arch enumerate_disks xvda xvdb DISKS=2 Load software RAID modules. modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep Load device mapper driver (for LVM). modprobe: could not parse modules.dep Load additional filesystem drivers. modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep modprobe: could not parse modules.dep mkswap -v1 /dev/xvda3 -L SWAP-xvda3 || shellout - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
On Feb 20, 2008 6:38 AM, Andrea Righi <[EMAIL PROTECTED]> wrote: > Andrea Righi wrote: Tory, David, > > could you check if the following patch fixes both your problems? > > Thanks, > -Andrea Seems to have worked for me. Didn't have to specify kernel and it didn't seem to have any issues. In fact my systemconfig.conf file "looks right". I'm going to reimage with a pretty much the created autoinstallscript.conf file and see what it does to my virtual domain. Thanks again A! I'll look for the X86-64 box Tory - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
On Feb 20, 2008 2:43 AM, Andrea Righi <[EMAIL PROTECTED]> wrote: > Tory, first of all that's simply great! I've just started to work on Xen > and SI integration, so I'm really interested in this topic!!! > > Question: are you running Xen in HVM mode to image the VM clients? And > after the imaging you can choose to switch to paravirtualized mode or > simply reboot and continue to use HVM, right? Currently I'm imaging inside the vm, allowing SI to reboot once done and I can console, shutdown, destroy etc. During the creation I'm in the vm (thus console) and so I can watch what SI is doing and if it fails, I can interact just like if I was imaging a standalone system (watching the console or terminal). Obviously one can simply create an domain in ram, but I like having the full domain available,, Using a lvm create a small 10gig chunk that SI sees as a xvd* disk, it partitions it nicely and bingo no issues. In fact just handed this off to one of my guys and they quickly built up a postgres install and is doing some basic testing of 8.3 in the domain (need to get off the virtual speak, and start using domain, or vice versa) Tory Trying the patch - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
Andrea Righi wrote:
> Tory M Blue wrote:
>> note what it's in my grub.conf after the mess
>>
>> # This file is generated by System Configurator. #
>> ##
>> # The number of seconds to wait before booting.
>> timeout 5
>> # The default kernel image to boot.
>> default 0
>> # The splash image (this line will be empty if nothing was found)
>> splashimage=/grub/splash.xpm.gz
>>
>> # kernel0
>> title fc6xen-virt_
>> root
>> kernel ro root=LABEL=/ ro root=LABEL=/ console=xvc0
>> initrd
>>
>
> We also need to patch UYOK stuff. See create_systemconfig_conf() in
> sbin/si_prepareclient.
>
Tory, David,
could you check if the following patch fixes both your problems?
Thanks,
-Andrea
---
Index: lib/SystemImager/UseYourOwnKernel.pm
===
--- lib/SystemImager/UseYourOwnKernel.pm(revision 4390)
+++ lib/SystemImager/UseYourOwnKernel.pm(working copy)
@@ -345,18 +345,30 @@
#
# and not a directory
if( -d $file ) { return undef; }
+#
+# skip symlinks
+if( -l $file ) { return undef; }
+#
+# skip .bak files
+if( $file =~ /\.bak$/ ) { return undef; }
+#
+# eliminate vmlinux files on RH
+if( $file =~ m/^vmlinux$/ ) { return undef; }
+#
+# eliminate ramdisks
+if( $file =~ m/initrd/ ) { return undef; }
+#
+# eliminate memtest
+if( $file =~ m/^memtest/ ) { return undef; }
+#
+# eliminate message
+if( $file =~ m/^message/ ) { return undef; }
#
# Get output from "file" for elimination by identification tests
-my $cmd = "file -b $file";
+my $cmd = "file -bz $file";
open(INPUT,"$cmd|") or die("Couldn't run $cmd to get INPUT");
my ($input) = ();
-#
-# eliminate vmlinux files on RH
-if( $input =~ m/ELF (32|64)-bit LSB executable,/ ) { return
undef; }
-#
-# eliminate compressed data (eg. ramdisk)
-if( $input =~ m/gzip compressed data,/ ) { return undef; }
# eliminate cpio archives (eg. ramdisk)
if( $input =~ m/cpio archive/ ) { return undef; }
# eliminate cramfs files (eg. ramdisk)
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Problems with RHEL5 and xen kernel
David Livingstone wrote: > Andrea, > > Decided to take the plunge and install RHEL5.1 with systemimager > 4.0.2-1. By default > on install the xen kernel is installed. As you will see below I've had > some errors > running si_prepareclient. Looked at some list entries(Nestor thread Oct/Nov) > so I attempted to run with kernel and module options which was > successful. The > --no-uyok fails. > > Thanks > It seems the same problem (one of them) reported by Tory in the "SI, XEN, FC6 wh" thread. I'll look at it ASAP. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
Tory M Blue wrote: > note what it's in my grub.conf after the mess > > # This file is generated by System Configurator. # > ## > # The number of seconds to wait before booting. > timeout 5 > # The default kernel image to boot. > default 0 > # The splash image (this line will be empty if nothing was found) > splashimage=/grub/splash.xpm.gz > > # kernel0 > title fc6xen-virt_ > root > kernel ro root=LABEL=/ ro root=LABEL=/ console=xvc0 > initrd > We also need to patch UYOK stuff. See create_systemconfig_conf() in sbin/si_prepareclient. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
Tory M Blue wrote:
> Okay after hard coding a few things in files, I now have a working xen
> deployment. (But before you ask!)
>
> I would like to unhack many things and get the flexibility back that
> SI provides.
Tory, first of all that's simply great! I've just started to work on Xen
and SI integration, so I'm really interested in this topic!!!
Question: are you running Xen in HVM mode to image the VM clients? And
after the imaging you can choose to switch to paravirtualized mode or
simply reboot and continue to use HVM, right?
Comments below.
>
> So ignoring the outstanding xen issues, lets get into the sI.
>
> autoinstallscript.conf, does not understand virtual disks xvd* is
> unknown to it so Diskorder is something that cannot be used and the
> system will not find the correct disk..
>
> DISKORDER=sd,cciss,ida,rd,hd <--- xvd would be nice
>
> Otherwise I force the device information
>
> if [ -z $DISKORDER ] ; then
> DISK0=/dev/xvda <-- works
> elif [ -z $DISK0 ] ; then
> echo "Undefined: DISK0"
> shellout
This is true if you used --autodetect-disks in si_getimage (or
si_mkautoinstallscript), but it should work if you don't use this
option. Just replace all the /dev/sda occurrences to /dev/xdva in
/var/lib/systemimager/images/YOURIMAGE/etc/systemimager/autoinstallscript.conf
and re-create the .master script by si_mkautoinstallscript.
Anyway, the --autodetect-disks issue can be easily fixed as you
suggested adding xvd to the DISKORDER list.
Index: lib/SystemImager/Server.pm
===
--- lib/SystemImager/Server.pm (revision 4388)
+++ lib/SystemImager/Server.pm (working copy)
@@ -1969,7 +1969,7 @@
if (/^\s*${delim}SET_DISKORDER${delim}\s*$/) {
# Set or unset disk autodetection.
if ($autodetect_disks) {
-print $MASTER_SCRIPT
qq(DISKORDER=sd,cciss,ida,rd,hd\n);
+print $MASTER_SCRIPT
qq(DISKORDER=sd,cciss,ida,rd,hd,xvd\n);
} else {
print $MASTER_SCRIPT qq(DISKORDER=\n);
}
>
> However if I do stop the SI process and drop into a shell, fdisk see's
> the disk just fine..
>
> /scripts/pre-install # fdisk -l
>
> Disk /dev/xvda: 10.7 GB, 10737418240 bytes
> 255 heads, 63 sectors/track, 1305 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Disk /dev/xvda doesn't contain a valid partition table
>
> So unless I hard code xvda in various locations my installation will
> fail. So how do I go about getting things a bit less rigid again?
>
>
> Now systemconfigurator, might be caused by the above issue, however
> systemconfigurator barfs all over the tasks of setting up my
> bootloader. (so much that I had to mount my partitions and edit
> grub.conf by hand)..
Yes, as expected, SC doesn't know what /dev/xdv* are, I suppose that's
very similar to the SI issue above. I'll look at it.
>
> Now I believe since my image is complete, I can skip the
> systemconfigurator bootloader piece and just have it deal with
> network, however again I would love to keep all components of SI in
> tact.
>
> And Andrea, I owe you a donation, send me a link (not for this, but
> for the last years worth of assistance (and yes i tend to jump from
> one implementation to another.)) I want to be able to use SI for
> everything! (and the new win stuff you announced, i'll try that as
> well!)))
Well, I've never understood how the donation system works on SF.net...
if you wanna try :-) Anyway, as I said in a previous mail, we would
really need a x86_64 server to build deb and RPM packages for this
architecture. Do you have a x86_64 machine online? a non-privileged
account would be enough to build SI packages, or better, you could
contribute building x86_64 packages for us if you're interested.
BTW have you registered your SI installations on the cluster map? ;-)
Thanks,
-Andrea
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
