Jump to content

Episode 5x24


Darren Kitchen

Recommended Posts

  • Replies 447
  • Created
  • Last Reply

Top Posters In This Topic

Well I've been trying to get GRUB installed on several usb disks and simply can't seem to get it working.

I have followed the instructions perfectly but all that happens is a flashing '_' in the top corner... so I am now looking at using GRUB 2 (1.96)

So shout out who's got GRUB 2 working on a USB Flash key, if you have could you please explain/show what you did ?? Bumperz ???

I've tried to create a GRUB 2 MBR from Ubuntu 9.10 already running the GRUB2 loader but it won't allow the creation of a MBR other than on a HD like HD0.

So any help appreciated.

I wonder if it is possible to rip the MBR from my Ubuntu 9.10 box and then write to the USB stick...

I did it using grub-install and grub-setup

Link to comment
Share on other sites

Does Kon-Boot work if you burn it to a CD or Floppy?

Yes, it does. At first I thought I might have a bad download or something, but I've downloaded it multiple times on different computers, burned each to a disk, and they all work. It works on Ubuntu, 7, or Vista, but won't if it's on the USB drive.

Link to comment
Share on other sites

Thanks for the replies guys, ok here goes

@Relium

Yes my computer can boot from USB as can another PC that I tried it on, but not the GRUB created USB.

@M0u53

Yup I was logged into my Ubuntu box as root.

@Psychosis

Could you show me the exact syntax you used to install both grub-install and grub setup, thanks.

I am wondering about the USB keys I am using... I have as a pack of 2 gig DANE Elec keys and I've tried each of them one by one and failing. I am waiting for my 2 new Cruzer U3's to turn up, so will see if they work with the 'straight forward install'

Link to comment
Share on other sites

I am wondering about the USB keys I am using... I have as a pack of 2 gig DANE Elec keys and I've tried each of them one by one and failing. I am waiting for my 2 new Cruzer U3's to turn up, so will see if they work with the 'straight forward install'

From the PEtoUSB ReadMe.txt

USB STICKS TESTED

=================

SanDisk Cruzer Mini SUCCESSFUL

PenDrive 2.0 Mini SUCCESSFUL

PQI iStick 2.0 SUCCESSFUL

I-Bead MP3 Player FAILED (I think the UFD initializes too slow for the BIOS)

Link to comment
Share on other sites

I am wondering about the USB keys I am using... I have as a pack of 2 gig DANE Elec keys and I've tried each of them one by one and failing. I am waiting for my 2 new Cruzer U3's to turn up, so will see if they work with the 'straight forward install'

I've got loads of that brand of drive and they work fine.

Try using the HP USB formatting tool, then use grubinst_gui to install a bootable MBR (make sure to pick the right drive) and then replace grldr with the one from grum4dos.

That really should be all there is to it.

Link to comment
Share on other sites

Anyone got BT4 Pre-Final to load from the ISO? I'm using:

title << Back | Track 4 (Pre-Final)
find --set-root /boot/iso/bt4-pre-final.iso
map /boot/iso/bt4-pre-final.iso (0xff)
map --hook
root (0xff)
kernel /boot/vmlinuz BOOT=casper boot=casper find_iso/filename=/boot/iso/bt4-pre-final.iso nopersistent rw quiet vga=0x317
initrd /boot/initrd.gz
boot

but it drops to the ASH shell at (initramfs)

Link to comment
Share on other sites

Anyone still struggling with BartPE? Easiest way to get that working is:-

1) Build your PE environment as usual

2) Use PeToUSB on a spare USB stick (3.0.0.8 works better on bigger USB sticks) - Enable Disk format, Quick format, Force Volume Dismount. Point the Source path to your BartPE folder (e.g C:\pebuilder3110a\BartPE) and tick "enable file copy". Then hit start.

3) Copy all files from your spare stick to your multiboot stick

4) You need to copy the file EMPTYREGDB.DAT to minint\SYSTEM32 on your multiboot stick. You can find this file in

C:\WINDOWS\system32 on a regular Windows XP installation.

5) add a menu.lst entry like this:-

# --- BartPE ---

title BartPE

root (hd0,0)

chainloader /minint/setupldr.bin

# --- --- --- ---

Having written this post, it now seems obvious that might be a long winded way of doing it, you might just be able to use PeToUSB without "Enable Disk Format" and "Don't rewrite MBR code" enabled to write the files directly to your multiboot stick.

