Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Boot BT4 from ISO on NTFS partition

  1. #1
    Just burned his ISO
    Join Date
    Feb 2010
    Posts
    2

    Default Boot BT4 from ISO on NTFS partition

    Hello. I am using grub4dos on a large USB drive that is formatted as NTFS. I am trying to boot BT4.iso, and it begins to load, however it seems to get stuck in an infinite loop, printing "NTFS Volume 3.1" over and over again. Here is the contents of my menu.lst:

    title Backtrack4
    find --set-root /ISO/bt4.iso
    map /ISO/bt4.iso (hd32)
    map --hook
    root (hd32)
    kernel /boot/vmlinuz BOOT=casper boot=casper nopersistent rw from=ISO/bt4.iso
    initrd /boot/initrd800.gz
    boot

    The kernel is loaded and the boot sequence appears to be working just fine until the infinite loop starts. Does anyone know what I am doing wrong? I can provide more information if needed.

    Thanks

  2. #2
    Just burned his ISO
    Join Date
    Feb 2010
    Posts
    2

    Default Re: Boot BT4 from ISO on NTFS partition

    I have found a topic pertaining to a similar problem, however it deals with Knoppix:

    ISO boot from FAT/NTFS/USB (GRUB.exe, grldr from boot.ini) - Knoppix.net

    It seems that someone modified initrd with NTFS kernel modules so that the kernel was able to see NTFS partitions before mounting the filesystem.

    I'm not sure if this is the same problem I am having, but it could be. Can someone clarify if Backtrack is able to boot from an ISO stored on an NTFS partition? And if so, how? Is the "from" cheatcode I used above correct? Or is there a different one I should be using?

  3. #3
    Junior Member jnt13's Avatar
    Join Date
    Feb 2010
    Location
    Ontario, Canada
    Posts
    39

    Default Re: Boot BT4 from ISO on NTFS partition

    Im also seeing this problem. I made a multiboot usb using the tool from pendrive linux. I have dozens of ISO distro's on it, all booting and working fine except the custom bt4 copy, giving me the "NTFS Volume version 3.1" loop.

    The new tool formats the drive to NTFS. My guess is the NTFS format is obviously whats bugging it. Im guessing a boot parameter could fix this. Any suggestions???

    title BackTrack 4 Custom ISO
    find --set-root /bt4-cust.iso
    map /bt4-cust.iso (0xff)
    map --hook
    root (0xff)
    kernel /casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper nonpersistent iso-scan/filename=/bt4-cust.iso splash
    initrd /casper/initrd.gz
    Last edited by jnt13; 02-28-2010 at 09:09 AM.

  4. #4
    Junior Member jnt13's Avatar
    Join Date
    Feb 2010
    Location
    Ontario, Canada
    Posts
    39

    Default Re: Boot BT4 from ISO on NTFS partition

    I took another USB and formated to fat32 and I still got the same issue, on both my netbook, and desktop.

    On a side note. Is there any issue with booting from the BT4 iso as opposed to extracting the filesystem out of the iso. I assumed most tutorials did this because most want persistant changes.

    It seems to happen when the NTFS partitions get recognized during the end of the boot. I let the loop sit, and it eventually drops to the squsfs prompt. Here's my dmesg.

    Is there any boot tag that will prevent it from automounting drives?

    Code:
    ata1.00: ATA-8: WDC WD1600BEVT-75ZCT2, 11.01A11, max UDMA/133
    ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    scsi 2:0:0:0: Direct-Access     ATA      WDC WD1600BEVT-7 11.0 PQ: 0 ANSI: 5
    sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
     sda: sda1 sda2 sda3
    sd 2:0:0:0: [sda] Attached SCSI disk
    usb 1-1: new high speed USB device using ehci_hcd and address 2
    Freeing unused kernel memory: 432k freed
    Clocksource tsc unstable (delta = -173034267 ns)
    usb 1-1: configuration #1 chosen from 1 choice
    scsi4 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 2
    usb-storage: waiting for device to settle before scanning
    VMware vmxnet virtual NIC driver
    usb 1-2: new high speed USB device using ehci_hcd and address 3
    fuse init (API version 7.11)
    usb 1-2: configuration #1 chosen from 1 choice
    usb 1-3: new high speed USB device using ehci_hcd and address 4
    usb 1-3: configuration #1 chosen from 1 choice
    scsi5 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 4
    usb-storage: waiting for device to settle before scanning
    NTFS volume version 3.1.
    sd 2:0:0:0: Attached scsi generic sg0 type 0
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    scsi 4:0:0:0: Direct-Access              USB Flash Memory PMAP PQ: 0 ANSI: 0 CCS
    sd 4:0:0:0: Attached scsi generic sg1 type 0
    sd 4:0:0:0: [sdb] 31346688 512-byte hardware sectors: (16.0 GB/14.9 GiB)
    usb-storage: device scan complete
    sd 4:0:0:0: [sdb] Write Protect is off
    sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
    sd 4:0:0:0: [sdb] Assuming drive cache: write through
    sd 4:0:0:0: [sdb] Assuming drive cache: write through
     sdb: sdb1
    sd 4:0:0:0: [sdb] Attached SCSI removable disk
    scsi 5:0:0:0: Direct-Access     Generic- Multi-Card       1.00 PQ: 0 ANSI: 0 CCS
    sd 5:0:0:0: Attached scsi generic sg2 type 0
    usb-storage: device scan complete
    sd 5:0:0:0: [sdc] Attached SCSI removable disk
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.
    NTFS volume version 3.1.

  5. #5
    Junior Member
    Join Date
    May 2007
    Posts
    40

    Default

    Hi I use grub2 to boot ISOs from Fat32 any one successful booting form any fs?
    What is the right parameter? When I use from I get dropped to busybox!

    I use grub2 + fat32 stick to boot the iso. If I use from=....iso it dropps me to busybox. What is the parameter?
    Last edited by lupin; 04-26-2010 at 01:05 AM. Reason: Merging...

  6. #6
    Just burned his ISO
    Join Date
    May 2010
    Posts
    2

    Default Re: Boot BT4 from ISO on NTFS partition

    I had this same problem. Here is a patch for BT4's 'bootloader', casper. This solution is a little long winded.

    The only alternative seems to be to extract the CD to the root of your NTFS drive, which sucks.


    Booting BackTrack 4 Final Release ISO from an NTFS partition with GRUB4DOS.
    -----------------

    Booting from the BackTrack 4 ISO from NTFS is tricky. GRUB4DOS can be used to provide ISO mapping or emulation, but BT4's casper bootloader gets stuck during booting if you do this.

    (For me I could get GRUB4DOS to boot the kernel+rd, but when it went to mount the root filesystem it printed out "NTFS volume version 3.1" endlessly whilst searching all my disks for the ISO).

    This method uses the casper bootloader scripts to mount the ISO file directly from its physical location on the partition.

    The casper scripts in BT4 are missing some options and have some bugs, so we'll have to patch the initrd image. So you'll end up having the kernel and ramdisk image alongside the ISO file.

    Instructions
    -------------

    Install GRUB4DOS

    Put bt4-final.iso in a permanent location.

    Ensure the file is contiguous (has no fragments). You can use Mark Russinovich's contig.exe on the file to do this.

    Extract boot/vmlinuz and boot/initrd.gz from the ISO.

    Apply the casper.patch to initrd.gz.

    Put vmlinuz and the new initrd.new.gz somewhere on the NTFS partition (e.g. C:\Share\ISO\BT4\)

    Add a new grub4dos menu.lst entry for BT4. Heres mine:

    Code:
    title BT4
    kernel /share/iso/bt4/vmlinuz BOOT=casper boot=casper nopersistent live-media=/dev/sda2 live-media-offset=35450585088 textonly rw
    initrd /share/iso/bt4/initrd.gz
    where:

    live-media is the NTFS partition containing your ISO file (could be a /dev/hd* either) Note this the partition device (e.g. /dev/sda2), not the whole drive (/dev/sda).
    live-media-offset is the offset in bytes from the start of the partition to the first byte of the ISO file. I used WinHex to find this (Open partition, find ISO file, Right-click first byte, "Add Bookmark", offset is shown).

    The ISO should now boot.

    You'll have to take a look at its own grub menu.lst to change bootup options. If you want to just have one ISO file, you can rebuild it with the new initrd.gz in place of the old one.

    casper.patch:
    Code:
    --- casper.old	2010-05-14 18:55:45.887493444 +0100
    +++ casper	2010-05-14 19:03:51.517929507 +0100
    @@ -36,6 +36,10 @@
                     export PERSISTENT="" ;;
                 union=*)
                     export UNIONFS="${x#union=}";;
    +            live-media=*)
    +                export LIVEMEDIA=${x#live-media=} ;;
    +            live-media-offset=*)
    +                export LIVEMEDIA_OFFSET="${x#live-media-offset=}";;
                 ip*)
                     STATICIP=${x#ip=}
                     if [ "${STATICIP}" = "" ]; then
    @@ -544,7 +548,24 @@
     
         set_usplash_timeout
     
    -    if [ ! -z "${NETBOOT}" ]; then
    +    if [ -n "${LIVEMEDIA}" ] && [ -n "${LIVEMEDIA_OFFSET}" ]; then
    +        # Regular casper code should work when using LIVEMEDIA_OFFSET, but is
    +        # broken in mount_images_in_directory() due to a bug in
    +        # busybox's 'losetup -f' which always return '/dev/loop0' even when
    +        # /dev/loop0 is in use. Do things by hand here instead.
    +        i=0
    +        while [ ! -b "${LIVEMEDIA}" ] && [ "$i" -lt 20 ]; do
    +            sleep 1            # Wait on udev for devices to appear
    +            i="$(($i + 1))"
    +        done
    +        losetup -o "${LIVEMEDIA_OFFSET}" /dev/loop1 "${LIVEMEDIA}"
    +        mount -t iso9660 /dev/loop1 "${mountpoint}"
    +        if is_casper_path $mountpoint; then
    +            livefs_root="${mountpoint}"
    +        else
    +            panic "Unable to find a live file system on iso9660 image at ${LIVEMEDIA}:${LIVEMEDIA_OFFSET}"
    +        fi
    +    elif [ ! -z "${NETBOOT}" ]; then
             if do_netmount ; then
                 livefs_root="${mountpoint}"
             else
    apply_patch.sh:
    Code:
    #!/bin/sh
    # Ensure casper.patch and original BT4 initrd.gz are in this directory
    
    mkdir initrd
    cd initrd
    gzip -dc ../initrd.gz | cpio -id
    cd scripts
    patch -p0 < ../../casper.patch
    cd ..
    find ./ | cpio -H newc -o > ../initrd.new
    cd ..
    gzip -f initrd.new
    File allegati File allegati
    Last edited by mcjerk; 05-15-2010 at 02:57 PM. Reason: paste code, spelling, clarification

  7. #7
    Just burned his ISO
    Join Date
    Apr 2010
    Posts
    2

    Default Re: Boot BT4 from ISO on NTFS partition

    Thanks for perfect manual... but is there any way to save changes booting ISO from NTFS drive? I've tried standard method but it's doesn't work

  8. #8
    Just burned his ISO
    Join Date
    Nov 2010
    Posts
    1

    Default Re : Boot BT4 from ISO on NTFS partition

    Hi,
    I'm a total noob so don't beat me down
    I experienced this issue of the "NTFS volume version 3.1" followed by a Busybox shell.
    To "solve" it I simply removed my hard drive : it worked but then the boot sequence hangs on something like "mounting rootfile" (I don't remember and, consedering I must remove my hard drive to go that "far" I can't check it right away in the public square I'm writing from).
    Sometimes it goes a little further, listing my usb devices I guess (removing all them out do not solve the problem).
    Suddenly my DVD reader stops and then I have to reboot. All I can write is not taken into account.

    I've a Toshiba Satellite x200 and I tried every choices in the boot menu.

  9. #9
    Just burned his ISO
    Join Date
    Dec 2010
    Posts
    1

    Exclamation AW: Boot BT4 from ISO on NTFS partition

    Hi everyboy,

    thanks for your patch but it doesn't work.

    -I have extract the initrd.gz from ISO file (bt4.iso).
    -than I apply the patch and get the new initrd.gz file
    -now I replace the existing initrd.gz in ISO file
    -if I boot these configuration I get the error:

    Code:
    NTFS volume version 3.1
    EXT3-fs: sda2: couldn't mount because of unsupported optional features (240)
    Code:
    title   Backtrack 4
    find --set-root /grldr
    map --heads=0 --sectors-per-track=0 /images/bt4.iso (hd32)
    map --hook
    chainloader (hd32)
    boot
    root (hd32)
    kernel /boot/vmlinuz BOOT=casper boot=casper nopersistent live-media=/dev/sda2 live-media-offset=15708160 findiso=/images/bt4.iso
    initrd /boot/initrd.gz
    Have anyone an idea to solve this problem?

    I don't understand this. So many boot sources are already work, why Backtrack not?

    Thanks and sorry for my poor english.

    Thx EvilToken

  10. #10
    Just burned his ISO
    Join Date
    Feb 2006
    Posts
    4

    Default Re: Boot BT4 from ISO on NTFS partition

    The patch works great. No problems. I use Syslinux for booting everything and anything including Mac/Chain loading Chameleon. At first I kept getting the NTFS loop. I always use a fat32 partition for all the kernels and images. I have a nice multiboot going. I put the extracted contents of the R2 iso into /BT4 of my booter and adjusted my APPEND line options. I get this loop because it cannot find a root device. It looks in the wrong place hence the loop. So I applied the patch, adjusted the live-media and offset options. Copied the bt4-r2.iso into /BT4. Works great. EvilToken, try to follow this and see if it works. I used backtrack 3 to modify and package the initrd.

    sda = 80Gig with 4 parts
    sda1= 25GB fat32 syslinux installed
    sda2= 25GB ntfs for storage
    sda3= 11GB OSX Journaled(iATKOS v7 Installer)
    sda4= 12GB OSX Journaled for storage

    Load Backtrack 3
    Code:
    mkdir /mnt/bt4
    mount -t iso9660 -o loop ~/bt4-r2.iso /mnt/bt4
    mkdir /tmp/bt4test
    cp /mnt/bt4/boot/initrd.gz /tmp/bt4test
    cd /tmp/bt4test
    gzip -dc ./initrd.gz | cpio -i
    rm ./initrd.gz
    cd ./scripts
    patch -p0 < ~/casper.patch
    cd ..
    find . | cpio -o -H newc | gzip -9 > ./initrd.gz
    mkdir /mnt/sda1
    mount -t vfat /dev/sda1 /mnt/sda1
    cp ./initrd.gz /mnt/sda1/boot/kernels/initrd.bt4
    cp /mnt/bt4/boot/vmlinuz /mnt/sda1/boot/kernels/vmlinuz.bt4
    umount /mnt/bt4
    mkdir /mnt/sda1/BT4
    cp ~/bt4-r2.iso /mnt/sda1/BT4/
    There is no need to recreate the iso. All I've done is patched the casper script inside the initrd.gz image. Now we use that for booting. I've copied the vmlinuz off the iso to my syslinux structure. Copied the iso to a custom folder. Used winhex to retrieve the physical offset of the iso file on the sda1 partition. Mine was 462C56C00 = 18836974592 in decimal which is the format we need for the offset. Added this to my cfg.

    Code:
    LABEL bt4
    MENU LABEL ^Backtrack 4
    MENU INDENT 3
    KERNEL /boot/kernels/vmlinuz.bt4
    INITRD /boot/kernels/initrd.bt4
    APPEND BOOT=casper boot=casper nopersistent live-media=/dev/sda1 live-media-offset=18836974592 rw vga=0x317
    TEXT HELP
    Version 4 Release 2
    ENDTEXT
    worked great. Maybe replacing the internal initrd in the iso is your problem? Give this a shot.

Page 1 of 2 12 LastLast

Similar Threads

  1. BT4 final doesn't detect NTFS partitions?
    By kulverstukas in forum BackTrack Bugs
    Replies: 6
    Last Post: 09-29-2010, 04:57 PM
  2. Boot Error (Can Start but not Boot)
    By AtHacks in forum Beginners Forum
    Replies: 6
    Last Post: 02-20-2010, 10:35 AM
  3. NTFS Mount failed
    By secnav in forum Beginners Forum
    Replies: 3
    Last Post: 01-25-2010, 12:17 AM
  4. Installing onto a prepared partition
    By Rupert3k in forum Beginners Forum
    Replies: 1
    Last Post: 01-23-2010, 06:38 PM
  5. Partition differnt hardrive
    By HootieMcWoot in forum Beginners Forum
    Replies: 2
    Last Post: 01-22-2010, 01:35 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •