Call to lnusertemp failed

[Iphtashu Fitz]

I have a MacBook pro that I've been running the BackTrack live CD on without any problems. I just downloaded BackTrack 3 final and tried booting it up. I used the VESA graphics mode as I have in the past, but this time when X starts up it eventually displays the following message:

"Call to lnusertemp failed (temporary directories full?). Check your installation."

I dropped to a command shell and verified that there's plenty of available space (1.8 gb for /). /tmp and /var/tmp are both world read/writable. Any suggestions as to why this might be happening? I'm going to do some more digging on my own but I'm not an expert with X or KDE so any suggestions would be appreciated.

[Iphtashu Fitz]

To follow up to my own post, it turns out that the live CD apparently is not creating the /root directory, which is the home directory of the root user. /root is listed as the home directory for the root account in /etc/passwd, but since it doesn't exist that's why lnusertemp fails. If you manually create the /root directory and restart X then KDE will start up, but with just a default desktop, not all the BT3 customizations...

[hcpirat]

i have an asus g1 and the same problem.
when i create a root dir and start it with startx the default desktop loads.
any solutions?

[Brlink]

I have the same problem with my Gigabyte ga-m57-sli-s4.

[Brlink]

I burned the image to another cd and it seems to be working fine now. Could have been a bad burn the first time, even though it passed the data check after it finished.

[hcpirat]

okay, i will try other cd.
did you burn the image with nero?
which method did you choose: track-at-once or disc-at-once?

thank you!

[Iphtashu Fitz]

It took me three downloads but I finally got one that worked. I burned it directly on my MacBook Pro so I wasn't using anything like Nero. I forgot to check the verify option the first time I burned a cd. The second download failed verification when I burned it, so I downloaded a third time and that one worked. Oddly enough I did check the md5sum of each download and they all reported the same as the posted hash...

[=Tron=]

It took me three downloads but I finally got one that worked. I burned it directly on my MacBook Pro so I wasn't using anything like Nero. I forgot to check the verify option the first time I burned a cd. The second download failed verification when I burned it, so I downloaded a third time and that one worked. Oddly enough I did check the md5sum of each download and they all reported the same as the posted hash...

In case the MD5 checksum did check out there really was no need to re-download the file each time. Most likely you were burning the CD at a too high speed which caused the disc to become corrupt during the writing process. A low writing speed at 1-2x is usually recommended.

[streaker69]

In case the MD5 checksum did check out there really was no need to re-download the file each time. Most likely you were burning the CD at a too high speed which caused the disc to become corrupt during the writing process. A low writing speed at 1-2x is usually recommended.

Just for the sake of my curiosity. Why does it seem BT is so prone to corruption under fast burns? I've downloaded hundreds of ISO's over the years, and I've never had an issue burning a single one at the highest speeds possible of the day. Including when I did BT2 (burned at 48x on a beat up drive on my laptop).

I'm just wondering if anyone has an idea why BT seems so 'unstable'?

[Apollopimp]

the only time i have had problems burning to disc was with bt2 when it had to be burned slow or the root and toor password would not work other than that ive never had a problem with the discs not working

[archangel.amael]

Just for the sake of my curiosity. Why does it seem BT is so prone to corruption under fast burns? I've downloaded hundreds of ISO's over the years, and I've never had an issue burning a single one at the highest speeds possible of the day. Including when I did BT2 (burned at 48x on a beat up drive on my laptop).

I'm just wondering if anyone has an idea why BT seems so 'unstable'?

I wondered the same thing, then I figured it fell in line with the same sort of questions like "why is water wet?". So I left it alone, until now. :D
With music or movies I could see that a fast burn would maybe cause some sort of "glitch" that would be imperceptible. Maybe it is some sort of secret muts uses to deter n00bs. :D

[streaker69]

I wondered the same thing, then I figured it fell in line with the same sort of questions like "why is water wet?". So I left it alone, until now. :D
With music or movies I could see that a fast burn would maybe cause some sort of "glitch" that would be imperceptible. Maybe it is some sort of secret muts uses to deter n00bs. :D

Well there's an answer for that.

"Purple, cause icecream don't have bones"

