It is currently Mon Sep 01, 2014 5:42 am

All times are UTC - 8 hours




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 10 posts ] 
Author Message
 Post subject: Boot Trinity Rescue Kit from UBCD
PostPosted: Tue Oct 21, 2008 1:39 am 
Offline

Joined: Mon Oct 20, 2008 4:56 am
Posts: 8
Location: Amersfoort, NLD
Hi everybody, another question from a new and enthousiastic UBCD user :)

I loaded UBCD onto a memory stick and wanted to add the Trinity Rescue Disc of which I'm also a fervent user. I opened the ISO in UltraISO and saved it as IMG, then GZipped it using PeaZip and renamed it to trk.igz. I then added it to bootdsk2.cfg like so:

LABEL trk
MENU LABEL Trinity Rescue Kit V3.2
KERNEL memdisk
APPEND initrd=/images/trk.igz

When loading it from UBCD, it will extract the image, so far so good, but then hangs while booting...

What I found strange is that UltraISO didn't only save a trk.img file but also a trk.ccd file and a trk.sub file. In my ignorance I must be doing it wrong... Could anybody point me to a clue?


Top
 Profile  
 
 Post subject:
PostPosted: Tue Oct 21, 2008 4:58 am 
Offline

Joined: Fri Jan 11, 2008 2:52 pm
Posts: 1278
Albantar wrote:
I loaded UBCD onto a memory stick and wanted to add the Trinity Rescue Disc of which I'm also a fervent user. I opened the ISO in UltraISO and saved it as IMG, then GZipped it using PeaZip and renamed it to trk.igz. I then added it to bootdsk2.cfg like so:

This method doesn't work for most linux based iso's. This works only if it needs a kernel and an initrd, without any other other files.

I wrote a tutorial for you (Trinity Rescue Kit V3.3). I don't think that it will differ much from the v3.2 (I don't think so).
http://www.ultimatebootcd.com/forums/viewtopic.php?p=6004#6004


Top
 Profile  
 
 Post subject:
PostPosted: Wed Oct 22, 2008 1:06 am 
Offline

Joined: Mon Oct 20, 2008 4:56 am
Posts: 8
Location: Amersfoort, NLD
First of all, thank you very much for that tutorial, it is very clear.

However (there's always a catch, isn't there?) when I did all that and then tried to boot from my boot stick, all I got was the blue menu screen (though smaller than usual, taking up about half the screen) with half a line of ASCII hieroglyphs, and a red text "Press [Tab] to edit options" at the bottom, and it hangs.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Oct 22, 2008 3:23 am 
Offline

Joined: Fri Jan 11, 2008 2:52 pm
Posts: 1278
You have to rerun the ubcd2usb script.

You also can run syslinux.exe instead:
    Go to Start ==> Run as... ==> cmd.exe
    Drag and drop syslinux.exe from c:\syslinux\win32\ to the cmd window
    Complete the command with the following (change x: with the drive letter of your usb stick, be careful!) :

Code:
syslinux -ma -d syslinux x:


Top
 Profile  
 
 Post subject:
PostPosted: Wed Oct 22, 2008 5:16 am 
Offline

Joined: Mon Oct 20, 2008 4:56 am
Posts: 8
Location: Amersfoort, NLD
Ah yes, that does the trick. The bottom of the menu is missing but that's just aesthetic.

Thank you so much for your helpfulness.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Oct 22, 2008 7:13 am 
Offline

Joined: Mon Oct 20, 2008 4:56 am
Posts: 8
Location: Amersfoort, NLD
An important note to other people who would like to run TRK from UBCD: it doesn't work with TRK 3.2...

It will start to boot but then it can't locate the RAM disk image on the USB drive and fail.

So I downloaded TRK 3.3 beta and gave that a shot. The same thing seemed to happen, but instead of failing after not having found the RAM disk image, it asked to enter manually on which device TRK can be found. I entered sda1 and off it went.

I believe this issue is already known to the TRK crew and is common to all people who want to boot TRK from a USB stick, but I'll just double-check and submit a bug report if necessary.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Oct 23, 2008 4:09 am 
Offline

Joined: Mon Oct 20, 2008 4:56 am
Posts: 8
Location: Amersfoort, NLD
Another note to people who would like to use TRK from UBCD:

the problem described by me is indeed known. For TRK3.2 the solution is to rename your USB stick to TRK_3-2.

For TRK3.3 you can either rename it to TRK_3-3, or use a new feature available in TRK3.3: add the option vollabel=YOURLABEL to all the boot options lines in TRK's isolinux.cfg

http://trinityhome.org/Home/index.php?w ... ront_id=12


Top
 Profile  
 
 Post subject:
PostPosted: Thu Oct 23, 2008 8:16 am 
Offline

Joined: Fri Jan 11, 2008 2:52 pm
Posts: 1278
I have updated my tutorial. I was to lazy to test it myself :wink: .


Top
 Profile  
 
 Post subject:
PostPosted: Thu Oct 23, 2008 9:49 pm 
Offline

Joined: Mon Oct 20, 2008 4:56 am
Posts: 8
Location: Amersfoort, NLD
Icecube wrote:
I have updated my tutorial. I was to lazy to test it myself :wink: .


I see you didn't test it, because it won't work like that ;)

The vollabel option needs to be in the "append" line.

:1,$s/initrd=/vollabel=UBCD410 initrd=/

;)


Top
 Profile  
 
 Post subject:
PostPosted: Fri Oct 24, 2008 7:04 am 
Offline

Joined: Fri Jan 11, 2008 2:52 pm
Posts: 1278
It was on the same line when I made it. but the forum software did mess up the output. I have added that to the tutorial, that it has to be on the same line.

Thanks for reporting.
Quote:
:1,$s/initrd=/vollabel=UBCD410 initrd=/

I don't get this. What do you mean with it?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 10 posts ] 

All times are UTC - 8 hours


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group