hello, after reading the interesting and promising systemimager howto (http://www.falkotimme.com/howtos/systemimager/index.php) we decided to give it a chance so, we download the package (we got SystemImager autoinstall v3.2.3) and installed - systemimager-i386boot-standard (server) - systemimager-i386initrd_template (golden-client) and to deploy the image, we made the floppy disk install (SYSLINUX 2.100 2004-06-18) via dd and copying local.cfg to it the image creation process in the gold-client was successful but... when we want to recreate in another machine we have errors.. allegedly because we have no hda!! problem shown in http://www.howtoforge.com/forums/showthread.php?t=6456 is very similar to our problem... but dont get the solution a extract of the info we get in the station 8<------------------------------------------------------------- ide : Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hda : ST380011A, ATA Disk drive ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14 Partition check: hda:end_request: I/O error, dev 03:00 (hda), sector 0 end_request: I/O error, dev 03:00 (hda), sector 2 end_request: I/O error, dev 03:00 (hda), sector 4 end_request: I/O error, dev 03:00 (hda), sector 6 end_request: I/O error, dev 03:00 (hda), sector 0 end_request: I/O error, dev 03:00 (hda), sector 2 end_request: I/O error, dev 03:00 (hda), sector 4 end_request: I/O error, dev 03:00 (hda), sector 6 unable to read partition table .... .... I will now run the autoinstall script: /scripts/mi_imagen.master get_arch DISKORDER=sd,cciss,ida,rd,hd Logmsg: no such file or directory logmsg: No such file or directory logmsg: No such file or directory logmsg: No such file or directory logmsg: No such file or directory Error: Could not stat device /dev/hda/ - No such file or directory. logmsg: No such file or directory Error: Could not stat device /dev/hda/ - No such file or directory. Killing off all running processes. killall: udp-receiver: no process killed 8<------------------------------------------------------------- any clues? thankyou in advanced btw, bios disk is in auto mode, and the disk only have one ext2 partition
If you use hda in the image, the client must also use hda, not hdb, sda, or anything else. If you don't use hda on the client, you could change the master script on the image server (I think it's in /var/lib/systemimager/scripts).
falko, we have 'hda' in both machines in the sisuite-users list, Andrea Righi has suggested us that the version we have been used (3.2.3) is too old... and we must upgrade it to (at least) 3.6.3 i dont understand why we got 3.2.3 and not the latest!!... because we follow the steps in http://www.systemimager.org/download for fedora/rpm users maybe the error came from the creation of the boot diskette... we download the image from your howto page anyway, of course we'll (try to) upgrade it thanks for your interest