[Barry]

Well there's an answer for that.

"Purple, cause icecream don't have bones"

Where the hell do you come up with this stuff?? :D

[archangel.amael]

Where the hell do you come up with this stuff?? :D

That's the Amish for ya, always talking about ice cream and what not.

On another note I did put that into google and the first hit back was someone with that as their name or whatever.

[streaker69]

Where the hell do you come up with this stuff?? :D

It goes right along with "how many pancakes does it take to shingle a doghouse?"

[archangel.amael]

It goes right along with "how many pancakes does it take to shingle a doghouse?"

23, but only if your wire canoe has no wheels (http://wiki.answers.com/Q/How_many_pancakes_does_it_take_to_shingle_a_dog_ho use) :D

[theprez98]

Just for the sake of my curiosity. Why does it seem BT is so prone to corruption under fast burns? I've downloaded hundreds of ISO's over the years, and I've never had an issue burning a single one at the highest speeds possible of the day. Including when I did BT2 (burned at 48x on a beat up drive on my laptop).

I'm just wondering if anyone has an idea why BT seems so 'unstable'?
I don't know that there is even a good answer for this. I myself have never had any problems, at any speed.

[=Tron=]

I don't know that there is even a good answer for this. I myself have never had any problems, at any speed.

Nor have I personally. I have always burned all my CDs/DVDs at full speed and usually on pretty cheap media as well. Nevertheless, I keep hearing about unreadable disc errors etc. as soon as someone dares to burn a disc at more than 3x speed :)

[b0ggy]

I'm having the same error msg with booting with flux. With the other options like kde, the X Server doesnt even start up!!. The backtrack team should perhaps verify the data integrity of backtrack 3 image.

[archangel.amael]

I'm having the same error msg with booting with flux. With the other options like kde, the X Server doesnt even start up!!. The backtrack team should perhaps verify the data integrity of backtrack 3 image.

If you are having a problem then a post about that problem to include what you are trying to do and what has worked and what has failed is much better than posting that the dev team needs to "verify the data integrity of backtrack 3" because on six of my computers out of the eight that I have tried it on works. Hundreds of other users have had little to no problems.
Having said that there is always the possibility that with any software of any type there will be problems. However the Dev team cannot test every single piece of computer equipment there is. If you are unhappy with a free distro then feel free to use something else.

Please do not feel free to post some sort of ego boast but rather take the time instead to post what the exact problems you are having and cut and paste or type verbatim the error code/s that you may receive and we may be able to help you.
:)

[b0ggy]

Hi,
I'm not saying that the dev team test the distro on every single hardware, I'm saying that they should maybe verify the distro to see if it is intact before releasing it, so far NOTHING has worked properly on my HP DV9000 notebook (Intel 965M Express)

Backtrack 3 beta worked on my notebook with no problems whatsoever, so I couldn't really see why the final version wouldn't work. Anyway, what i noticed from the images I downloaded is that (mind you i downloaded twice from two different mirrors) the 4 cds i've burnt, all of them fail to insert /pentest.lzm module upon initialization. So anyway, by starting KDE, i get the error msg:

Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3) server error.

So I proceeded to run xconfig, that yielded me another error upon initializing x server: Call to lnusertemp failed

[archangel.amael]

Hi,
I'm not saying that the dev team test the distro on every single hardware, I'm saying that they should maybe verify the distro to see if it is intact before releasing it, so far NOTHING has worked properly on my HP DV9000 notebook (Intel 965M Express)
Again this is not the a fault of the dev team it works on lots of other computers and again there is no way to verify that it will work on all computers out there.
But I digress I will not argue this point any more.
As for you problem see below

Anyway, what i noticed from the images I downloaded is that (mind you i downloaded twice from two different mirrors) the 4 cds i've burnt, all of them fail to insert /pentest.lzm module upon initialization. So anyway, by starting KDE, i get the error msg:
Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3) server error.
So I proceeded to run xconfig, that yielded me another error upon initializing x server: Call to lnusertemp failed


