Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Tory M Blue wrote: Well that makes sense since my image which is what is used when the chroot /a/ happens, does not have these devices, since again it started life as an sda equipped server. So using the /dev filesystem on the image will totally fail, I guess there is a step that is missing that creates the new /dev/hda* devices.? This step is automatically done by the autoinstall script, but you should have the following line into your autoinstallscript.conf: boel devstyle=udev/ Check if you have it and re-create your .master autoinstall script (via si_mkautoinstallscript). With udev devstyle a simple mount /dev /a/dev -o bind is performed, before chroot-ing into the image. Otherwise if devstyle=static nothing will be performed, since everything is supposed to be already present into the image. -Andrea - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Jan Groenewald wrote: I had the same hda/sda trouble. It was an ide-scsi module, which I had to add to a pre-UYOK SI kernel, but that is another story. Yes... this is another bad story, but I think we should address it in some ways... it should depend on the udev config, so a very bad, ugly, orrible hack would be to copy the /etc/udev/ conf into the initrd_template and re-create the boot package via si_prepareclient or si_mkbootpackage (kernel + initrd.img). If I'm not wrong Bernard tested it with a CentOS, but IMHO passively copying the /etc/udev dir into the initrd_template should be done only in the strictly necessary cases (think at all the possible dependencies that the udev conf files could require...) Ideas? -Andrea - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
You could simply re-run mkinitrd/grub at the end of the image copy in the post-install script -Drew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrea Righi Sent: Monday, June 04, 2007 7:00 AM To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Back, have some time,. SDA to HDA imaging Jan Groenewald wrote: I had the same hda/sda trouble. It was an ide-scsi module, which I had to add to a pre-UYOK SI kernel, but that is another story. Yes... this is another bad story, but I think we should address it in some ways... it should depend on the udev config, so a very bad, ugly, orrible hack would be to copy the /etc/udev/ conf into the initrd_template and re-create the boot package via si_prepareclient or si_mkbootpackage (kernel + initrd.img). If I'm not wrong Bernard tested it with a CentOS, but IMHO passively copying the /etc/udev dir into the initrd_template should be done only in the strictly necessary cases (think at all the possible dependencies that the udev conf files could require...) Ideas? -Andrea - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
That's why you should run mkinitrd at the end of your imaging process. I fixed this entire process a long long time ago before I found kickstart which is much easier. You have to detect wether or not it is sd or hd, and then you have to make a new initrd. -Drew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tory M Blue Sent: Wednesday, May 30, 2007 1:35 AM To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Back, have some time,. SDA to HDA imaging Thanks for the various responses. My SATA/SDA image has ZERO hda* devices, so it mounts up the right dir /dev/ but only see's /dev/hdc, which is not in this system. Are you saying there is another directory other then /dev that would have the devices? In FC*? I don't see it, seems that this directory is completely empty in my image and appears to be created on boot. My issue is purely that I had no hda* devices listed in /dev of my image (because the image was not on a IDE system and thus used megaraid-sas to create the /dev/sda devices. It's working now, by solely, rsync'in the /dev/hda* files from a ide image, that was the only change. So I'm having a hard time with the other suggestions (not saying they are bad, just not seeing them fit my scenario).. Thanks Tory On 5/29/07, Jan Groenewald [EMAIL PROTECTED] wrote: Hi I had the same hda/sda trouble. It was an ide-scsi module, which I had to add to a pre-UYOK SI kernel, but that is another story. SI didn't think my master script needed to mount /dev /a/dev/ -o bind but in fact it was needed for chroot /a/ systemconfiguraror so that the part doing grub-install can see the hard drive devices. Worse, I had to, after this mount, before chroot /a/ systemconfigurator, ln -s /dev/hda1 /dev/sda1 and it actually worked. Inelegant, obscure, and took to long to find. The installer sees hda, the images sees sda. ide-scsi yuckness. Of course, yesterday Ubuntu Feisty 7.04 upgraded the kernel package linux-image-2.6.20-16-generic, (from -15) and now, still via ide-scsi, the Dell Optiplexes now again show hda and not sda, like older kernels, like the installer, but not like Feisty since release up to now :-P Why the sudden reversal? /Me has not ventured to lkml or feisty changelogs... OK, had a look now at the Feisty changelogs for that kernel, and it is a mostly networking related security upgrade, with no mention of ide-scsi. Irunno... OK, so the stupid ln -s is no longer necessary, but the dev bind-mount is still necessary, somehow mkautoinstallscript thinks I don't need it for this image. The fstab file also had to be changed in the master script to be sda, and now back to hda. UUIDs didn't seem to work despite the labels being set in the master script during partitioning. However grub booted a root partition by label. Perhaps this is also solved now. To debug all this read the master script, shellout at the appropriate place, and test some things in the installer environment and in the chroot. I run stock Ubuntu Dapper 6.06.1 LTS servers, and teach people to use these, and it is desireable to start off with the versions of software already packaged for this. It means SI 3.2.3, fairly old. Aside: For the ide-scsi kernel module I just downloaded the 3.8 source, recompiled just for the client boot kernel with one extra module, and took the kernel and initrd out and put it in /var/lib/tfptboot where it was needed, in a 3.2.3 systemimager-server installation. Even in Ubuntu Feisty 7.04 the packaged version of SI is 3.2.3, there seems to be not a lot of movement to UYOK and later upstream versions? SI bo! cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Same Failure. This appears to be 100% in systemconfigurator, since the
drive is partitioned, filesystems created and the image rsycnd, it
just fails to install the bootloader.
I've even tried to run the various systemconfigurator commands locally
with the same results..
Single master drive (IDE) and single secondary master (CDROM)
Version info:
systemconfigurator-2.2.9-1
systemimager-server-3.9.0-1
systemimager-client-3.9.0-1
systemimager-i386boot-standard-3.9.0-1
systemimager-common-3.9.0-1
systemimager-i386initrd_template-3.9.0-1
Grub Version in image:and server
grub (GNU GRUB 0.97)
ERROR:
sent 116 bytes received 66 bytes 364.00 bytes/sec
total size is 0 speedup is 0.00
Editing files for actual disk configuration...
/dev/sda - /dev/hda
/etc/fstab
/boot/grub/menu.lst
/etc/grub.conf
ÇÇÇ
Probing devices to guess BIOS drhdc: packet command error: status=0x51 { ives. T
his may tDriveReady Sake a long timeeekComplete Error }
hdc: packet command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
No suitable drive was found in the generated device map.
Reverting to backed up copy.
WARNING: Label / not found anywhere on the system! at /usr/lib/systemconfig/Boot
/Grub.pm line 207
WARNING: Label /boot not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /ipix not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /logs not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /tmp not found anywhere on the system! at /usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label /var not found anywhere on the system! at /usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label SWAP-sda2 not found anywhere on the system! at /usr/lib/systemcon
fig/Boot/Grub.pm line 207
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Error: None of the following bootloaders were successfully setup on your system:
YaBoot,Iseries,EFI,Elilo,Lilo,Grub,Palo,Aboot
Killing off running processes.
write_variables
On 5/27/07, Andrea Righi [EMAIL PROTECTED] wrote:
Tory M Blue wrote:
So I was working on this and trying various patches but had to deal
with some other projects. i've done a search and doesn't appear that
anyone else has reported or found a solution to the issue
History.. Image came from a SATA box, i'm installing said image on a
box with HDA (other then that similar hardware). The partition,
format , swap creationg etc.etc works fine. The image is rsyncd over
and is on the server, but when it trys to create the boot records etc
, it bombs with the following:
Special note, hdc (don't have such a device and never had, it's no
where in the configs. my fstab has only labels and the /etc/mntab file
shows /dev/hda1-8, so it's hda, but systemconfigurator has bad info
and not sure what that is .
I've even disabled my cdrom in bios, so that it should only pull up
the single master hd, which should be hda.. i'm unclear where
systemconfigurator is pulling hdc from
any ideas since I disappeared?
thanks
tory
OUTPUT
systemimager 3.7.x (can't find a 2.9 systemconfigurator rpm, so can't
try systemimager 3.9.x (as it appears it make have some updates to
solve my issue)
I suppose you mean systemconfigurator 2.2.9:
http://sourceforge.net/project/showfiles.php?group_id=24006package_id=17960release_id=503167
First test could be to just update systemconfigurator in your image, still
using
systemimager 3.7.x... hey, 3.7.x??! have you seen it? you're using an old
release! and even unstable!!! :-)
Second test (if the previous doesn't resolve) should be to update systemimager
systemconfigurator, re-create the autoinstall script (with
si_mkautoinstallscript) and try again...
BTW which version of grub do you have in your image?
-Andrea
Probing devices to guess BIOS drhdc: packet command error: status=0x51 {
ives. T
his may tDriveReady ake a long time.SeekComplete
Error }
hdc: packet command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
No suitable drive was found in the generated device map.
Reverting to backed up copy.
WARNING: Label / not found anywhere on the system! at
/usr/lib/systemconfig/Boot
/Grub.pm line 207
WARNING: Label /boot not found anywhere on the system! at
/usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /ipix not found anywhere on the system! at
/usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /logs not found anywhere on the system! at
/usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /tmp not found anywhere on the system! at
/usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label /var not found anywhere on the system!
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
I just had it install grub at the end instead of using systemimager.
I wrote a shell script which detected whether it was sd or hd and then just
manually re-installed grub.
Maybe you can do this yourself.
-Drew
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tory M Blue
Sent: Tuesday, May 29, 2007 4:55 PM
To: [EMAIL PROTECTED]; sisuite-users@lists.sourceforge.net
Subject: Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Same Failure. This appears to be 100% in systemconfigurator, since the
drive is partitioned, filesystems created and the image rsycnd, it
just fails to install the bootloader.
I've even tried to run the various systemconfigurator commands locally
with the same results..
Single master drive (IDE) and single secondary master (CDROM)
Version info:
systemconfigurator-2.2.9-1
systemimager-server-3.9.0-1
systemimager-client-3.9.0-1
systemimager-i386boot-standard-3.9.0-1
systemimager-common-3.9.0-1
systemimager-i386initrd_template-3.9.0-1
Grub Version in image:and server
grub (GNU GRUB 0.97)
ERROR:
sent 116 bytes received 66 bytes 364.00 bytes/sec
total size is 0 speedup is 0.00
Editing files for actual disk configuration...
/dev/sda - /dev/hda
/etc/fstab
/boot/grub/menu.lst
/etc/grub.conf
ÇÇÇ
Probing devices to guess BIOS drhdc: packet command error: status=0x51 { ives. T
his may tDriveReady Sake a long timeeekComplete Error }
hdc: packet command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
No suitable drive was found in the generated device map.
Reverting to backed up copy.
WARNING: Label / not found anywhere on the system! at /usr/lib/systemconfig/Boot
/Grub.pm line 207
WARNING: Label /boot not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /ipix not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /logs not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /tmp not found anywhere on the system! at /usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label /var not found anywhere on the system! at /usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label SWAP-sda2 not found anywhere on the system! at /usr/lib/systemcon
fig/Boot/Grub.pm line 207
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Error: None of the following bootloaders were successfully setup on your system:
YaBoot,Iseries,EFI,Elilo,Lilo,Grub,Palo,Aboot
Killing off running processes.
write_variables
On 5/27/07, Andrea Righi [EMAIL PROTECTED] wrote:
Tory M Blue wrote:
So I was working on this and trying various patches but had to deal
with some other projects. i've done a search and doesn't appear that
anyone else has reported or found a solution to the issue
History.. Image came from a SATA box, i'm installing said image on a
box with HDA (other then that similar hardware). The partition,
format , swap creationg etc.etc works fine. The image is rsyncd over
and is on the server, but when it trys to create the boot records etc
, it bombs with the following:
Special note, hdc (don't have such a device and never had, it's no
where in the configs. my fstab has only labels and the /etc/mntab file
shows /dev/hda1-8, so it's hda, but systemconfigurator has bad info
and not sure what that is .
I've even disabled my cdrom in bios, so that it should only pull up
the single master hd, which should be hda.. i'm unclear where
systemconfigurator is pulling hdc from
any ideas since I disappeared?
thanks
tory
OUTPUT
systemimager 3.7.x (can't find a 2.9 systemconfigurator rpm, so can't
try systemimager 3.9.x (as it appears it make have some updates to
solve my issue)
I suppose you mean systemconfigurator 2.2.9:
http://sourceforge.net/project/showfiles.php?group_id=24006package_id=17960release_id=503167
First test could be to just update systemconfigurator in your image, still
using
systemimager 3.7.x... hey, 3.7.x??! have you seen it? you're using an old
release! and even unstable!!! :-)
Second test (if the previous doesn't resolve) should be to update systemimager
systemconfigurator, re-create the autoinstall script (with
si_mkautoinstallscript) and try again...
BTW which version of grub do you have in your image?
-Andrea
Probing devices to guess BIOS drhdc: packet command error: status=0x51 {
ives. T
his may tDriveReady ake a long time.SeekComplete
Error }
hdc: packet command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
No suitable drive was found in the generated device map.
Reverting to backed up copy.
WARNING: Label / not found anywhere on the system! at
/usr/lib/systemconfig/Boot
/Grub.pm line 207
WARNING
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Well that makes sense since my image which is what is used when the chroot /a/ happens, does not have these devices, since again it started life as an sda equipped server. So using the /dev filesystem on the image will totally fail, I guess there is a step that is missing that creates the new /dev/hda* devices.? Looking at how to get passed this,,, Tory On 5/29/07, Tory M Blue [EMAIL PROTECTED] wrote: On 5/29/07, Drew Weaver [EMAIL PROTECTED] wrote: I just had it install grub at the end instead of using systemimager. I wrote a shell script which detected whether it was sd or hd and then just manually re-installed grub. Maybe you can do this yourself. -Drew thanks Drew interesting, I can see /dev/hda fine, however if I chroot (as done by systemconfigurator) , I can no longer see /dev/hda at all using /sbin/fdisk -l. So something in the chroot is causing systemconfigurator to not see the /dev/hda device.. /scripts/pre-install # /sbin/fdisk -l Disk /dev/hda: 40.0 GB, 40020664320 bytes 16 heads, 63 sectors/track, 77545 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device BootStart EndBlocks Id System /dev/hda1 * 1 500 251953 83 Linux Partition 1 does not end on cylinder boundary. /dev/hda2 5004469 200 83 Linux Partition 2 does not end on cylinder boundary. /dev/hda344696459 1002929+ 83 Linux Partition 3 does not end on cylinder boundary. /dev/hda46459 77545358277975 Extended Partition 4 does not end on cylinder boundary. /dev/hda56459 10427 199+ 83 Linux /dev/hda6 10427 12417 1002929+ 83 Linux /dev/hda7 12417 14409 1003905+ 83 Linux /dev/hda8 14409 7754531820960+ 83 Linux /scripts/pre-install # chroot /a/ sh: no job control in this shell sh-3.1# /sbin/fdisk -l sh-3.1# Shows nothing, knows nothing about /dev/hda! So somehow I need to path systemconfigurator so it doesn't need to do a chroot or? Thanks, got me to start thinking!! Tory - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Update: So I simply rsyncd the /dev/hd* files from a previous good HDA box and my image worked fine. So where exactly is systemimager/systemconfigurator suppose to create these new device files? It's not being done automatically, so I can't see anyone having success moving from a SDA image to HDA hardware, I don't see it! Tory On 5/29/07, Tory M Blue [EMAIL PROTECTED] wrote: Well that makes sense since my image which is what is used when the chroot /a/ happens, does not have these devices, since again it started life as an sda equipped server. So using the /dev filesystem on the image will totally fail, I guess there is a step that is missing that creates the new /dev/hda* devices.? Looking at how to get passed this,,, Tory On 5/29/07, Tory M Blue [EMAIL PROTECTED] wrote: On 5/29/07, Drew Weaver [EMAIL PROTECTED] wrote: I just had it install grub at the end instead of using systemimager. I wrote a shell script which detected whether it was sd or hd and then just manually re-installed grub. Maybe you can do this yourself. -Drew thanks Drew interesting, I can see /dev/hda fine, however if I chroot (as done by systemconfigurator) , I can no longer see /dev/hda at all using /sbin/fdisk -l. So something in the chroot is causing systemconfigurator to not see the /dev/hda device.. /scripts/pre-install # /sbin/fdisk -l Disk /dev/hda: 40.0 GB, 40020664320 bytes 16 heads, 63 sectors/track, 77545 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device BootStart EndBlocks Id System /dev/hda1 * 1 500 251953 83 Linux Partition 1 does not end on cylinder boundary. /dev/hda2 5004469 200 83 Linux Partition 2 does not end on cylinder boundary. /dev/hda344696459 1002929+ 83 Linux Partition 3 does not end on cylinder boundary. /dev/hda46459 77545358277975 Extended Partition 4 does not end on cylinder boundary. /dev/hda56459 10427 199+ 83 Linux /dev/hda6 10427 12417 1002929+ 83 Linux /dev/hda7 12417 14409 1003905+ 83 Linux /dev/hda8 14409 7754531820960+ 83 Linux /scripts/pre-install # chroot /a/ sh: no job control in this shell sh-3.1# /sbin/fdisk -l sh-3.1# Shows nothing, knows nothing about /dev/hda! So somehow I need to path systemconfigurator so it doesn't need to do a chroot or? Thanks, got me to start thinking!! Tory - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
You need to mount proc. -Drew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tory M Blue Sent: Tuesday, May 29, 2007 6:07 PM To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Back, have some time,. SDA to HDA imaging On 5/29/07, Drew Weaver [EMAIL PROTECTED] wrote: I just had it install grub at the end instead of using systemimager. I wrote a shell script which detected whether it was sd or hd and then just manually re-installed grub. Maybe you can do this yourself. -Drew thanks Drew interesting, I can see /dev/hda fine, however if I chroot (as done by systemconfigurator) , I can no longer see /dev/hda at all using /sbin/fdisk -l. So something in the chroot is causing systemconfigurator to not see the /dev/hda device.. /scripts/pre-install # /sbin/fdisk -l Disk /dev/hda: 40.0 GB, 40020664320 bytes 16 heads, 63 sectors/track, 77545 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device BootStart EndBlocks Id System /dev/hda1 * 1 500 251953 83 Linux Partition 1 does not end on cylinder boundary. /dev/hda2 5004469 200 83 Linux Partition 2 does not end on cylinder boundary. /dev/hda344696459 1002929+ 83 Linux Partition 3 does not end on cylinder boundary. /dev/hda46459 77545358277975 Extended Partition 4 does not end on cylinder boundary. /dev/hda56459 10427 199+ 83 Linux /dev/hda6 10427 12417 1002929+ 83 Linux /dev/hda7 12417 14409 1003905+ 83 Linux /dev/hda8 14409 7754531820960+ 83 Linux /scripts/pre-install # chroot /a/ sh: no job control in this shell sh-3.1# /sbin/fdisk -l sh-3.1# Shows nothing, knows nothing about /dev/hda! So somehow I need to path systemconfigurator so it doesn't need to do a chroot or? Thanks, got me to start thinking!! Tory - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Hi I had the same hda/sda trouble. It was an ide-scsi module, which I had to add to a pre-UYOK SI kernel, but that is another story. SI didn't think my master script needed to mount /dev /a/dev/ -o bind but in fact it was needed for chroot /a/ systemconfiguraror so that the part doing grub-install can see the hard drive devices. Worse, I had to, after this mount, before chroot /a/ systemconfigurator, ln -s /dev/hda1 /dev/sda1 and it actually worked. Inelegant, obscure, and took to long to find. The installer sees hda, the images sees sda. ide-scsi yuckness. Of course, yesterday Ubuntu Feisty 7.04 upgraded the kernel package linux-image-2.6.20-16-generic, (from -15) and now, still via ide-scsi, the Dell Optiplexes now again show hda and not sda, like older kernels, like the installer, but not like Feisty since release up to now :-P Why the sudden reversal? /Me has not ventured to lkml or feisty changelogs... OK, had a look now at the Feisty changelogs for that kernel, and it is a mostly networking related security upgrade, with no mention of ide-scsi. Irunno... OK, so the stupid ln -s is no longer necessary, but the dev bind-mount is still necessary, somehow mkautoinstallscript thinks I don't need it for this image. The fstab file also had to be changed in the master script to be sda, and now back to hda. UUIDs didn't seem to work despite the labels being set in the master script during partitioning. However grub booted a root partition by label. Perhaps this is also solved now. To debug all this read the master script, shellout at the appropriate place, and test some things in the installer environment and in the chroot. I run stock Ubuntu Dapper 6.06.1 LTS servers, and teach people to use these, and it is desireable to start off with the versions of software already packaged for this. It means SI 3.2.3, fairly old. Aside: For the ide-scsi kernel module I just downloaded the 3.8 source, recompiled just for the client boot kernel with one extra module, and took the kernel and initrd out and put it in /var/lib/tfptboot where it was needed, in a 3.2.3 systemimager-server installation. Even in Ubuntu Feisty 7.04 the packaged version of SI is 3.2.3, there seems to be not a lot of movement to UYOK and later upstream versions? SI bo! cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Back, have some time,. SDA to HDA imaging
Thanks for the various responses. My SATA/SDA image has ZERO hda* devices, so it mounts up the right dir /dev/ but only see's /dev/hdc, which is not in this system. Are you saying there is another directory other then /dev that would have the devices? In FC*? I don't see it, seems that this directory is completely empty in my image and appears to be created on boot. My issue is purely that I had no hda* devices listed in /dev of my image (because the image was not on a IDE system and thus used megaraid-sas to create the /dev/sda devices. It's working now, by solely, rsync'in the /dev/hda* files from a ide image, that was the only change. So I'm having a hard time with the other suggestions (not saying they are bad, just not seeing them fit my scenario).. Thanks Tory On 5/29/07, Jan Groenewald [EMAIL PROTECTED] wrote: Hi I had the same hda/sda trouble. It was an ide-scsi module, which I had to add to a pre-UYOK SI kernel, but that is another story. SI didn't think my master script needed to mount /dev /a/dev/ -o bind but in fact it was needed for chroot /a/ systemconfiguraror so that the part doing grub-install can see the hard drive devices. Worse, I had to, after this mount, before chroot /a/ systemconfigurator, ln -s /dev/hda1 /dev/sda1 and it actually worked. Inelegant, obscure, and took to long to find. The installer sees hda, the images sees sda. ide-scsi yuckness. Of course, yesterday Ubuntu Feisty 7.04 upgraded the kernel package linux-image-2.6.20-16-generic, (from -15) and now, still via ide-scsi, the Dell Optiplexes now again show hda and not sda, like older kernels, like the installer, but not like Feisty since release up to now :-P Why the sudden reversal? /Me has not ventured to lkml or feisty changelogs... OK, had a look now at the Feisty changelogs for that kernel, and it is a mostly networking related security upgrade, with no mention of ide-scsi. Irunno... OK, so the stupid ln -s is no longer necessary, but the dev bind-mount is still necessary, somehow mkautoinstallscript thinks I don't need it for this image. The fstab file also had to be changed in the master script to be sda, and now back to hda. UUIDs didn't seem to work despite the labels being set in the master script during partitioning. However grub booted a root partition by label. Perhaps this is also solved now. To debug all this read the master script, shellout at the appropriate place, and test some things in the installer environment and in the chroot. I run stock Ubuntu Dapper 6.06.1 LTS servers, and teach people to use these, and it is desireable to start off with the versions of software already packaged for this. It means SI 3.2.3, fairly old. Aside: For the ide-scsi kernel module I just downloaded the 3.8 source, recompiled just for the client boot kernel with one extra module, and took the kernel and initrd out and put it in /var/lib/tfptboot where it was needed, in a 3.2.3 systemimager-server installation. Even in Ubuntu Feisty 7.04 the packaged version of SI is 3.2.3, there seems to be not a lot of movement to UYOK and later upstream versions? SI bo! cheers, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] Back, have some time,. SDA to HDA imaging
So I was working on this and trying various patches but had to deal
with some other projects. i've done a search and doesn't appear that
anyone else has reported or found a solution to the issue
History.. Image came from a SATA box, i'm installing said image on a
box with HDA (other then that similar hardware). The partition,
format , swap creationg etc.etc works fine. The image is rsyncd over
and is on the server, but when it trys to create the boot records etc
, it bombs with the following:
Special note, hdc (don't have such a device and never had, it's no
where in the configs. my fstab has only labels and the /etc/mntab file
shows /dev/hda1-8, so it's hda, but systemconfigurator has bad info
and not sure what that is .
I've even disabled my cdrom in bios, so that it should only pull up
the single master hd, which should be hda.. i'm unclear where
systemconfigurator is pulling hdc from
any ideas since I disappeared?
thanks
tory
OUTPUT
systemimager 3.7.x (can't find a 2.9 systemconfigurator rpm, so can't
try systemimager 3.9.x (as it appears it make have some updates to
solve my issue)
Probing devices to guess BIOS drhdc: packet command error: status=0x51 { ives. T
his may tDriveReady ake a long time.SeekComplete
Error }
hdc: packet command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
No suitable drive was found in the generated device map.
Reverting to backed up copy.
WARNING: Label / not found anywhere on the system! at /usr/lib/systemconfig/Boot
/Grub.pm line 207
WARNING: Label /boot not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /ipix not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /logs not found anywhere on the system! at /usr/lib/systemconfig/
Boot/Grub.pm line 207
WARNING: Label /tmp not found anywhere on the system! at /usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label /var not found anywhere on the system! at /usr/lib/systemconfig/B
oot/Grub.pm line 207
WARNING: Label SWAP-hda2 not found anywhere on the system! at /usr/lib/systemcon
fig/Boot/Grub.pm line 207
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Couldn't find grub root at /usr/lib/systemconfig/Boot.pm line 110
Error: None of the following bootloaders were successfully setup on your system:
YaBoot,Iseries,EFI,Elilo,Lilo,Grub,Palo,Aboot
sh-3.1#
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
