Results 1 to 7 of 7

Thread: Problem installing BTR3 persistent usb

  1. #1
    Just burned their ISO
    Join Date
    Feb 2010
    Location
    NYC
    Posts
    19

    Question Problem installing BTR3 persistent usb

    after booting to the usb, I get a blank screen with a repeating while line pulsating.

    I have follow the following next tutorial:

    http://www.backtrack-linux.org/wiki/...Persistent_USB


    using the following Equipment and software

    Windows 7 x 64

    Vmware 9 running

    BT5R3 KDE 32



    Code:
    dmesg | egrep hd.\|sd.
    
    fdisk /dev/sdb
    
    Command (m for help): d
    Partition number (1-4): 1
    
    Command (m for help): n
    Command action
    e   extended
    p   primary partition (1-4)
    p
    Partition number (1-4): 1
    First cylinder (1-522, default 1): 
    Using default value 1
    Last cylinder, +cylinders or +size{K,M,G} (1-522, default 522): +3500M
    
    
    
    Command action
    e   extended
    p   primary partition (1-4)
    p
    Partition number (1-4): 2
    First cylinder (193-522, default 193): 
    Using default value 193
    Last cylinder, +cylinders or +size{K,M,G} (193-522, default 522): 
    Using default value 522
    
    Command (m for help): t
    Partition number (1-4): 1
    Hex code (type L to list codes): b
    Changed system type of partition 1 to b (W95 FAT32)
    
    
    Command (m for help): t 
    Partition number (1-4): 2
    Hex code (type L to list codes): 83
    
    
    Command (m for help): a
    Partition number (1-4): 1
    
    Command (m for help): w
    
    
    mkfs.vfat -F 32 -n BT5 /dev/sdb1
    mkfs.ext3 -b 4096 -L casper-rw /dev/sdb2
    
    
    
    mkdir /mnt/sdb1
    mount /dev/sdb1 /mnt/sdb1
    
    
    cd /mnt/sdb1
    rsync -r /cdrom/* .
    
    
    syslinux /dev/sdb1
    
    cp -r isolinux syslinux
    cp syslinux/isolinux.cfg syslinux/syslinux.cfg
    cp syslinux/isolinux.bin syslinux/syslinux.bin
    
    
    nano syslinux/syslinux.cfg
    and i modify the last screen so it look like this
    Code:
    default vesamenu.c32
    prompt 0
    timeout 300
    
    menu title BackTrack Live CD
    menu background splash.png
    menu color title 1;37;44 #c0ffffff #00000000 std
    
    label DEFAULT
      menu label BackTrack Persistent Text - Persistent Text Mode Boot
      kernel /casper/vmlinuz
      append  file=/cdrom/preseed/custom.seed boot=casper persistent initrd=/casper/initrd.gz text splash vga=791--
    
    label text
      menu label BackTrack Text - Boot Text Mode
      kernel /casper/vmlinuz
      append  file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrd.gz text splash vga=791--
    
    label STEALTH
      menu label BackTrack Stealth - No Networking enabled
      kernel /casper/vmlinuz
      append  file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrds.gz text splash staticip vga=791--
    
    label FORENSICS
      menu label BackTrack Forensics - No Drive or Swap Mount
      kernel /casper/vmlinuz
      append  file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrdf.gz text splash vga=791--
    
    label NODRM
      menu label BackTrack noDRM - No DRM Drivers
      kernel /casper/vmlinuz
      append  file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrd.gz text splash nomodeset vga=791--
    
    label debug
      menu label BackTrack Debug - Safe Mode
      kernel /casper/vmlinuz
      append  file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrd.gz text--
    
    label memtest
      menu label BackTrack Memtest - Run memtest
      kernel /isolinux/memtest
      append -
    
    label hd
      menu label Hard Drive Boot - boot the first hard disk
      localboot 0x80
      append -
    but I was un sure to what to do next so I just closed the shell.
    should I have done something, else?


    thank you

  2. #2
    Very good friend of the forum maverik35's Avatar
    Join Date
    Sep 2009
    Location
    Debian land
    Posts
    734

    Default Re: Problem installing BTR3 persistent usb

    You did everything ok. The issue here it could be, and almost sure a video issue..

    What is your video card type? and module loaded to it by kernel if any? You might want to post that info.

    Luck.

  3. #3
    Just burned their ISO
    Join Date
    Feb 2010
    Location
    NYC
    Posts
    19

    Default Re: Problem installing BTR3 persistent usb

    I ran dxdiag

    and got this



    Display Devices
    ---------------
    Card name: ATI Mobility Radeon HD 5830 Series
    Manufacturer: ATI Technologies Inc.
    Chip type: ATI display adapter (0x68A1)
    DAC type: Internal DAC(400MHz)
    Device Key: Enum\PCI\VEN_1002&DEV_68A1&SUBSYS_1522103C&REV_00
    Display Memory: 4071 MB
    Dedicated Memory: 1011 MB
    Shared Memory: 3059 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)
    Monitor Name: Generic PnP Monitor
    Monitor Model: unknown
    Monitor Id: LGD01FB
    Native Mode: 1920 x 1080(p) (59.934Hz)
    Output Type: Internal
    Driver Name: atiu9p64.dll,aticfx64.dll,aticfx64.dll,atiu9pag,at icfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64 .dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a. cap,atitmm64.dll
    Driver File Version: 8.14.0001.6099 (English)
    Driver Version: 8.712.0.0
    DDI Version: 11
    Driver Model: WDDM 1.1
    Driver Attributes: Final Retail
    Driver Date/Size: 3/2/2010 22:06:36, 28160 bytes
    WHQL Logo'd: Yes
    WHQL Date Stamp:
    Device Identifier: {D7B71EE2-2BE1-11CF-5F64-2335A1C2C535}
    Vendor ID: 0x1002
    Device ID: 0x68A1
    SubSys ID: 0x1522103C
    Revision ID: 0x0000
    Driver Strong Name: oem19.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Manhattan:8 .712.0.0ci\ven_1002&dev_68a1&subsys_1522103c
    Rank Of Driver: 00E60001
    Video Accel: ModeMPEG2_A ModeMPEG2_C

  4. #4
    Just burned their ISO
    Join Date
    Feb 2010
    Location
    NYC
    Posts
    19

    Default Re: Problem installing BTR3 persistent usb

    Here is the code that I have use to make a peristent usb.
    I'm following the wiki persistent usb at http://www.backtrack-linux.org/wiki/...Persistent_USB

    I'm running wMware workstation 9 btr3 kde 64


    Code:
    root@bt:~# dmesg | egrep hd.\|sd.
    [    0.224912] NMI watchdog enabled, takes one hw-pmu counter.
    [    0.238972] NMI watchdog enabled, takes one hw-pmu counter.
    [    0.253759] NMI watchdog enabled, takes one hw-pmu counter.
    [    0.267489] NMI watchdog enabled, takes one hw-pmu counter.
    [    5.127966] sd 2:0:0:0: Attached scsi generic sg1 type 0
    [    5.128765] sd 2:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 GB/20.0 GiB)
    [    5.129533] sd 2:0:0:0: [sda] Write Protect is off
    [    5.130199] sd 2:0:0:0: [sda] Mode Sense: 61 00 00 00
    [    5.130995] sd 2:0:0:0: [sda] Cache data unavailable
    [    5.132176] sd 2:0:0:0: [sda] Assuming drive cache: write through
    [    5.133571] sd 2:0:0:0: [sda] Cache data unavailable
    [    5.134319] sd 2:0:0:0: [sda] Assuming drive cache: write through
    [    5.135514]  sda: unknown partition table
    [    5.136930] sd 2:0:0:0: [sda] Cache data unavailable
    [    5.137884] sd 2:0:0:0: [sda] Assuming drive cache: write through
    [    5.138874] sd 2:0:0:0: [sda] Attached SCSI disk
    [  518.994277] sd 3:0:0:0: Attached scsi generic sg2 type 0
    [  518.999232] sd 3:0:0:0: [sdb] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  519.007112] sd 3:0:0:0: [sdb] Write Protect is off
    [  519.007118] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
    [  519.015120] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [  519.049092]  sdb: sdb1
    [  519.078043] sd 3:0:0:0: [sdb] Attached SCSI removable disk
    root@bt:~# fdisk /dev/sdb
    
    WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
             switch off the mode (command 'c') and change display units to
             sectors (command 'u').
    
    Command (m for help): U
    Changing display/entry units to sectors
    
    Command (m for help): D
    Selected partition 1
    
    Command (m for help): 1
    1: unknown command
    Command action
       a   toggle a bootable flag
       b   edit bsd disklabel
       c   toggle the dos compatibility flag
       d   delete a partition
       l   list known partition types
       m   print this menu
       n   add a new partition
       o   create a new empty DOS partition table
       p   print the partition table
       q   quit without saving changes
       s   create a new empty Sun disklabel
       t   change a partition's system id
       u   change display/entry units
       v   verify the partition table
       w   write table to disk and exit
       x   extra functionality (experts only)
    
    Command (m for help): D
    No partition is defined yet!
    
    Command (m for help): N
    Command action
       e   extended
       p   primary partition (1-4)
    P
    Partition number (1-4): 1
    First sector (63-62530623, default 63): 
    Using default value 63
    Last sector, +sectors or +size{K,M,G} (63-62530623, default 62530623): +3500M
    
    Command (m for help): N
    Command action
       e   extended
       p   primary partition (1-4)
    P
    Partition number (1-4): 2
    First sector (7168064-62530623, default 7168064): 
    Using default value 7168064
    Last sector, +sectors or +size{K,M,G} (7168064-62530623, default 62530623):
    Using default value 62530623
    
    Command (m for help): T
    Partition number (1-4): 1
    Hex code (type L to list codes): B
    Changed system type of partition 1 to b (W95 FAT32)
    
    Command (m for help): T
    Partition number (1-4): 2
    Hex code (type L to list codes): 83
    
    Command (m for help): A
    Partition number (1-4): 1
    
    Command (m for help): W
    The partition table has been altered!
    
    Calling ioctl() to re-read partition table.
    
    WARNING: If you have created or modified any DOS 6.x
    partitions, please see the fdisk manual page for additional
    information.
    Syncing disks.
    root@bt:~# dmesg | egrep hd.\|sd.
    [    0.224912] NMI watchdog enabled, takes one hw-pmu counter.
    [    0.238972] NMI watchdog enabled, takes one hw-pmu counter.
    [    0.253759] NMI watchdog enabled, takes one hw-pmu counter.
    [    0.267489] NMI watchdog enabled, takes one hw-pmu counter.
    [    5.127966] sd 2:0:0:0: Attached scsi generic sg1 type 0
    [    5.128765] sd 2:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 GB/20.0 GiB)
    [    5.129533] sd 2:0:0:0: [sda] Write Protect is off
    [    5.130199] sd 2:0:0:0: [sda] Mode Sense: 61 00 00 00
    [    5.130995] sd 2:0:0:0: [sda] Cache data unavailable
    [    5.132176] sd 2:0:0:0: [sda] Assuming drive cache: write through
    [    5.133571] sd 2:0:0:0: [sda] Cache data unavailable
    [    5.134319] sd 2:0:0:0: [sda] Assuming drive cache: write through
    [    5.135514]  sda: unknown partition table
    [    5.136930] sd 2:0:0:0: [sda] Cache data unavailable
    [    5.137884] sd 2:0:0:0: [sda] Assuming drive cache: write through
    [    5.138874] sd 2:0:0:0: [sda] Attached SCSI disk
    [  518.994277] sd 3:0:0:0: Attached scsi generic sg2 type 0
    [  518.999232] sd 3:0:0:0: [sdb] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  519.007112] sd 3:0:0:0: [sdb] Write Protect is off
    [  519.007118] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
    [  519.015120] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [  519.049092]  sdb: sdb1
    [  519.078043] sd 3:0:0:0: [sdb] Attached SCSI removable disk
    [  953.954164]  sdb: sdb1 sdb2
    [  992.732823] sd 4:0:0:0: Attached scsi generic sg2 type 0
    [  992.737992] sd 4:0:0:0: [sdb] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  992.745830] sd 4:0:0:0: [sdb] Write Protect is off
    [  992.745836] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
    [  992.754464] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [  992.789808]  sdb: sdb1 sdb2
    [  992.817759] sd 4:0:0:0: [sdb] Attached SCSI removable disk
    root@bt:~# mkfs.vfat -F 32 -n BT5 /dev/sdb1
    mkfs.vfat 3.0.7 (24 Dec 2009)
    root@bt:~# mkfs.ext3 -b 4096 -L casper-rw /dev/sdb2
    mke2fs 1.41.11 (14-Mar-2010)
    Filesystem label=casper-rw
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    Stride=0 blocks, Stripe width=0 blocks
    1733312 inodes, 6920320 blocks
    346016 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=4294967296
    212 block groups
    32768 blocks per group, 32768 fragments per group
    8176 inodes per group
    Superblock backups stored on blocks: 
            32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
            4096000
    
    Writing inode tables: done                            
    Creating journal (32768 blocks): done
    Writing superblocks and filesystem accounting information: done
    
    This filesystem will be automatically checked every 23 mounts or
    180 days, whichever comes first.  Use tune2fs -c or -i to override.
    root@bt:~# mkdir /mnt/sdb1
    root@bt:~# mount /dev/sdb1 /mnt/sdb1
    mount: special device /dev/sdb1 does not exist
    root@bt:~# cd /mnt/sdb1
    root@bt:/mnt/sdb1# rsync -r /cdrom/* .
    rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
    rsync: write failed on "/mnt/sdb1/casper/filesystem.squashfs": No space left on device (28)
    rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7]
    rsync: connection unexpectedly closed (164 bytes received so far) [sender]
    rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]
    root@bt:/mnt/sdb1# syslinux /dev/sdb1
    /dev/sdb1: No such file or directory
    root@bt:/mnt/sdb1# syslinux /dev/sdb
    /dev/sdb: No such file or directory
    root@bt:/mnt/sdb1#
    I notice that when I type in:
    root@bt:~# mount /dev/sdb1 /mnt/sdb1

    I get

    mount: special device /dev/sdb1 does not exist

    Is this the my problem?

  5. #5
    Good friend of the forums zimmaro's Avatar
    Join Date
    Mar 2010
    Location
    milano
    Posts
    407

    Default Re: Problem installing BTR3 persistent usb

    I notice that when I type in:
    root@bt:~# mount /dev/sdb1 /mnt/sdb1

    I get

    mount: special device /dev/sdb1 does not exist

    Is this the my problem?[/QUOTE]

    hi
    (i think)yes for me the problem is here! try to ""extract & re-insert"" your usb-device
    i'm testing now the procedure (in VMware-player) to build my bt5-r3-USB 8gb(cruizer):


    *****I had a similar problem in this step:************

    root @ bt: ~ # mkfs.vfat-F 32-n BT5 / dev/sdb1
    mkfs.vfat 3.0.7 (24 Dec 2009)
    / dev/sdb1: No such file or directory ??????????????????

    ****I disconnected & reconnected my usb (physically) and everything went smoothly thus far:*******

    root @ bt: ~ # mkfs.vfat-F 32-n BT5 / dev/sdb1
    mkfs.vfat 3.0.7 (24 Dec 2009)
    root @ bt: ~ # mkfs.ext3-b 4096-L casper-rw / dev/sdb2
    mke2fs 1:41:11 (14-Mar-2010)
    Filesystem label = casper-rw
    OS type: Linux
    Block size = 4096 (log = 2)
    Fragment size = 4096 (log = 2)
    Stride = 0 blocks, Stripe width = 0 blocks
    264528 inodes, 1058032 blocks
    52901 blocks (5.00%) reserved for the super user
    First data block = 0
    Maximum filesystem blocks = 1086324736
    33 block groups
    32768 blocks per group, 32768 fragments per group
    8016 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736

    Writing inode tables: done
    Creating journal (32768 blocks): done
    Writing superblocks and filesystem accounting information: done

    This filesystem will be automatically checked every 33 mounts or
    180 days, whichever comes first. Use tune2fs-c or-i to override.
    root @ bt: ~ # mkdir / mnt/sdb1
    root @ bt: ~ # mount / dev/sdb1 / mnt/sdb1
    root @ bt: ~ # cd / mnt/sdb1
    root @ bt :/ mnt/sdb1 # rsync-r / cdrom / *.
    rsync: link_stat "/ cdrom / *" failed: No such file or directory (2) ????????????????
    rsync error: some files / attrs were not Transferred (see previous errors) (code 23) at main.c (1060) [sender = 3.0.7] ????????

    ******then I thought "" auto-mount "" CDROM in VMWARE .. & I corrected this way:********************

    root @ bt :/ mnt/sdb1 # rsync-r / media/BT5 / *.
    root @ bt :/ mnt/sdb1 # syslinux / dev/sdb1
    root @ bt :/ # cp-r mnt/sdb1 isolinux syslinux
    root @ bt :/ # cp mnt/sdb1 syslinux / isolinux.cfg syslinux / syslinux.cfg
    root @ bt :/ # cp mnt/sdb1 syslinux / syslinux isolinux.bin / syslinux.bin
    root@bt:/mnt/sdb1# gedit syslinux/syslinux.cfg............

    at finish try my usb-persistence to boot ""vmware-way"" & WORKED!
    bye

  6. #6
    Just burned their ISO
    Join Date
    Feb 2010
    Location
    NYC
    Posts
    19

    Default Re: Problem installing BTR3 persistent usb

    Quote Originally Posted by zimmaro View Post
    I notice that when I type in:
    root@bt:~# mount /dev/sdb1 /mnt/sdb1

    I get

    mount: special device /dev/sdb1 does not exist

    Is this the my problem?
    hi
    (i think)yes for me the problem is here! try to ""extract & re-insert"" your usb-device
    i'm testing now the procedure (in VMware-player) to build my bt5-r3-USB 8gb(cruizer):


    *****I had a similar problem in this step:************

    root @ bt: ~ # mkfs.vfat-F 32-n BT5 / dev/sdb1
    mkfs.vfat 3.0.7 (24 Dec 2009)
    / dev/sdb1: No such file or directory ??????????????????

    ****I disconnected & reconnected my usb (physically) and everything went smoothly thus far:*******

    root @ bt: ~ # mkfs.vfat-F 32-n BT5 / dev/sdb1
    mkfs.vfat 3.0.7 (24 Dec 2009)
    root @ bt: ~ # mkfs.ext3-b 4096-L casper-rw / dev/sdb2
    mke2fs 1:41:11 (14-Mar-2010)
    Filesystem label = casper-rw
    OS type: Linux
    Block size = 4096 (log = 2)
    Fragment size = 4096 (log = 2)
    Stride = 0 blocks, Stripe width = 0 blocks
    264528 inodes, 1058032 blocks
    52901 blocks (5.00%) reserved for the super user
    First data block = 0
    Maximum filesystem blocks = 1086324736
    33 block groups
    32768 blocks per group, 32768 fragments per group
    8016 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736

    Writing inode tables: done
    Creating journal (32768 blocks): done
    Writing superblocks and filesystem accounting information: done

    This filesystem will be automatically checked every 33 mounts or
    180 days, whichever comes first. Use tune2fs-c or-i to override.
    root @ bt: ~ # mkdir / mnt/sdb1
    root @ bt: ~ # mount / dev/sdb1 / mnt/sdb1
    root @ bt: ~ # cd / mnt/sdb1
    root @ bt :/ mnt/sdb1 # rsync-r / cdrom / *.
    rsync: link_stat "/ cdrom / *" failed: No such file or directory (2) ????????????????
    rsync error: some files / attrs were not Transferred (see previous errors) (code 23) at main.c (1060) [sender = 3.0.7] ????????

    ******then I thought "" auto-mount "" CDROM in VMWARE .. & I corrected this way:********************

    root @ bt :/ mnt/sdb1 # rsync-r / media/BT5 / *.
    root @ bt :/ mnt/sdb1 # syslinux / dev/sdb1
    root @ bt :/ # cp-r mnt/sdb1 isolinux syslinux
    root @ bt :/ # cp mnt/sdb1 syslinux / isolinux.cfg syslinux / syslinux.cfg
    root @ bt :/ # cp mnt/sdb1 syslinux / syslinux isolinux.bin / syslinux.bin
    root@bt:/mnt/sdb1# gedit syslinux/syslinux.cfg............

    at finish try my usb-persistence to boot ""vmware-way"" & WORKED!
    bye[/QUOTE]

    when you type
    "root @ bt :/ mnt/sdb1 # rsync-r / media/BT5 / *."
    should i type in BT5, even when VMware is running BTR5 kde x 64 originallty from an iso?
    I use btr3 kde 64 to run a virtual machine using VMware, and the media was originally and iso.

    thank you

  7. #7
    Good friend of the forums zimmaro's Avatar
    Join Date
    Mar 2010
    Location
    milano
    Posts
    407

    Default Re: Problem installing BTR3 persistent usb

    hi
    I have performed the procedure on a linux machine installed in VMware-player (release3 backtrack 5 gnome 32)
    "instead of" the. iso to install on USB-key I inserted the CD / ROM (BT5-r3-gnome32) [the-same .ISO mastered]
    ..&& connect CD/ROM to virtual machines

Similar Threads

  1. Installing backtrack 5r3 persistent to USB
    By ThePie69 in forum BackTrack 5 Beginners Section
    Replies: 8
    Last Post: 12-14-2012, 06:56 PM
  2. Error when installing BTR3 in Vmware/VirtualBox
    By btparsing in forum BackTrack 5 Beginners Section
    Replies: 2
    Last Post: 12-03-2012, 04:28 AM
  3. problem with installing bt5 on persistent usb drive
    By phrozenglow in forum BackTrack 5 Beginners Section
    Replies: 0
    Last Post: 08-17-2011, 02:49 PM
  4. error when Installing to USB with persistent changes
    By Jaylong in forum BackTrack 5 Beginners Section
    Replies: 0
    Last Post: 05-13-2011, 06:11 AM
  5. Problems when installing BT4 persistent in USB
    By KnightSakabatto in forum Beginners Forum
    Replies: 1
    Last Post: 10-28-2010, 10:38 AM

Posting Permissions

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