Page 1 of 1

Bugs with USB install

Posted: 01 Aug 2011, 19:29
by beejaye
srcd Install to USB bug report
Quick summary: Option A does not work as described. Software saw flash as sdd and created non-existent sdd0 whereas it is sdd1 that exists. Option A abandoned. Option E adjusted for Puppy peculiarities installed rescuecd, but boot flag was missing; I got boot errors of missing linux and "UI" in syslinux.cfg; and error when gparted launched.

======================================================
Unable to either import screenshots in the text below or attach an archive detailing the ordeal.
If someone is interested, email me and I'll send it.
======================================================

Woes putting SRCD on USB Key
I run Puppy linux. Don't snort, please.
Kernel is 2.6.33.2
RAM=3GB
Objective: Put srcd on USB key
Target Flash drive for rescuecd: 4 GB PQI
Quick summary: Option A does not work as described. Software saw flash as sdd and created non-existent sdd0 whereas it is sdd1 that exists. Option A abandoned. Option E adjusted for Puppy peculiarities installed rescuecd, but boot flag was missing; I got boot errors of missing linux and "UI" in syslinux.cfg; and error when gparted launched.


As malware has affected my Windows box

1. I boot Puppy Linux from a flash drive (I am not using Windows until malware infection fixed, hence my interest in SRCD). The device name of the booted flash drive is sdc1 and the host device names are sda1 and sda2 (RECOVERY).
2. I don't have a working CD/DVD (malware inflicted). Therefore I had to opt to put systemrescue CD on a 4GB flash drive. When the empty flash drive is inserted after booting, it is assigned sdd1. I don't know what it would be assigned when the puppy flash drive is removed and it becomes the boot drive (likely sdc1).

I read the manual and chose option A, the recommended USB installation method from Linux. I followed the instructions faithfully. When I executed the installer I thought nothing of the device being named /dev/sdd as shown in the screenshot below, although cfisk and the desktop icon both show it as sdd1 (see bottom of screenshot).

[img]file:///mnt/hp100w/4Forum&Mail/the%20pieces/devname_not_sdd1.png[/img]

I clicked OK and got the graphic below:
[img]file:///mnt/hp100w/4Forum&Mail/the%20pieces/srcd_feedback.png[/img]

Note that the file system being created is /dev/sdd0. But I didn't see it and waited and waited for the program to give me some feedback, Was it aborted? Where are we in the progress? Nothing! I gave up waiting after an hour, checked the log and saw.

/dev/sdd0 is not a valid partition.

After unmounting, the flash drive could not be mounted. In Puppy, I used fdisk and Gparted to partition the drive in 2, a 2 GB and the rest. I was able to restore the 2 GB partition.

Obviously there was a programming problem, so no use in retrying that procedure without a program change and that was beyond me.

Despite the warning that method E Manual installation from Linux using cp is a bit complicated, I decided to try it. It really wasn't although
I had to make the following adjustments:
in puppy, mbr.bin was located in /usr/lib/syslinux/ not /usr/share/syslinux/ [Step 2]
changed the command to access the files from the iso instead of the CD by mounting the iso and noting the directory. [Step 3]
cp -af /mnt/+mnt+sda1+systemrescuecd-x86-2.2.0.iso /mnt/usbstick

All went well, but when I booted I got a flashing underscore. In puppy/GParted, on checking the boot flag I discovered that it had not been set. Unless I don't understand, cfdisk told me the drive was bootable and the command in Step 4 should have made it bootable. Ah well ...So, I fixed that and rebooted. I got an error messages:
Unknown keyword in configuration file: UI
Could not find kernel image: linux
then the boot: prompt
At the boot: prompt I pressed the Enter key and got another message and turned off the computer.

Rebooted puppy and looked at syslinux.cfg and found 'UI' on the very first line.


What should I do now?
rebooted. I got the same error messages then the boot prompt again. Remembering from the docs that rescuecd was a boot command, I entered rescuecd and all's well except that selecting gparted from the menu generates an error.

Thought this was going to be easy but it wasn't.

Re: Bugs with USB install

Posted: 01 Aug 2011, 23:05
by falk
* Creating filesystem on /dev/sdc0...
You are not alone with this problem.
I am not alone with this problem.
Thanks. 8-)

I made many tests with the script and found the realy problem.
look at http://www.sysresccd.org/forums/viewtop ... =13&t=4191
I hope it help.
[img]file:///mnt/hp100w/4Forum&Mail/the%20pieces/devname_not_sdd1.png[/img]
where are the Login-Data from your Server - i can mount your harddisk over sshfs? :-P

cu, Falk