Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am the person who wrote LifeBoat. I have not tested it on a USB CD writer because I do not own one. You are the first person that I know of who has tried to use LifeBoat to burn a USB CD. So I guess you are my guinea penguin on USB CD writers.
From what I read there I would say that CDR_DEVICE="0,0,0" should work just like it does for an IDE CD writer. If your CD writer is the first (or only) scsi device on your system then its device number is 0,0,0. If it is the second scsi device then its number is 1,0,0 and so on.
If you set the CDR_DEVICE parameter incorrectly then LifeBoat will not burn a LifeBoat CD.
I can only guess about IDESCI=. The purpose of this parameter is to tell the kernel to use the scsi modules for a device that is configured as IDE. If your USB CD writer is configured as a native scsi device then you do not need IDESCI and you should set it to null: IDESCSI= If your USB writer is configured as native IDE then you need an IDESCI parameter to tell LifeBoat which IDE device is being run as a scsi device.
The IDESCSI parameter is needed by the LifeBoat kernel at boot. If you set it incorrectly the only problem that will happen is that the LifeBoat rescue CD will not be able to write CDs, something that people rarely do in rescue mode anyway.
Also if you need the IDESCSI parameter then you also need it for your desktop kernel. You should have the parameter in your bootloader, either grub or lilo.
If you don't get LifeBoat to burn a CD on the first try or two then I suggest that you first learn to burn an ordinary ISO9660 data CD, then tell me how to do that on an USB CD writer and I could probably tell you how to make it work in LifeBoat.
In any case I would like you to let me know how things work out in detail so that I can do whatever is necessary to make LifeBoat work on USB CD.
Steve,
I post the same question on another forum since here was no
answers and I received one:
Re:LifeBoat config
« Reply #1 on: October 14, 2003, 07:52:59 PM » Reply with quote
--------------------------------------------------------------------------------
for me, I have an USB 2.0 CD-RW that just works out of the box. I plug it in, and X CD Roast just sees it.
I did that. May the output will tell you something.
login as: root
root@xxxxx's password:
Last login: Tue Oct 14 22:12:26 2003 from 10.0.0.10
[root@RH9 root]# cdrecord --scanbus
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI dr
iver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Looks like it will not work for me.
But I will try tomorrow at work and will let you know...
Hello Steve,
sorry,
yesterday my colegue took this removable writer and after didn't plugin the power.
Yesterday I run scanbus through ssh to my office RH....
)
I will try to create LifeBoat now.
Looks like everythinf is fine.
This is today's result:
Steve,
I created cd. When I boot computer hangs on line:
RAMDISK: Compressed image found at block 0.
What is wrong?
Here is out of disk creation:
[root@RH9 LifeBoat-0.2]# ./lifeboat
begin config processing
CDR_DEVICE=0,0,0
CDR_SPEED=
DISTRO=generic
IDESCSI=hdb=ide-scsi
KERNEL=/boot/vmlinuz
MANPAGES=yes
MYNAME=STITES
RAMDISK_SIZE=250
end config processing
250+0 records in
250+0 records out
mke2fs 1.32 (09-Nov-2002)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
64000 inodes, 256000 blocks
12800 blocks (5.00%) reserved for the super user
First data block=1
32 block groups
8192 blocks per group, 8192 fragments per group
2000 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
begin generic processing
cp: cannot stat `/bin/eject': No such file or directory
cp: cannot stat `/bin/guessfstype': No such file or directory
cp: cannot stat `/sbin/cfdisk': No such file or directory
cp: cannot stat `/sbin/killproc': No such file or directory
cp: cannot stat `/sbin/pidofproc': No such file or directory
cp: cannot stat `/sbin/start_daemon': No such file or directory
cp: cannot stat `/usr/bin/basename': No such file or directory
cp: cannot stat `/usr/bin/chroot': No such file or directory
cp: cannot stat `/usr/bin/grep': No such file or directory
cp: cannot stat `/usr/bin/loadkeys': No such file or directory
cp: cannot stat `/usr/bin/nice': No such file or directory
cp: cannot stat `/usr/bin/sed': No such file or directory
cp: cannot stat `/usr/bin/zcat': No such file or directory
cp: cannot stat `/usr/lib/awk/*': No such file or directory
cp: cannot stat `/usr/sbin/parted': No such file or directory
cp: cannot stat `/usr/share/kbd/keymaps/i386/include/*': No such file or directory
cp: cannot stat `/usr/share/kbd/keymaps/i386/qwerty/*': No such file or directory
cp: cannot stat `/usr/bin/catman': No such file or directory
cp: cannot stat `/usr/bin/mandb': No such file or directory
cp: cannot stat `/usr/lib/man-db/*': No such file or directory
cp: cannot stat `/usr/sbin/accessdb': No such file or directory
cp: cannot stat `/var/adm/fillup-templates/sysconfig.cron-man': No such file or directory
cp: cannot stat `/var/cache/man/index.db': No such file or directory
end generic processing
begin addons processing
end addons processing
89M .of ramdisk used out of 250M allocated.
Size of boot image is 4 sectors -> No emulation
25.20% done, estimate finish Wed Oct 15 10:53:12 2003
50.42% done, estimate finish Wed Oct 15 10:53:10 2003
75.56% done, estimate finish Wed Oct 15 10:53:10 2003
Total translation table size: 2048
Total rockridge attributes bytes: 752
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 4000
19856 extents written (38 Mb)
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
Using libscg version 'schily-0.7'
Device type : Removable CD-ROM
Version : 2
Response Format: 1
Vendor_info : 'HP '
Identifikation : 'CD-Writer+ 8200 '
Revision : '1.0f'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
starting to burn STITES LIFEBOAT SYSTEM
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
Device type : Removable CD-ROM
Version : 2
Response Format: 1
Vendor_info : 'HP '
Identifikation : 'CD-Writer+ 8200 '
Revision : '1.0f'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R
Starting to write CD/DVD at speed 4 in real TAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Track 01: Total bytes read/written: 40665088/40665088 (19856 sectors).
STITES LIFEBOAT SYSTEM has been successfully created
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.