HD Install :: HD install from USB Stickand unzippeddsl
Hello,
I try to make a HD install from a USB Stick.
I have an IBM Thinkpad 570e with an Usebase where is a floppy in,
but no cdrom. It could not boot from USB.
So I made the bootfloppy USB, and unzipped the dsl embedded 1.1.zip to my USB Stick (In real it's an SD Card in a Reader/Writer but I think thats not the Problem).
I put the disk in the floppy Drive and put the USB Stick in the port and started the Laptop.
A few Minutes Later I Have the DSL Desktop. So far so good.
The Usebase is not mine and I have to give it back this Week, so I like to make a HD Install. DSL Can have the whole HD I don't need another System on it.
So I do: sudo -u root dsl-hdinstall in Xterm.
Target hda1 (It ' s bootable & Free)
Standard Install
Multi-User
ext3
The laptop is writing on HD.
I got the message:
The copying of the file syszem has completed
Setting up /root/
Setting up /home/dsl/
tar: Removing leadin '/ ' from member names
mount:special device /dev/cdrom does not exist
cp: cannot stat '/mount/booting/boot/isolinux/linux24': No such file or directory
umount: /mount/booting : Not mounted
The installation process is finished
:
Do you want to run mkliloboot now? y
/dev/root on / type ext2 (rw)
/dev/sda1 on cdrom type vfat (rw)
/dev/cloop on /Knoppix type iso9660 (ro)
/ramdisk on /ramdisk type tmpfs (rw,size=149996k)
/dev/hda1 on /mnt/hd type ext2 (rw)
mount:special device /dev/cdrom does not exist
gzip: /mnt/l1/boot/isolinux/minirt24.gz : No such file or directory
umount: /mnt/l1 : not mounted
mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems
umount: /mnt/l1/: not mounted
Setting up boot loader lilo in mbr
part: /dev/sda1, type4
Warning 'proc partitions'does not exist, disk scan bypassed
Fatal: open boot linux24 : No such file or directory
The lilo boot installation process has finished
Ok , when I try to boot from HD I Got the message
Error while loding the OS
Anyone an idea??
Thank you for help!!
The hard drive install script was made to run from a liveCD.
This script was made before pendrives were out.
The directory structure is different between cdrom and pendrive.
The cdrom has a directory boot/isolinux/... whereas the pendrive the boot up files, e.g. linux24, etc., are in the / directory.
You might want to try to either modify the script or copy over the boot/isolinux directory from the cdrom to the pendrive and try the script again.
First of all,
Thank you for wasting time with my problems 
I found the script in : /usr/sbin/dsl-hdinstall startet beaver as su opend it, and can not edit it because beaver opend it as read only. The whole truth is, if I could edit I don't know what. Change the cdrom at the end of the script in sda1??
How ever:
I loaded down a new DSL CD iso, and made it on CD, found there the /boot/isolinux directory and copied it to the / on my pendrive.
Startet DSL again.
Again sudo dsl-hdinstall
It works so far then:
Mkliloboot
y
/dev/root on / type ext2 (rw)
/dev/sda1 on cdrom type vfat (rw)
/dev/cloop on /Knoppix type iso9660 (ro)
/ramdisk on /ramdisk type tmpfs (rw,size=149996k)
/dev/hda1 on /mnt/hd type ext2 (rw)
Setting up boot loader lilo in mbr
part/dev/sda, typ 4
Warning: 'proc partitions'does not exist, disk scan bypassed
Added Linux*
Skipping /vmlinuz.old
Device= 0x800: Inconsistence partition table, 1st entry
CHS Adress in PT: 0:1:1 --> LBA(62)
LBA Adress in PT: 225 --> CHS(0:3:40)
Fatal: Either FIX-TABLE or IGNORE-TABLE must be specified
If not sure , first try IGNORE-TABLE (-P ignore)
The lilo boot installation process has finished
I don't realy understand but I thought there where a problem in the mbr.
so I tried to overwrite him with:
dd if=/dev/zero of=/dev/hda bs=512 count=1
try it again, but it helped not.
Then I tried to boot with freedos and fdisk /mbr, but there came an error:
Invalid drive designation.... Operation terminated.
Started DSL again but the same problem.
Hmm anyone any idea??
Thank very much for helping me!!!!
Hi it's me again,
I think the problem could be a hardware defect.
I let run badblocks -w /dev/hd...
It seems to work a while
Let's see what happend......
original here.