It does not matter that you downloaded the software 1 time or 1500 times
What matters is that you follow the advice posted in the forums about downloading. Shown here (http://forums.remote-exploit.org/showthread.php?t=9618).
You need to check the md5sum and it might not hurt to check the sha1sum as well.
You must also ensure that you are not using some sort of download manager.
If you have a shoddy connection to the internet (dial up) you may also have problems with packet loss or whatever. But the md5sum should tell you this. Check that thread for more info.
Once you meet the criteria above then we can move on.
I took your error message about the "call to inusertemp fail" and put that into google and one of the first hits brought me this page (http://www.pclinuxos.com/index.php?option=com_smf&Itemid=26&topic=23065.0;wap2) that seems to have the same problem and it has some sort of solution.
Read it and then try to apply the same thing to your case and see what happens. If it works then great if not post back what happens and lets see if we can find another solution.
It might be as simple as re-downloading and then it will all work out.
Due note that instructions seem simple to me but they may be complicated for you. If you have problems then take a minute to google a bit about what is being referenced.
:)

[b0ggy]

yes the md5sum was consistent and I appreciate the link you posted but it did not fix my problem as it is kinda of a different error.

[mcai8rw2]

okay, i will try other cd.
did you burn the image with nero?
which method did you choose: track-at-once or disc-at-once?

thank you!


I have downloaded and slowly burnt the iso five times now... two failed the MD5 check... three were burnt unsuccessfully using the DISC-AT-ONCE option in Nero.

I tried burning a good image with TRACK-AT-ONCE instead. This works. Although I am still getting the "Call To LNUSERTEMP Failed" error.

Thanks

[archangel.amael]

I have downloaded and slowly burnt the iso five times now... two failed the MD5 check... three were burnt unsuccessfully using the DISC-AT-ONCE option in Nero.

I tried burning a good image with TRACK-AT-ONCE instead. This works. Although I am still getting the "Call To LNUSERTEMP Failed" error.

Thanks

Did you check the md5sum right after the download?
Do not bother to burn the cd and then check it.
Download, Check md5sum, Then burn it.

[Thasaidon]

I'm using an old HP Pavilion laptop, with an ATI graphics card.
The "regular" KDE GUI won't run with this hardware, so I normally use the VESA option.

However, I encounter the same problem with the lnusertemp.
Every cd I've ever burned with my writer has never had any problems,
so burning Backtrack3 on 1x or 2x speeds seems unlogical.
Also, most burners don't even give you the option to burn on 1x or 2x.
(mine has a minimun of 8x)

I tried several downloads, and even burning on another system with another cd burner, but without result. Even burning the cd on the laptop I'm running BT3 on doesn't do the trick.
Each time the download shows a correct md5 checksum and after each burn the verify gives an ok too. But I still have this problem.

As a sidenote, Ubuntu 8.04 worked perfectly from live cd and is now running just fine on the same laptop from harddisk.
All other live cd's I've tried on this system also had no problems (except for the ATI vid card that is).

So if there is any solution to this problem, I'd love to know

Thasaidon
*allready spent 6 cd's on bt3, but it's worth it :D *


***edit***
I also tried a few of the cd's on another Dell laptop, but with the same result...

[mcai8rw2]

Did you check the md5sum right after the download?
Do not bother to burn the cd and then check it.
Download, Check md5sum, Then burn it.

Thank you for Replying archangel... yes, i did check the md5 AND the SHA1 hashes after having downloaded. Both checked out ok. Tried again, this afternoon; but still getting the same issues.

[JibberingJ]

I am having the same problem. I downloaded the BT3 Final ISO and checked both the MD5 and SHA1 checksums, which were both good. My first 2 attempts to burn the CD I did with Nero at max speed, but failed data verification. So I tried using PowerISO at x4 speed and did not recieve any errors, but when I tried to boot the CD it failed to load the /pentest.lmz section and continued booting. Everything thing else went well until /startx when I received the error:

"Call to lnusertemp failed (temporary directories full?). Check your installation."

There doesn't seem to be any answer/solutions to this problem yet other than "Check your MD5/SHA1 checksums" and "Burn at a slower speed", but if anyone who has had this problem has any more tips or tricks, they would be very much appreciated.

// I've tried re-downloading and rechecking checksums 4 times and probably // gone through 15+ CD's