Regardless, this method does not copy the ISO to RAM and so it's better if you often find yourself fixing older PC's with limited memory.

On another note, while digging around the internet for information on getting various apps to work, I found a thread which stated that for best compatibility with older motherboards, it was better to partition the stick. This fooled older, badly coded BIOS'es into thinking the stick was a hard drive and thus allowed booting from it. Obviously if your carrying your USB multiboot with you, you want it as compatible as possible. Anyone any thoughts on this, the information can be found here:- http://www.boot-land.net/forums/index.php?...mp;p=62682&

Link to comment
Share on other sites

Try using the HP USB formatting tool, then use grubinst_gui to install a bootable MBR (make sure to pick the right drive) and then replace grldr with the one from grum4dos.

I'll give it a go with the HP util and see if that works, otherwise I will have to wait till my new cruzers turn up in the morning and try them.

Link to comment
Share on other sites

Use the Acronis rescue media builder to make an ISO. Use grub ISO emulation like this:

title Acronis

map --mem /Acronis.iso (hd32)

map --hook

chainloader (hd32)

uptil now i havent been able to boot isos

i am using grub4dos 4.4 with fat16 and also tried using (fat32) - which one is better for multiboot??

i am able to BT4,HBCD,Konboot ,acronis hangs booting acronis media

i am not able to boot iso's

title Acronis

map --mem /Acronis.iso (hd32)

map --hook

chainloader (hd32)

title Acronis media

find --set-root /acronis10.iso

map /acronis10.iso (hd32)

map --hook

root (hd32)

chainloader (hd32)

title Super Grub Disk

map --mem (pd)/sgd.iso (hd32)

map --hook

chainloader (hd32)

Link to comment
Share on other sites

uptil now i havent been able to boot isos

i am using grub4dos 4.4 with fat16 and also tried using (fat32) - which one is better for multiboot??

i am able to BT4,HBCD,Konboot ,acronis hangs booting acronis media

i am not able to boot iso's

title Acronis
map --mem /Acronis.iso (hd32)
map --hook
chainloader (hd32)

title Acronis media
find --set-root /acronis10.iso
map /acronis10.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)


title Super Grub Disk
map --mem (pd)/sgd.iso  (hd32)
map  --hook
chainloader  (hd32)

they both work fine, but with fat32 you wont get "warnings" about the filesize..

about the acronis iso, it works here..

are you sure its on your drive on the root with exact the same filename?

i have this, and it works fine here

title Acronis
map --mem /acronis.iso (hd32)
map --hook
chainloader (hd32)

try with your Acronis media boot to select the kernel? otherwise i dont know.

play with the boot line's

Link to comment
Share on other sites

i like its (Acronis) deleted /corrupted partition recovery addon

I benchtested it (admittedly almost a year ago) against a couple of other packages, it was the only one that failed to sucessfully reimage a drive either from a boot CD or in Windows ! (if your interested you can read about it here http://www.top-windows-tutorials.com/TWT_N...iskBackup.html)

Their new version might be better, but once bitten twice shy for me.

Link to comment
Share on other sites

Trinity is working from it's own directories

1. create the trinity USB as shown in the show from the CD using the command line

2. copy all of the files on the trinity usb to /boot/trinity/ on your multipass usb drive - except /trk3 dir

3. copy the /trk3 directory from the trinity usb to root of the multipass usb

When it boots it will ask you to identify where your USB is located (usually /sdb1)

title Trinity Rescue Kit
kernel /boot/trinity/kernel.trk initrd=/boot/trinity/initrd.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose 
initrd /boot/trinity/initrd.trk

This isn't perfect because you still have to tell it where the usb drive is but it keeps the root directory clean.

Link to comment
Share on other sites

Just a thought...

Grub errors from the people who are having grub problems might be useful.

ie i keep getting "bad device string" errors trying to boot from isos.

EDIT: I switched from the standard grub 1 to grub4dos and the errors have ceased : )

<ignore this>

As per the above, I need some help understanding what I'm doing wrong with some of these entries

particularly the booting direct from isos.

</ignore this>

here is my menu.lst

color red/black white/black

title Smart Boot Manager (good)
kernel /memdisk
initrd /sbm.img floppy

title BT3 (good)
kernel /bt3_root/boot/vmlinuz vga=0x317 ramdisk_size=6666 root=/dev/ram0 rw quiet
initrd=/bt3_root/boot/initrd.gz
boot

