I'm in process of creating a bootable BackTrack 3 USB drive. From this link...
http://wirelessdefence.org/Contents/..._USB_Howto.htm
...I have successfully created two partitions as confirmed from the shell window using fdisk (code below)
please note USB drive listed as sdb
______________________
bt ~ # fdisk /dev/sdb
The number of cylinders for this disk is set to 7228.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 2013 MB, 2013265920 bytes
17 heads, 32 sectors/track, 7228 cylinders
Units = cylinders of 544 * 512 = 278528 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 3677 1000128 b W95 FAT32
/dev/sdb2 3678 7228 965872 83 Linux
______________________
...I then proceed to the mkdir command...(code below)
______________________
bt ~ # mkdir /usb
bt ~ # mkdir /usb1
bt ~ # mount /dev/sdb1 /usb
bt ~ # mount /dev/sdb2 /usb1
mount: No such file or directory
______________________
...fsck is unsuccessful thus far (code below)
______________________
bt ~ # fsck -a /dev/sdb2
fsck 1.39 (29-May-2006)
/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/sdb2
/dev/sdb2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
bt ~ # e2fsck -b 8193 /dev/sdb2
e2fsck 1.39 (29-May-2006)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
______________________
It looks like I will need to delete and recreate the partition since repairing it
doesn't look like an option.
HELP!!!!!
