How to Backtrack 3 Fix – /dev/hda* not cleanly unmounted, check forced

/dev/hda1 was not cleanly unmounted, check forced

I had this problem after installing BT3. Every time I booted into BT3, I was faced with a forced check and then a second reboot. So off I went to and came across THIS POST about the issue.

This is how I fixed the problem:
Become root:

su + password

Edit rc.6 with nano:

nano /etc/rc.d/rc.6

Scroll down to where it says:

# Kill all processes.
# INIT is supposed to handle this entirely now, but this didn’t always
# work correctly without this second pass at killing off the processes.
# Since INIT already notified the user that processes were being killed,
# we’ll avoid echoing this info this time around.
#TM: we need fuse-based filesystem to be alive (if mounted from #initrd).
#if [ ! “$1” = “fast” ]; then # shutdown did not already kill all processes
# /sbin/killall5 -15
# /bin/sleep 5
# /sbin/killall5 -9

And uncomment the lines from if to fi (delete the #’s)

It should now look like this:

# Kill all processes.
# INIT is supposed to handle this entirely now, but this didn’t always
# work correctly without this second pass at killing off the processes.
# Since INIT already notified the user that processes were being killed,
# we’ll avoid echoing this info this time around.
#TM: we need fuse-based filesystem to be alive (if mounted from initrd).
if [ ! “$1” = “fast” ]; then # shutdown did not already kill all processes
/sbin/killall5 -15
/bin/sleep 5
/sbin/killall5 -9

Reboot, no more forced fsck, cake!

Thanks to _JMF_ at remote-exploit forums.


How to Add Backtrack 3 to Existing Grub

Dual-Boot Backtrack 3
Well, I have Backtrack 3 installed, and as you know, it uses Lilo, which to be honest I’m not all that keen on.

Using Grub from another distro
I reinstalled Dreamlinux 3.5 and chose “Install Grub to MBR”. So, back to Grub, but now I have to add Backtrack 3 which doesn’t have the initrd file in the /boot directory.

Adding Backtrack 3 to Menu List
No problem, just add these lines where “hda1” is your Backtrack partition:

title Backtrack 3 Desktop
rootnoverify (hd0,0)
kernel /boot/vmlinuz vga=791 root=/dev/hda1 ro autoexec=xconf;kdm

title Backtrack 3 Console
rootnoverify (hd0,0)
kernel /boot/vmlinuz vga=791 root=/dev/hda1 ro

Now reboot and you should see those entries, and you should be able to boot into Backtrack 3 from Grub.

*note* Grub partition numbers
Remember that the Grub partition number will always be one less than the actual partition.
For example
hda1 is (hd0,0)
0 for the first harddrive, 0 as well for the first partition
hda2 would be (hd0,1)
hda3 would be (hd0,2) etc etc, always one number less.

What if you have a second harddrive?
hdb1 would be (hd1,0)
hdb2 would be (hd1,1) etc, etc, now the harddrives go up as well as the partitions.

There you go, easy.

How to Fix Backtrack 3 Slapt-Get package installer

The installed version of Backtrack 3 is missing some files which are needed to use slapt-get and the gslapt gui front-end package managers.

I had to go looking for the files but you can find them here:(right click “save as”)
1. gnupg-1.4.7-i486-1.tgz
2. gpgme-1.1.4-i486-1.tgz
3. libassuan-1.0.1-i486-1.tgz

Once they have all been downloaded to your home directory, issue these commands to install each package one by one.

installpkg gnupg-1.4.7-i486-1.tgz

installpkg gpgme-1.1.4-i486-1.tgz

installpkg libassuan-1.0.1-i486-1.tgz

Once you have installed all of them you should be able to use slapt-get, so start by updating the package cache and then upgrade the system:

slapt-get --update

slapt-get --upgrade

You are now ready to install whatever you need from the repos. I’ll talk about the different repositories in another post. Poople who are accustomed to Debian’s 18,000 packages seem to believe that Slackware doesn’t have access to all those lovely applications. Wrong! There are are loads of repos and Slackware package builds of practically every major/known software applications, including Desktop Environments. But i’ll save that for later.

How to Install Backtrack 3

If you have been using the live version, such as I have, you may have decided that you would like to keep Backtrack 3 as a permanent install. Since Batrack 4 is now Ubuntu based, you may have decided that you would prefer to continue running the Slackware based BT3.

You will also have noticed that Backtrack 3 has no graphical installer included on the final iso.

1. Download the Backtrack 3 installer. As BT has now gone Ubuntu, I will be hosting a copy of the BT3 installer HERE on LxH.

2. If you haven’t created a partition for your newly installed BT3, do it now. I used Qtparted on the BT3 live cd, and chose a standard Ext3 partition.

3. Next I mounted that new destination partition (hda1) in the Backtrack /mount directory:

mount /dev/hda1 /mnt/hda1

4. Next up I ran the installer (which was in the “root” directory), by opening Konqueror and double-clicking the installer.

This is what the installer looks like:
The Backtrack 3 Graphical Installer

So, I chose the /mnt/hda1 partition to install to, the REAL install, and didn’t choose Restore original Lilo to MBR. Basically as this laptop had Grub and a couple of other distros on it. I decided to give lilo a try, and then just add my other distros to Lilo (That will be another Howto).

5. That’s it, click INSTALL, go and make a coffee, and it should be done when you get back.
*Note* Most installers will appear to halt for a long time while transferring the /usr files (Unix System Resources), Dreamlinux does this as well. Don’t panic, just be patient, the /usr directory is like 90% of the distro so there is a lot of stuff to copy to the harddrive.

6. Reboot, and hey presto! You’ve got an installed version of Backtrack 3.

Backtrack 3 (Slackware) and Staying

Whoppix, Whax and Backtrack
Well, as well as using Dreamlinux and a few other distros, one live cd/pen-drive I always carry around is Backtrack. I have always messed with networks as a little hobby ever since I started using Linux, especially after the advent of wireless. There are a load of distros that provided the tools to analyze network traffic, security etc.

Of my favourites were Whoppix/Whax, Grml (Debian), and then with the merger of Auditor and Whax – Backtrack.

Using Slackware
As a mainly Debian/Arch user, the appeal for me was that Backtrack was Slackware or Slax. There was a bit of a learning curve doing things the “Slackware Way” but it always felt robust and fast even running as a Live cd. I’m not a Kde fan so I always used the Fluxbox version.

Backtrack goes Ubuntu
Recently after hearing the news that Backtrack 4 will be Ubuntu based, I decided to install Backtrack 3 on my main laptop, as sadly, it will be my last download and first install of this remarkable distro. I’m not sure why they changed to Ubuntu, but to go from one of the fathers of Linux, skip Debian and go straight for a newbie derivative, especially a distro which suffers from a lot of breakage, is madness in my eyes.

Backtrack Forums
The Backtrack forums have always advocated learning, and doing things the hard way to find out the where, what, why and how of analysis, hacking and cracking. The Ubuntu forums have always been full of newbies looking for immediate point and click results with no intention of learning or giving back to the community. Well, this is a high percentage of Ubuntu users anyway. There are some knowledgeable guys there, but the “takers” far outweigh them.
Backtrack forums will now be flooded with this type of user, which will be a shame. Just wannabe crackers asking basic questions about how to point and click to crack wpa. I can see it now.

Forum Lurker
As a forum Admin myself, I always use Google then the forum search of any distro before posting, and as it happens, both have always served me well with Backtrack and Slackware. I signed up yesterday to ask “Why Ubuntu?”. Then I decided that it doesn’t matter, and the devs obviously have a good reason for their choice. I just hope it’s for the right reasons and not just publicity.

Sticking with Slackware
I have Backtrack 3 (Slackware 12 Upgrade) installed. I get all my updates from the Slackware repos, all the Backtrack-centric scripts do what I need them to do, and i’ll manually install any updates.
I’m not sure what the Backtrack masses feel about the swap, i for one won’t be using HackBuntu 4.