title BT4 pre (good)
configfile /bt4-pre_root/boot/grub/menu.lst
savedefault

title Ophcrack (good)
kernel /ophcrack_root/boot/bzImage rw root=/dev/null vga=normal lang=C kmap=us screen=1024x768x16 autologin
initrd /ophcrack_root/boot/rootfs.gz

title Kon Boot (works with darren's method after switching to grub4dos)

title Hirens 9.9 (good)
kernel /memdisk
initrd /hirens_root/boot.gz

title ntpasswd (good)
kernel /memdisk
initrd /ntpasswd.img floppy

title DBAN (good)
kernel /memdisk
initrd /dban-floppy.img floppy

title Clonezilla (boots to error)
kernel /clonezilla_root/live/vmlinuz1 initrd=/clonezilla_root/live/initrd1.img boot=live union=aufs  hostname=jaunty edd=on nolocales noprompt ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" acpi=off irqpoll noapic noapm nodma nomce nolapic nosmp ip=frommedia vga=normal
initrd /clonezilla_root/live/initrd1.img

edit:
title Parted Magic(good after moving pmagic dir to root dir)
kernel /pmagic/bzImage noapic load_ramdisk=1 prompt_ramdisk=0 rw vga=791 sleep=10 loglevel=0 keymap=us
initrd /pmagic/initramfs

## old one that didn't work
#title Parted Magic(can't remember)
#kernel /pmagic_root/pmagic/bzImage noapic load_ramdisk=1 prompt_ramdisk=0 rw vga=791 sleep=10 #loglevel=0 keymap=us
#initrd /pmagic_root/pmagic/initramfs
#map --unmap=0:0xff (this line caused grub error: bad device)

title FreeDOS (good)
kernel /memdisk
initrd /freedos.img floppy

title Damn Small Linux (update: good after moving KNOPPIX dir to root dir)
kernel /dsl_root/boot/isolinux/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=789 initrd=minirt24.gz nomce noapic BOOT_IMAGE=dsl
initrd /dsl_root/boot/isolinux/minirt24.gz

title Super Grub Rescue Disk(boots but needs editing in submenus)
configfile /super-grub_root/grub/menu.lst
savedefault

title Trinity Rescue Kit (boots to error (I know there's abunch of stuff wrong with this one))
kernel /trinity_root/kernel.trk initrd=/trinity_root/initrd.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose
initrd /trinity_root/initrd.trk

title Ubuntu LiveCD(works after switching to grub4dos)
find --set-root /ubuntu-9.04-desktop-i386.iso
map /ubuntu-9.04-desktop-i386.iso (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/ubuntu-9.04-desktop-i386.iso quiet splash locale=en.UTF-8 --
initrd /casper/initrd.gz
boot

title Memory Test
kernel /memtest86+.bin (stolen from BT4pre)

title Boot the First Hard Disk
root (hd1)
chainloader +1

##END################
boot

here is my dir stucture

ROOTDIR of BOOTUSB
|-- BT3
|   |-- base
|   |-- livecd.sgn
|   |-- make_iso.bat
|   |-- make_iso.sh
|   |-- modules
|   `-- tools
|-- KNOPPIX(for dsl)
|   `-- KNOPPIX
edit:(no more boot folder switched to grub4dos don't got the grub-install route if you want to do the fun stuff)
|-- bt3_root
|   `-- boot
|       |-- bootinst.bat
|       |-- bootinst.sh
|       |-- bootlilo.sh
|       |-- chain.c32
|       |-- dos
|       |   |-- BT3.bat
|       |   |-- config
|       |   |-- loadlin.exe
|       |   `-- readme.txt
|       |-- initrd.gz
|       |-- isolinux
|       |   |-- isolinux.bin
|       |   |-- isolinux.boot
|       |   `-- isolinux.cfg
|       |-- msramdmp.c32
|       |-- mt86p
|       |-- syslinux
|       |   |-- ldlinux.sys
|       |   |-- lilo
|       |   |-- mbr.bin
|       |   |-- syslinux
|       |   |-- syslinux.cfg
|       |   |-- syslinux.com
|       |   `-- syslinux.exe
|       |-- vesamenu.c32
|       `-- vmlinuz
|-- bt4-pre_root
|   |-- boot
|   |   |-- bootsplash
|   |   |-- grub
|   |   |   |-- bt4.xpm.gz
|   |   |   |-- menu.lst
|   |   |   `-- stage2_eltorito
|   |   |-- initrd.gz
|   |   |-- initrd800.gz
|   |   |-- initrdfr.gz
|   |   |-- memtest86+.bin
|   |   `-- vmlinuz
|   |-- boot.catalog
|   `-- md5sum.txt
|-- casper (for bt4)
|   |-- filesystem.manifest
|   |-- filesystem.manifest-desktop
|   `-- filesystem.squashfs
|-- clonezilla_root
|   |-- COPYING
|   |-- Clonezilla-Live-Version
|   |-- home
|   |   `-- partimag
|   |-- live
|   |   |-- eb.zli
|   |   |-- filesystem.squashfs
|   |   |-- freedos.img
|   |   |-- gpxe.lkn
|   |   |-- initrd1.img
|   |   |-- memtest
|   |   |-- packages.txt
|   |   |-- parameters.txt
|   |   `-- vmlinuz1
|   |-- syslinux
|   |   |-- chain.c32
|   |   |-- drblwp.png
|   |   |-- memdisk
|   |   |-- menu.c32
|   |   |-- ocswp.png
|   |   |-- syslinux.cfg
|   |   `-- vesamenu.c32
|   `-- utils
|       |-- README.txt
|       |-- linux
|       |   |-- VERSION.txt
|       |   |-- makeboot.sh
|       |   `-- syslinux
|       |-- mbr
|       |   `-- mbr.bin
|       `-- win32
|           |-- VERSION.txt
|           |-- makeboot.bat
|           `-- syslinux.exe
|-- dban-floppy.img
|-- dsl_root
|   |-- boot
|   |   `-- isolinux
|   |       |-- boot.cat
|   |       |-- boot.msg
|   |       |-- f2
|   |       |-- f3
|   |       |-- german.kbd
|   |       |-- isolinux.bin
|   |       |-- isolinux.cfg
|   |       |-- linux24
|   |       |-- logo.16
|   |       `-- minirt24.gz
|   `-- index.html
|-- freedos.img
|-- grldr
|-- grub-rescue-floppy.img
|-- hirens_root
|   |-- Vdefs
|   |-- WinTools
|-- konboot-1.1.img
|-- memdisk
|-- memtest
|-- ntpasswd.img
|-- ophcrack_root(works so excluded)
|   |-- boot
|-- pmagic_root(works so excluded)
|   |-- boot
|   |   `-- grub
|-- pmagic
|   `--(important stuff)
|-- sbm.img
|-- super-grub_root
|   |-- grub
|   |   |-- choose
|   `-- sgd
|       |   `-- menu.lst
|       |-- menu.lst
|-- tables
|   `-- vista_free
|-- trinity_root
|   |-- boot.cat
|   |-- bootlogo.jpg
|   |-- initrd.trk
|   |-- isolinux.bin
|   |-- isolinux.cfg
|   |-- kernel.trk
|   |-- ldlinux.sys
|   |-- memdisk
|   |-- memtest.x86
|   |-- pxelinux.0
|   |-- pxelinux.cfg
|   |-- syslinux.cfg
|   |-- trinity.ico
|   |-- trk3
|   `-- vesamenu.c32
`-- ubuntu-9.04-desktop-i386.iso

I tried to make it as small as possible so there is a lot of stuff missing.

Link to comment
Share on other sites

Wish I would have read all the threads... mapping ISO's is much cleaner especially for the Trinity Rescue Kit I just mapped the ISO and renamed the USB to TRK_3-3 and it works.

Edit: Nevermind it was feeding off the other files I removed them and the ISO alone is'nt working :\

Link to comment
Share on other sites

I've read most of this thread and didn't see anything mentioned about U3? Forgive me if I missed it somewhere. Are you guys using U3 drives with the standard U3 partition? I have a SanDisk Cruzer 8GB with the standard U3 partition I haven't deleted or modified it yet.

I copied the menu.ls file from the show notes and I have just about all the files on the drive except for the BackTrack files.

When I boot off the drive It says (Try (hd0,0) FAT32:) for about 5 seconds then it says something else so fast I can't read it then just hangs with a flashing cursor. I posted earlier in the thread somewhere about an idea I had only I don't think I worded it that well.

After 1 has a U3 loaded with their choice of tools couldn't they image that drive creating an .iso and then flash another drive with the ISO and have a duplicate?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...