Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 18 of 18
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,901

    Quote Originally Posted by Segfault View Post
    Why did you need to changeroot? You couldn't log on from console?
    I take it there is a difference between logging from console and chroot?

    When I was in the sytem via chroot, I was able toview the file.
    rm' ing the file did absolutely nothing.
    As when I tried to upgrade, I got the same error about that file.
    I tried to reboot and login again, no change.
    Booted back into live Linux Mint 18. to update this thread.
    Tried the chroot again to post the contents of that file. But then I received a message saying "/mnt does not exist in /etc/fstab"
    Mkdir /mnt received an error of "/mnt already exists"
    Trying to open the file from Linux Mint 18 filemanager failed. It attempted to open it, a progress bar got about 75% across and failed with a permissions error.

    I am beginning to think that the usb environment is to unstable for regular use.
    If you want to learn more about linux take a linux journey
    https://linuxjourney.com/
    Use CODE tags when posting output of commands. Thank you.
    https://www.linuxcounter.net/cert/608410.png

  2. #12
    Linux Guru Segfault's Avatar
    Join Date
    Jun 2008
    Location
    Acadiana
    Posts
    2,185
    Sorry, you lost me. I have no clue what you are doing and why you are doing it. Earlier I was thinking you could not log on from GUI, so I recommended logging on from console. How comes rm does not work on that file? It should give an error if it is unable to perform the action. Are you mixing up live environment with your installed Linux? Did you run the fsck on correct filesystem? I'm not there watching over your shoulder. Bits and pieces of information you are posting do not make much sense to me.

  3. #13
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,901
    After checking your reply I got what you meant about logging in from console.
    Did CTRL-ALT-F7 to bring up command line.
    Logging in as root or doug, I see a quick message that looks like it is successful, to quick to see it. But the part I caught says "last logged in on" and that is it. Back to "login:"

    From the live environment I managed to delete the file that would not let me update. Then when I go to do the upgrade, it gets to the point of preconfiguring packages.Then it fails.

    Code:
    124 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
    Need to get 0 B/138 MB of archives.
    After this operation, 38.4 MB of additional disk space will be used.
    Do you want to continue? [Y/n] y
    Extracting templates from packages: 100%
    Preconfiguring packages ...
    E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or directory)
    dpkg: unrecoverable fatal error, aborting:
     unable to open files list file for package `libfakeroot:amd64': No such device or address
    E: Sub-process /usr/bin/dpkg returned an error code (2)
    Last edited by budman7; 10-30-2016 at 01:55 AM.
    If you want to learn more about linux take a linux journey
    https://linuxjourney.com/
    Use CODE tags when posting output of commands. Thank you.
    https://www.linuxcounter.net/cert/608410.png

  4. $spacer_open
    $spacer_close
  5. #14
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,901
    Quote Originally Posted by Segfault View Post
    Sorry, you lost me. I have no clue what you are doing and why you are doing it. Earlier I was thinking you could not log on from GUI, so I recommended logging on from console. How comes rm does not work on that file? It should give an error if it is unable to perform the action. Are you mixing up live environment with your installed Linux? Did you run the fsck on correct filesystem? I'm not there watching over your shoulder. Bits and pieces of information you are posting do not make much sense to me.
    Back to the beginning.
    I upgraded new Linux Mint 17 system. Next time I tried to login to Linux Mint 17 I received an "Authentication Failed" popup.
    Then I booted into recovery mode. It was readonly. So I mounted it read/write, updated the password. No effect, same Authentication failed popup.
    Then I created a new user, doug1, no effect there either, Authentication failed.
    Did the fsck from recovery mode, got errors, did fsck from Mint 18 live. No errors. Still got Authentication failed on attempt to login.
    Then tried to update/upgrade from chroot. got errors about one of the files. managed to delete said file.
    Still not able to upgrade, updating worked though.
    Logging in from console, as root, doug, doug1 did not work.
    If you want to learn more about linux take a linux journey
    https://linuxjourney.com/
    Use CODE tags when posting output of commands. Thank you.
    https://www.linuxcounter.net/cert/608410.png

  6. #15
    Linux Guru
    Join Date
    Dec 2013
    Posts
    2,747
    one last idea, maybe the partition(s) is/are full (usually they keep back 5%, so if it's got 5% left, it's still full for all intents and purposes)?

    if that doesn't help either, i think you are looking at some sort of corruption, either some crucial files, or filesystem, which might point to the underlying hardware...

  7. #16
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,901
    It is a 16G usb stick, with over 50% free.
    I am not going to spend any more time on this for now. Maybe later I will come back to it.
    I bought a 64G USB3 for $15.
    I am going to try using that.
    If you want to learn more about linux take a linux journey
    https://linuxjourney.com/
    Use CODE tags when posting output of commands. Thank you.
    https://www.linuxcounter.net/cert/608410.png

  8. #17
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,901
    I now believe that there was something wrong with that usb stick, as any distro I tried to install on it failed partway during copying files.
    Bought a new usb stick and that works just fine.
    If you want to learn more about linux take a linux journey
    https://linuxjourney.com/
    Use CODE tags when posting output of commands. Thank you.
    https://www.linuxcounter.net/cert/608410.png

  9. #18
    Linux Guru
    Join Date
    Dec 2013
    Posts
    2,747
    -->
    Quote Originally Posted by budman7 View Post
    I now believe that there was something wrong with that usb stick, as any distro I tried to install on it failed partway during copying files.
    Bought a new usb stick and that works just fine.
    hardware failure is always an easy explanation, but usually the wrong one.
    nevertheless, sometimes hardware failure is the answer, and i agree with your assessment.
    good you got it solved.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •