I am livid, I am ready to throw this f-ing machine into the street and make several passes over it with a freight train.............................!!!!!

I have done init-/bin/bash <ctl>x
I have used knoppix
I have stood on my head and sung Barry White songs to it...
I have threatened torture
I am just about done with this idiotic stupid usless piece of software that will not even allow me to run snapteck package manager to update it.

I hate this it is idiotic that I cannot take control of my own computer and load a frigging update........

Who ever wrote this crap should be taken out and..........

It wont change, I have spent 6 f-ing hours on this....

...and maybe if you provided some details, like what KIND of machine, running what (subject mentions Debian?), what you mean by 'snapteck', and where knoppix comes into this, we might be able to actually help. You say "init-/bin/bash" (???), and what did you actually *DO* in that shell? What did you actually DO with knoppix???

If you just want to rant and rave, there's no point in posting. What are you actually trying to DO, from what desktop environment???

Ok, I have had some time to sleep on it and I'm somewhat less perturbed than I was at 2 or 3 am...

I am working with Debian in a Mate desktop environment, although I can load KDE Cinnamon Gnome and a couple of others, I allowed several to install so I could test the difference.

Using an old Dell PowerEdge 860 with a 160gb HDD and 4G RAM. Synaptic Package Manager is what I meant, Knoppix comes into this because a buddy of mine said that is always his "go-to" Swiss army knife of software to solve any problem.....and I actually DID get "Password Successfully Changed" reply back from the server when I used it to attempt to change the root PW, however upon reboot, Synaptic requested root PW to run updates ect, and I entered the new "Successfully Changed PW" and still got rejected.

So one of the first attempts to change root PW was to "E"dit into the Grub Boot-loader and add init=/bin/bash to the end of the kernel line beginning with Linux...
No Joy....Half a dozen or so lockups on Google in the forums ect. to get this pathway to work yielded more frustrations.

So I attempted to DL Knoppix, which in and of itself was a substantial challenge as every link in the Knoppix page brought me back to the same Knoppix page, like being caught in a trackback loop....again VERY frustrating.....finally after achieving a successful download and burn of Knoppix and untold numbers of searches (because what I was seeing on my screen was not even close to what the tutorial I was following) I finally stumbled (more or less) into an area on my screen that very closely resembled the tutorial and I did the psswd root change, and to my delight it was successful....

Only to be denied again on reboot and launch of Synaptic Package Manager......

I re-attempted the init=/bin/bash from Grub again (if I remember correctly) and here is where I sit at this time:

https://s13.postimg.org/nz2zlvzmv/IMG_4532.jpg

NO JOB CONTROL IN SHELL
is why is not allowing you to do anything becuase that shell has no control for doing jobs, ie changing passwords, that is a new error to me never seen it but google has plenty of posts on this subject.

your prompt root@(none) says something. when it should be showing your domain name

was your system working properly before you decided to try and change the root password?

if yes then, perosonally I'd do a re-install and be done with the head acke of trying to fix everything first just to change it. saves time.

but you also could wait and see if anyone else in here can help you to fix that NO JOB CONTROL IN SHELL error so you can change your password.


[modded moved to top]

I'm getting all you want to do is change the root password?
open up a terminal and use that to do this...

To change the password of your account, use command: passwd.
To change password of any account when login as root, use command: passwd <account name>
To change password of a group, use command: passwd -g <group name>


me already having sudo (root) prevages I was able to change the root password using the old root password to give myself (root) a new and different password (same password in real life because I didnt really want to change mine) I only did this to get something for you to read to see what is going on. You have to have root privages to change passwords.

log in as root, or use sudo if you have the privages set up in your sudoers file.

[command] passwd [user name needing new or old password changed] userName, then just follow the prompts. Being that it is a system side operation you have to have the privages of root to do so. or be logged in as root, or su (superUser)

if the linux OS is not doing what you want and it is you that is trying to change whatever it is then it is not the OS but the proccedure being used that is not the right proccedure being used or the command is not completely correct in order for the changes to take place.


if you have time, me I would just wipe that install by re-installing my OS me personally I'd use a different version of Linux .. but that is me, debian is not that bad of a linux os though. I just no longer use it.

then if all you wanted to do is change the password then go though the steps needed

That screenshot looks like it's not getting anywhere near the Mate desktop environment, or any desktop environment, or even a successful boot. It looks like you messed up the initial install, with the same issue as whatever you originally had.

In the previous thread, someone noticed that the dashes in your machine name may have confused the LVM handler--replacing single dashes with double dashes.

I would strongly recommend you reinstall Debian. This time, don't use LVM, and use a normal alphanumeric machine name with no dashes or other special characters. If you really insist upon having both, you can try that again later.

It's entirely unclear what you have done with Knoppix, but it sounds like you don't really know quite what you're doing with it. As such, there's a good chance that the only password you changes was the password in Knoppix (which gets forgotten upon shutdown anyway, since it stores those changes in RAM rather than a hard drive). Alternatively, even if you did successfully chroot into a suitable environment to change the passwd file on that messed up LVM install, the point is moot since the boot process doesn't seem to get far enough to load up that passwd file anyway.

from the following prompt:
root@(none):/#

I typed:
sudo passwd root

Server replied:
Enter new UNIX password:

I entered:
123

Server replied:
Retype new UNIX password:

I entered:
123

Server replied:
passwd: Authentication token manipulation error
passwd: password unchanged

https://s15.postimg.org/4dm6way8b/IMG_4533.jpg

