This leads me to believe one of two things:. First we want to confirm the that the modules we need were copied over. There will be other stuff in there, but those two are the ones we want to confirm. Finally we want to confirm that lvm is included and our pvcrypt script is where it belongs. If any of the above is not true, then we have an issue with the rebuild of the initrd image. Run update-initramfs -u again and recheck this stuff.
If none of that helps, I am a bit of a loss on next steps other than to start over completely by deleting any partitions and rebooting.
Should I edit the script. Backtrack has loaded just fine, although sometimes it seems a little slower then on the CD or HD. Also my wireless is not working I keep getting a code error 80ba or something like that when I enter the password for the wireless access point.
I had no problem with my wireless when I had bt4 installed on my HD. Any suggestions? Previously I installed and used Network Manager. I also tried providing the pwd in hex. The system is taking the essid just fine as reflected in iwconfig cmd. Do you have any suggestions or do you know of any issues with wireless when used on the USB? Thanks again. Forget the stuff about the wireless, I think I figured it out.
I have gotten the wicd working and it is trying to obtain and ip address. I also got the wireless to accept my girl friends pwd after again coverting to hex. Now all I got to do is get it to give me an IP address, hopefully I can figure that out soon. I hope that is all that is broke. Thanks again, but still, any of your suggestions are welcome. This is definitely a process!! Iv tried updating initramfs again but its exactly the same. That is pretty bizarre stuff with the wireless. A trip to the remote-exploit.
The fact that xts. Something bad happened. As you indicate, a re-install is probably the best thing to try. Should I try to download it again or paste it in as above?
Of should I leave it as it is, currently empty? Yes, you want to make sure that script is there. It is used every time a rebuild of the initrd image is done and makes sure some important files are copied to the image. I do not have a boot partition on my 8GB thumb drive. I did use fdisk to create it in an earlier step.
Is there a step missing? Everything needed to complete the install is included in the how-to. My first guess is that the partition table is not getting written correctly. What does the out put of. Opening the install. According to your screenshot, I should have a MB boot partition. It almost looks like there is one large extended partition that is then partitioned into more logical partitions. The contents of the install. First create the MB primary partition, then create the extended partition with the rest of the drive and create the logical partition.
The output of the fdisk -l command should look more like this:. Note: I think I also realized something else you are doing. It looks like you are creating the 3rd partition as a primary partition and not a logical one. Thanks Kevin, I downloaded the script but it was again blank. So, I just added the 1st. I am rebooting now to see if it had any negative effects.
Mmmm…every loaded fine with no errors. What do you think the chances of me being hacked using the LAN with the encrypted file system? During a network hack where I was on the LAN would the encrypted disk ask anyone that attempted to connect for the LUKS pwd, or would the system allow a connection to mount the drive encrypted drive.
I would think hopefully not. Once you have booted the system and entered the password, the drive is accessible to locally logged on users. If you turn on samba or nfs or some other file sharing service and allow anonymous access or some gains access to that service, they will see the files on disk. The encryption ensures that a lost thumb drive cannot be read, not an up and operating system.
Thanks for the awesome tutorial! I started from the top and this time everything went smoothly. No hitches at all. Enabling encryption does affect performance slightly, but the thumb drive and computer itself contribute more to the equation in my experience. Great insight on the network security part of this.
However, in my spare time I will read up on how all of this works together and get a more deeper and granular understanding of the crypto and functionality.
Now I know I should have enabled iptables first before going on the network, hopefully I was lucky enough that nobody attempted any local hacks from the network on the os. Hopefully BT4 comes reasonably secure in the default that I was not totally insecure. Thanks again for all your insight and assistance. I did a quick run through on your tutorial only to run into partitioning problems not realizing sdb, sdb1, sdb2, etc.
Not an issue! I will start over. The kernel still uses the old table. The new table will be used at the next reboot. Backtrack out of the box is very secure. There are no listening services so chances of anything bad happening are very very slim. You are welcome. I have experienced that error before. It has never gotten in the way that I can remember and, yup, pick your own passphrase..
Thanks for the alternate command for randomizing the disk. I have followed your tutorial and have successfully created a fully encrypted Back Track 4 installation on my 8gb flash drive. Your well-written article is an excellent addition to the Back Track homepage how-to section. As a side note to any users following this tutorial, here are some of the things I encountered that confused me.
Using the final write w command using fdisk can give you an error 22 about the kernel still using the old table…just ignore it or use the o command on your drive before performing ANY of the partitioning steps and it should not bug you when you go to write.
I think mine was 2 actually. On the type passphrase step. Please enter your own! I can see fifty users out in the world with this advanced encryption scheme all with the same log-in pass…I almost entered passphrase!
Make up your own! The script and modules files you have to edit might be hidden if you use Konquer file explorer. Just cd into the directory and use nano to edit the files. Thank you for suggestion 5 I was having a helluva time trying to find a way to edit the file.
Used nano, and it worked great! It made me think of trying too to skip the installtion script and do it all manually. I dont think it wood be that much more work. A quick howto in converting , The partions can not bee mounted I rebooted using my backtrack CD and install apt-get install hashalot lvm2 again. I then got the following:. I thought i had maybe entered the wrong passphrase and thought it best to check it using the process in your guide where it says that if you remember the passphrase you dont need to do everything all over again.
The system then asked for my passphrase — i used the one i had used previously and it was accepted. This leads me to the conclusion that my passphrase was correct. Why then does the system not accept it at boot time, yet accepts it if i try to mount the encrypted partition from within the installer?
Thank you for the compliment. The error you are seeing is usually an indication that one of the crypto modules did not make it into the initrd image. Here is a series of things to check after you have remounted the encrypted image and chrooted to that environment. The other individual who had this same problem ended up starting over and it worked the second time around.
Thanks very much for the advice on my question above. In the end i just re-did everything from scratch and it worked like a charm. Its strange. Some people say it works out of the box, others say you need to install new drivers. Go back to the how-to and see where you need to chroot to the system after you finish the install. You will also need to reinstall hashalot and lvm2 again and follow the rest of the steps. My experience with getting wireless working on Backtrack has been hit or miss.
I have everything working fine. The initial errors are all gone and once I placed the 1st script in its proper place good things really started to happen. My whole system updated properly as i had run the upgrade for BT4 earlier. As you stated previously the initrd image must have gotten updated by that script after I placed it correctly. Wireless is working great after setting it manually, I was making some very basic errors and it is suggested that it be set manually instead of dynamically at the BT forums.
The encryption has a impact om speed but not that bad belive it is my old and slow CPU that limits it most. I have a 8gig stick when you need this info. Others have experienced this problem and it went away on redoing the build, but apparently that is not working for you. The full file should look something like this:. List of modules that you want to include in your initramfs. Confirm that it looks like this or do the following after mounting and chrooting to the installed Backtrack environment:.
Some people are having issues with the xts. Most have been able to correct this by redoing the install, but I wondered if maybe a consistent modules file would help, i. To that end, I have modified the how-to. I created a preconfigured modules file like I did for the two pvcrypt scripts and added the wget command to download it. I also added what the contents of that file should look like. Or is there some reson to have it on a logical partion?
So I have to install the boot partition on the internal hard disk which is seen as hda and the root partition on the USB external device sda. The hda disk is only shown if I launch the install process without any attached USB drive. How can the steps above be modified to have the system boot from the internal hard disk, and then load the encrypted file system from the USB thumbdrive?
It should be be possible to do skip the lvm part and directly use encrypted partitions. However, you will have to create two partitions, one for root and one for swap.
You will also have to update the scripts to unlock both partitions at boot. When the partitioning portion of the install.
I wonder if the age of you system is getting in the way. I will think about it and let you know if I come with anything. Today I installed ubuntu 9. After reading your post, I started playing around with partitions, making some additional check that they were all unmounted, and trying with different USB ports… at the end, I relaunched the install process and both drives were magically recognized!
I tried booting with the livecd, and then seeing if I can open the encrypted portion, same error. This has happened to me twice starting from scratch both times. Greetings from Sweden!
I just wanted to say thank you for this guide. It worked like a charm! Much appreciated you took the time to make this.
Hello i have been having a problem , all the procedure until the installation is exactly as above no problems there but when i go in the manual install no partitions are made in the flash drive , i tried with an 8G and a 16G flash drive no luck. And also if i proceed with the installation then during the installation a get a fatal error and the hole procedure stops.
In the end I found running backtrack4 in VirtualBox installed not live disc worked best and returned no errors throughout the process. That is not actually an error. The programs get installed correctly. The update-initramfs runs fine once we have installed Backtrack to the target drive and then chrooted to it. The how-to calls for using all space on the target drive. If you have a large enough drive, say 16 GB or bigger, you could setup a partition that is FAT or NTFS formatted to use with Windows, but you would lose the encryption option for that partition.
The required encryption modules are no in the initrd image on the drive. Usually, redoing the install carefully will take care of this. Make sure you are deleting any partitions on the target drive before you try to create the new ones. Sometimes you have to delete the partitions, write the table to the drive, quite fdisk, reboot and then create the new partitions.
Give it a try and let us know. Thanks a lot for the guide, it was really helpful especially the scripts part which would have been very difficult to figure out alone. If this is an obvious thing please forgive my ignorance i am still getting used to linux.
That is usually indicative of the mistyped UUID or other problem. Just getting a few problems:. Although when manually editing the boot partition in the install process, i get a different window than the one in your screenshot, more.. Will try a full reinstall again, i just dont want to keep repeating the 3 hour wait while filling the partition with random data, or the hour or so wait while installing.
The problem with the update-initramfs command concerns me because it means that things are not getting written correctly to the usb device. The no operating system found could be related to that or to the final step when you select the device to install the boot loader to. Make sure you are picking the correct device. Regarding that, am i meant to select the device sda or the boot partition of the device sda1? The guide shows the device itself, so i chose it, but just to be clear.
Hey thanks for this guide… unfortunately i am getting an error where it finds the UUID I put in but then it says attempting to resume from… with a UUID that is diff than mine.. Is this happening after you have enter your LUKS key or before. Seems my first problem was an error with the bios — it was counting my usb drive as a hard drive, which pushed it down to second priority and so didnt boot. Kevin, the resume msg is happening after i put in the key.. Ok tried again… it says boot from dev blah, blah then my UUID..
That file looks good. I have had several people who, for whatever reason, have had problems with their first install, but starting over has worked. Something to consider.
After enable encryption the BT installer run but close in the 3rd screen Prepare disk space without notice. Hi again, i solved it, i just restarted the tutorial after formatting the drive and it seems to be working fine.
You might try performing the initial partitioning step. Rebooting, installing lvm2 and hashalot and then encrypting the device and creating the logical volumes. Careful reading of the how-to will provide you with all the answers you need, but, in short, you install Backtrack using Unetbootin to one device, boot from it and perform all other actions to the second device.
Again, read all steps very carefully, particularly when partitioning and installing the bootloader. These two steps can cause your system OS to not boot if done incorrectly. You can add a non-admin account if you want just like you indicate. For Backtrack and the uses I have for it, I just run as root. What do I do then?
It looks like you missed the chroot step. Go back to that point in the how-to and repeat all the steps after chrooting. Gave up waiting for root device. Dropping to a shell! You might try the troubleshooting options at the bottom of the post and redoing the apt-get install lvm2 and update-initramfs commands.
Truly excellent write-up and support! We all appreciate the help!! First thanks for this gread tut! At last installation step running install. Will be figuring out with smaller USB, as my 8Gb takes hours to execute dd command, and about 2 hours last time for installation.
In my experience, this often happens when the wrong device is selected for the bootloader to install to. This is the last step in the install. Make sure you select the right boot device.
A full install requires 6. You will not be able to use this method with a smaller USB thumb drive. Double check your partition sizing. It seems like maybe you are not using the entire disk as described in the howto.
Alos, you only have to do the dd step once. I tried it now twice and I dont think that its because of selecting the wrong device… I will install it again now to make shure its the right device!
You need that large of a disk because of the updates that will be installed and the encryption step. You really need it if you use the new method of full disk encryption that is referenced at the very top of the how-to. I will post the results when Ive finished the installation… I found a difference to your installation after choosing the manual part at the top there are also 2 parts of my hard disk. Minor versions can be omitted. The local-top script itself points to the disk UUID so im relatively sure it isnt pointing to the wrong drive and not finding the passphrase, unless this changes with computer i dont have much experience in partitioning although i presume this does not happen.
Help me my system during boot gives me a message: Give up waiting for root device. Dropping to a shell. Try the recovery steps at the end and do the apt-get install portion again. Ive posted the menu. Give up waiting for root device. I am getting the same error as above. I have gone through the recovery steps a few times with no luck.
I have followed the directions three times now and still the same results. I hate to lose…lol. Same problem as Kevin and Source. That allows me to boot from the drive from the shell…. It appears the drive is simply not going through that command or the decrypt process is taking too long and it is timing out?
I booted back into the live environment and went back through the troubleshooting steps. I added these and then ran update-initramfs -u. Thanks for the great install write-up. I just got this working last night on a new 8GB memory stick. The install went smoothly, and I can boot up on the stick, unlock the volume, and log in.
The system, however, is ridiculously slow. As of right now, the system is nearly unusable due to the slow write speeds.
Is it possible you are plugged into a USB 1. The only other thing I can think of is that the stick is faulty. Nice guide. I am however having a little trouble. Then when I get to the install it thinks vg is on my hard drive or something instead of on the usb drive.
Any suggestions would be appreciated. Did you get things working? Can you provide a screen shot or list of the devices that the install. I might be able to guide you with that info. I will keep at it a bit.. I hate when I can not solve a problem… still taking suggestions.
I walked away from it for a couple days and tried again…. These tutes of yours have been my starting point with new BT installs for at least 2 years now. Sadly, though, mine has suddenly b0rked! What would be the correct way to troubleshoot this, anyone? The error seems to relate to the encryption software and how it handles the containers it creates, and their mappings, but to be honest too many components in the mix here for me to figure it out unguided.
The method I used was the TrueCrypt-based article, and kriggins specifically mentions that issues with device names might well cause this to happen when moving from one machien to the other.
Without these programs you will not be able to open the encrypted volume when you boot using the usb drive. After a full day dealing with this on 2 laptops i almost got it! Kevin tnx for all ur help! This is usually one of few things. Somehow the device had gotten mounted.
I have had this happen a couple times. No real explanation for how it happens, but it does. Double check the device name. The how-to uses sdb, but yours may be different. Verify the partition table is correct. Thanks for a great tutorial! So the cryptsetup command will fail until that point. This seems to have resolved well, bypassed the issue. I will offer that most of the problems you mention are not issues all the time, but occur in some cases.
Either way, great help. The first image, Unetbootin. Strange, after folling this guide completely and booting the usb key… I get a black screen with no information on it and no error message. One of you guys know what is wrong?
What I need to set the partition size to 4 GB flash drive? Thank you for your reply. Kevin, First of all, thanks for taking the time and putting together such a detailed tutorial. I was working my way through yesterday, but after the system installation was complete on my usb drive I had to shut down for the day. I would like to thank you for this tutorial. After several attempts, I have finally got Backtrack working on an 8GB Cruzer using it now to post this.
There is a problem in ubuntu 8. It works perfectly if you boot from the live cd and then unlocks. The install does take a long time and I do now recommend using an 8GB drive. Any thoughts? I figured out the problem. I solved the problem by using Nero to burn the bt4final. Yes… lvm2 and hashalot is installed after i chroot the USB drive along with mounting all the correct mounts proc, sys, and devpts.
Hey kriggins, I was just wondering what you think would be better. I have Vista on the first G, was thinking of putting Backtrack on the rest and installing Ubuntu side-by-side with Vista. Do you think I will need to set primary sda3 M, extended sda4 and logical sda5? It is frustrating to know that I am so close to being done, but seemingly so far. Any help is greatly appreciated. When I try to apt-get install hashalot lvm2 after chroot, I get this: Reading package lists… Done Building dependency tree Reading state information… Done The following NEW packages will be installed: hashalot lvm2 0 upgraded, 2 newly installed, 0 to remove and 32 not upgraded.
After this operation, kB of additional disk space will be used. Any idea as to what may be causing this? Thanks for all your help so far. I would never have come this far without your answers to the many questions in the comments. Thanks J. It looks like the initramfs-tools files are not updated correctly.
They are responsible for copying the files you need. I would boot with the troubleshooting steps at the bottom of the how-to and double check all the files you need to change in the initramfs-tools section.
First, Backtrack is based on Ubuntu so you might want to consider just having Vista and Ubuntu. That being said, GRUB can be used as the boot loader. It does require a bit of finagling which is beyond the scope of this how-to. Second, If you want to use encryption then yes, you will have whatever partitions that exist for Vista and then you will need a small primary boot partition and an extended partition.
My only guess is that either the hashalot package is getting corrupted during download, it is corrupted on the update site or there is a problem with your USB drive.
I was installing last weekend and the hashalot file was okay then. I am not familiar with that error. The backtrack-linux. You can stop networking from starting automatically by executing:.
Thanks for your reply! I guess this is one of those problems that are easier to bypass by just starting over, than to spend hours dealing with.
Thanks for your help, non the less. Am trying to set up on a 8Gb usb drive, using acer ferarri and second usb key 2Gb that backtrack4 is running from,. I have run Backtrack without swap successfully before.
The persistent method does so. You have not successfully chrooted your system after the install finishes. This message occurs when you are still operating from the original 2GB booted Backtrack.
Go back to the how-to and carefully read the chroot instructions. Command failed: Can not access device Gave up waiting for root device. Dropping to shell! I have gone through the tutorial twice, and this has happened both times. Everything seemed to go through alright until I tried to reboot, at which point, the above problem came up.
Any ideas? Sean managed to resolve his issue by watching the video. All commands necessary to build the system are in the how-to, but the video might provide some clarity. The problem you are having is usually indicative of the logical volume manager lvm2 not being installed again after chrooting.
Check out the how-to again and pay particular attention to the section after the install. However, the. Specifying ext3 fails with dmesg returning:. EXT4-fs: Update your userspace programs to mount using ext4 EXT4-fs: ext4dev backwards compatibility will go away by 2.
Am creating the bootable encrypted usb drive. I am in no way a Linux person. Starting to learn a little. There were 2 scripts to run. I do not know how to find this file to edit it. I assume once I find it , I copy it to an editor, delete the file in the dir, modify it in the editor, and paste it back to the dir. I have a Question which is more speed-related than anything. Everything seems fine except that it took about 3 hours to do the install copying of files from the CD to the USB drive.
I think it should not take more than 10 to 20 minutes. I did a transfer of the image of BT4 to the FAT32 first partition , and the whole iso took 2 minutes and 50 seconds, so I know my key is OK thats write average of 8. Is it because the partition is encrypted I dont think so , or because its a logical one again, dont think so , so some other factor?? Any ideas are appreciated. If the filesystem is showing as fat32 after you have partitioned and formatted it as ext3, something very strange is going on.
I am not sure where to point you other than you might try booting, deleting all partitions and writing the partition table so the drive is blank, rebooting again and then try partitioning as in the how-to. For whatever reason, it has always taken forever for the install. I think it is a function of the fact that we are writing to an encrypted volume and we are also decompressing a good bit of data during the install. The iso is 1. Oh I had the impression it took about 10 minutes or so from the clock in your video..
Also, with BT3, it was a matter of copying 2 folders, boot and bt, about MB, and we were almost set. I think this time it actually installs itself, plus the factors u mentioned makes it just slower. How long it took for your installation to finish? The OS boots fine, but I get hanging while using it.
I think a faster USB flash with better read and write speeds would be much better option. Hey mate, great work, exact same problem as cryptosond right now. Everything so far has been a charm up to this command. I finished the install, and it all went through fine. So first, thanks for the excellent tutorials.
Which is fine, I changed the root pw using passwd, and it seems ok. I just wanted to make sure this is normal. Also, It seems to be running with a noticeable slowdown compared to the 2GB usb install. Is this normal because of the encryption? Glad you got it working. Encrypting does slow things down a bit. Anyone Kevin? I also rather have a backup I can just put back in case the OS gets corrupt or I lose my key and have another one ready….
It transfers 1. No hickups, no slowdowns. Its a bit pricey but with the speed and storage, its worth it IMO. Everything seems to be working fine until I get to the installation step. You may resume partitioning from the partitioning menu. Did you format the partitions before you started the install? I have seen forgetting to do that step cause problems before.
You can also try to tell the install. See if that gets you past this issue. After trying again, and looking into the problem some more, I believe it may be my flash drive that is giving me the problems.
Great tutorial, thanks! I also have a problem which makes me pull my hair out.. Ik have succesfully created the partitions on my 16 GB Corair GT drive and enabled encryption and mounted the partitions.
No problems there.. Any thoughts what could be wrong? I read something above about the swap partition crippling the flashdrive? I have done this before without a problem and it worked just fine. I just entered in the LUKS passphase successfully. After researching this problem on the Internet, I decided to start all over and use the DD command to erase the whole usb and then I will format it again and start all over.
Hopefully this will correct the problem with pvcreate and I will not have any problems with the other commands to create volumes groups. I will let you know if it works for anyone else that encounters the problem. I think it is a result of blocks left on the disks after I messed up not including the UUID number in the script. My ideas above all flat out failed. I am still getting the same error from my post above, do you have any idea what the problem may be.
Oh, one more thought. However, I do not know how it works and I am researching trying to get a clue as to why it no longer works. Before I crashed the disk, and had to start all over, I had gotten all the way to the end and the pvcreate command worked just find. As well as all the vg commands. What do you suggest? What could possibly make the command no longer work? The bt4 installation is no a cd-r disk and should not be corrupted upon reboot.
Therefore all files should be accurate and working as they were on the first install. The USB seems to be working find when I use it on the windows machine, I have once again reached the point of successfully entering the luks passphrase and attempting to create the volume groups. Hey thanks for the tutorial its ausome! Thanks for the great guide. How to fix that? Do a search for partition recovery tools and use one to get your boot partition straightened out for Windows. Any one know what step i have miss?
Cause i have windows system in the hd and try to boot my backtrack in usb. That restores the original partition configuration and the ability to boot BT4 from the thumb drive.
Once you get this right, you can boot this thumb drive on Mac or PC… either one works great. A truly portable copy of BT4. Thanks Kevin for your help. I did get a warning, not sure if it is related to the problem:. The number of cylinders for this disk is set to There is nothing wrong with that, but this is larger than , and could in certain setups cause problems with: 1 software that runs at boot time e.
I have also tried to make the usb flash drive bootable with UNetbootin, and that works. Probably, been covered in previous comments. The how-to will be updated soon to mention this and also mounting the filesystem as ext2 to disable journaling for the same reason.
I have never come across it. It has to do with the way the install works for the fully encrypted version. Essentially the entire distribution is expanded and copied to the USB drive.
It takes about 6. You can install and have an encrypted volume using the persistence method how-to on this site, but space becomes a real issue as you start up update things.
The install with full encryption does not use the persistence mechanism built into Backtrack. Hello, Great guide! I was able to follow it all the way up to the part where I need to edit the script to point to the encrypted volumes.
Your help with this would be greatly appreciated! Thank you, Eric. First I want to say thank you for your complete and detailty discription how to create an encrypted file system and install backtrack on it. This guide helped me a lot. Have you an idea how I can add the Backtrack boot partition to grub 1 that it works again? I encountered one problem although I think this is to do with using the newer R1 release iso instead of the older pre release one.
Thanks for the info. I just confirmed what you experienced with Backtrack R1. Updating the how-to in a few minutes to require a 16 GB drive. Great guide! I managed to successfully install and boot backtrack 4 on my 16G thumb drive. The only problem is that I followed your guide exactly, and now I get an error saying that my root partition is full.
For all of you who get a warning message during fdisk about GPT structure on the USB thumb drive, there is a easy solution to this problem. Simply open gparted, delete all partitions on the sdb or what ever your drive is, then go to edit partition table and select msdos. Now the warning message is not there anymore and you can follow the guide doing all the steps in of making partitions with fdisk.
As long as you have space in the logical volume, you and use the lvextend command to extend a partition. I followed everything according to plan but when I try to reboot and enter the Luks passphrase I get the following error:. Weird I thought since I know the passphrase is correct. Anyway, i booted through the LiveCd and ran the cryptsetup luksOpen command and was able to unlock it no problem.
So the error must lie somewhere in building the initramfs no? So close after all this time and yet so far. By the way, Andrew and Drew up top. I had the same problem and was able to work around it by booting from the CD and making sure my USB drive was not mounted before running cryptsetup.
If it is just umount it. That is usually an indication that there was a problem when the initrd image was built with update-initramfs. This particular error usually means that the correct encryption modules were not included in the initrd image.
It must contain the lines. BTW — if you are using the R1 version, you may be hitting a space limitation issue on the boot partition. I updated the how-to a couple days ago to increase the boot partition to MB. Kriggens, Thanks for such a quick reply. I mounted the drive and the correct modules are there. Thanks for your continued efforts in keeping the guide clean and up to date. My current problem is only happening with the new R1.
Neither would work, both having identical issues. I tried reinstalling R1 live cd onto my thumb drive, no dice, then I tried doing it through VMware. Neither worked.
Then encrypting, etc, then installing. It would then crash. I did select my correct device name to install the boot loader on. I did this twice with the same result to make sure. I am really running out of ideas here. I could go without encryption, but then I would rather just use the live CD. Any ideas on how to oversome this? Ok, I have figured out the problem. Both drives I was working with had been formatted many times. Silly me, I thought that it being formatted in windows, then partitioned with fdisk would work.
I could have swore that is what I had done in previous installs. Low and behold, ubiquity now recognizes my partitions. What a relief…. Very interesting.
I must admit that I have not verified the encrypted portion yet. I did a quick install with out encryption to check file space. I will probably not be able to get to until this weekend. I will let you know if a I have the problem and b figure out a way around it. Check out comment 58 for some other troubleshooting tips. The person who had that problem actually ended up starting over and had success. Thanks again for your help.
I followed the tips in comment 58 and I have found some things are missing. First some info. My kernel is therefore different than the one in your tips 2. Mine is 2. For some reason when my image gets built xts disappears. Was this a typo or should I have a directory named pre-mount?
The problem was indeed with the xts module missing from the initrd image. I ran into VirtualBox issues this weekend and have just gotten those sorted out.
That is where I do all my testing. I am trying the install now. I will say that I have gotten some comments from folks where things worked fine for both USB installs and disk installs.
Ubiquity had no problem finding the partitions. I will offer that I have had a similar issue before if I did not format the partitions prior to starting the install. Everything else worked fine too. I will pick one up and see what happens. We need to free space , whoever finds big spaceconsuming applications tell us , 16GB are affordable yet! So i have to boot it from usb! I tried another usb flash drive, same problem.
Can you please help me? If you can, i need some details for it. I successfully performed this procedure the first time and could boot backtrack 4 R1 on different machines from the stick-drive successfully. I have a significant concern however: I used a 16G Toshiba TransMemory stick-drive to install Backtrack 4 R1 on, and again it boots successfully. However, I set the root partition to 7.
Any more guidance you can provide will be greatly appreciated! Thanks for the kind words. You have not set the partition table for ever. You can delete the partitions and start over without any problems. However, it should be possible to use the lvextend command to add any unused space to the vg-root logical volume. I have not tried this and it does depend on how you partitioned the disk and defined the volume group.
Easiest is probably to just redo it. Notify me of new posts via email. Home About How to hack Windows from Backtrack 4 R1 24 09 This Super-working article will tell you how can anyone hack or reset a windows password from Backtrack or Ubantu live cd. What you have to do is following the steps: Step1.
If not found download it from the following command sudo apt-get update sudo apt-get install chntpw Step5. Like this: Like Loading Demi nemo : Try a third part windows password recovery tool. Sam : You can make a video please? Sam : ok thankss. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public.
Name required. Blog at WordPress. Follow Following. Sign me up. Already have a WordPress.
0コメント