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 Boot Start End Blocks Id System > > /dev/hda1 * 1 500 251953 83 Linux > > Partition 1 does not end on cylinder boundary. > > /dev/hda2 500 4469 2000000 83 Linux > > Partition 2 does not end on cylinder boundary. > > /dev/hda3 4469 6459 1002929+ 83 Linux > > Partition 3 does not end on cylinder boundary. > > /dev/hda4 6459 77545 35827797 5 Extended > > Partition 4 does not end on cylinder boundary. > > /dev/hda5 6459 10427 1999999+ 83 Linux > > /dev/hda6 10427 12417 1002929+ 83 Linux > > /dev/hda7 12417 14409 1003905+ 83 Linux > > /dev/hda8 14409 77545 31820960+ 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! > > > > Sooooo 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 [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