Tried your second choice answer, and will spare the repetition of the above and just include the screen shot of the failure here:

https://s15.postimg.org/xhaesjmbv/IMG_4534.jpg

Thank you all for your time and attention, I truly appreciate your assistance.
I could just re-install, but would probably end up at the same point, and I'd rather learn something.

Alan

This is a Test Only

Sorry was trying to see if it would attach a signature.....it did not....

NOTE the error message prior to trying to change your password that is what is preventing you from doing so. therefore learn how to fix whatever it is that is causing your OS to give you that error message before proceding to keep trying to change your password.

or
you could just re-install and try it again.

That screenshot is weird. Some distros don't have a root password, therefor you cannot change it. (without extra steps).

root@(none):/# echo $0
root@(none):/# id
root@(none):/# lsb_release -a

To set a root password in ubuntu (which breaks ubuntu's security model).

root@(none):/# passwd -d root
root@(none):/# passwd root

BUT... If you chroot into it from another distro, you are root at the chroot. At which point you can add users and change their login credentials without breaking said distro. Plus the other admin steps to enable sudo for said user so you don't need root (directly) and don't break the distros security model.

Although I have no idea if this is your issue, or if you're even in a linux environment and not same bash shell for windows. By all outward appearances that environment didn't even set the hostname, so is likely not properly installed at a minimum. Or maybe / is read-only so you can't really change anything anyway.

root@(none):/# mount | grep " / "

No it's not. He booted by passing to the bootloader. I'm willing to take the educated guess that means that the root fs is still mounted read only because (s)he hasn't indicated otherwise.

"OHPRG Project Director", check the output of mount as Shadow suggested. If it says "ro", the root fs is mounted ready only and that's why you're getting the error.

At the shell prompt:

then try changing the password again. Any password, not just root can be done in this manner. That'll likely fix your problem. Then you can go back to singing Barry White. Me personally, I sing Chris Cornell to my laptop, scares the thing into doing what I want.

1 members found this post helpful.

goumba is exactly correct! (I built a similar Vbox [but no GUI] to follow-along &learn)

sudo isn't needed (you're already 'root'; sudo wants user's [not root's!] password)

Hopefully, after the `passwd` succeeds (and you press reset to reboot), all will be ok.

Even I (an OLD long-ago Unix SysAdmin) still get lost, overlooking some 'basic' concept,
so I'm glad to hear you recovered from the head-smashing that this 'puzzle-gifter' [Linux] provided.
Also, ack. '1st-responder' for not seeming upset (analogously)!

Best wishes in all this (I'm guessing OHPRG is an after-hours volunteer task)

I had posted about this in another thread and an answer did come to light....

I named my box TAPS-0-GRN, as I have 2 others for similar purposes timing and scoring of rally races
TAPS-1-RED & TAPS-2-BLU.......RED/GRN/BLU......RGB.....GET IT....Graphic artist, Computer nerd, Racecar fan...evil genius (at times)
I share the prize winning theroy with you here as well....


Originally Posted by Jjanel View Post
oh wow: *maybe* your hostname of TAPS-0-GRN 'confused' the LVM install!
(note in 4th img that something turned the single hyphens into DOUBLE hyphens!)
(I'm not sure whether this was ever fixed.)

What 'distro' are you using now?
(I had a thought: pick the distro used in: whatever instruction/guide you will use for your timeserver)

p.s. I vaguely remember running into the same root-can't-login-after-install!
It *might* have been some distro's /etc/securetty 'feature' [linux puzzle-gift]
Or a @ or # (or ...) special char in the password confused something
Well this sure would explain a lot...... <sigh>.......Which kinda bums me out because I was going to make this PowerEdge the Master which always stayed at home base and TAPS-1-RED & TAPS-2-BLU were going to be the actual on course timing devices for our races, RED and BLU are a couple of Identical (build by same company, same line, same guy, same day) ilbiet fairly cheap desktop tower computers running Mint.....(No double Hyphens there)....so the theroy was that any inherient latentency in the timing of each once synced with the master at the beginning and and of the race day would be minimal.....I will re read the tutorial about the time server/service I beleive it is running free BSD. So will take a look at a reload for sure maybe mint is fine for this one too but as it is a GENUINE server and not a fake wanna be server (even as old as it is) that id treat myself to a wiz bang interface, (with my fat finger typing and horrible spelling and syntax....GUI is the way to go.....LOL.....

Thanks folks for all your help and assistance, any thoughts on what to load on it next......???

Alan






The method lvm uses for naming is:

Use volumegroupname-volumename

if the names have dashes in them, double up the dashes so that the only
place with a single dash is the one seperating the volumegroupname from
the volumename.

I think they do this to make sure hey stay unique.

After all if you had a volume group named 'a-b' with a volume named 'c'
and a nother volume group named 'a' with a volume named 'b-c' you would
end up with:

a-b-c for both of them if you didn't do the doubling thing. Instead you get get:

a--b-c (VG a-b with LV c)
a-b--c (VG A with LV b-c)

So the installer must double the dash in any volumegroup name or
volumename when generating the name in /dev/mapper to expect.

Glad you got it sorted. If the hyphen is not a suitable delimiter for your purposes, then simply find one that is, but keeping the VG name to your intent. For most purposes, once you set the VG name, you're really not going to need to touch it again unless you add more hard disks, storage, whatever and need to add them to the group.

TAPS-0-GRN TAPS.0.GRN maybe not confuse OS whereas the - (hyphenate) did .. but I'd have to be look up to be sure.