LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-12-2017, 05:02 PM   #1
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 239
Blog Entries: 15

Rep: Reputation: 24
Upgraded to -current, cannot boot


Hi --

I decided to upgrade to --current. Did so without difficulties, ran lilo as suggested at the end of the process. Rebooted.

Alas, I'm getting the same "Read-only file system" errors reported in this SOLVED thread:

http://www.linuxquestions.org/questi...ed-4175611523/

There are also lots of complaints in the boot messages about "/lib64/libc.so.6: version 'GLIBC_2.25' not found (required by /lib64/libblkid.so.1)"
<-- that's one example - the same message pops up for many libraries. Perhaps slackpkg didn't update glibc correctly? I'm stabbing in the dark here.

Unfortunately, because I'm too boneheaded to have backed things up, I can't restore as the OP in that previous post did.

I don't know whether the fact that I am experiencing the same problem indicates anything whatsoever. Am looking through the output of dmesg, but not seeing anything suspect yet.

I've downloaded Slacko as one poster to that prior thread suggested, but am not sure what to look for (one person suggested deleting everything in /tmp ... I suppose that is a good first thing to try).

Suggestions are welcome. I'm looking through the SOLVED post and trying the suggestions there. Some are moot due to the filesystem being read-only

Thanks,

Glenn
 
Old 08-12-2017, 06:19 PM   #2
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 239
Blog Entries: 15

Original Poster
Rep: Reputation: 24
Using Slacko, I emptied out /tmp and cleared some lock files from /var/log. No happiness booting. I am downloading the Slackware DVD image and will use that to attempt a repair.
 
Old 08-12-2017, 07:59 PM   #3
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 239
Blog Entries: 15

Original Poster
Rep: Reputation: 24
There was no actual solution. I simply reinstalled stable. Unsure whether I want to try another upgrade to --current.
 
Old 08-12-2017, 08:48 PM   #4
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, and whatever VMs I happen to be playing with
Posts: 12,359
Blog Entries: 16

Rep: Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146
I offer this as a shot in the dark.

I once made this mistake in upgrading a Slackware install:

I ran slackpkg upgrade-all before slackpkg install-new. A crucial new package was not in place when I ran upgrade-all and I bricked my system.

That's when I learned how to boot to a live CD and rescue my install.
 
1 members found this post helpful.
Old 08-12-2017, 09:07 PM   #5
hitest
LQ Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 5,138

Rep: Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112
Quote:
Originally Posted by frankbell View Post
I offer this as a shot in the dark.

I once made this mistake in upgrading a Slackware install:

I ran slackpkg upgrade-all before slackpkg install-new.
Indeed. There are a lot of new packages that have been introduced in -current since 14.2's release.
I also run slackpkg clean-system after upgrade-all as there will be obsolete packages to remove.
 
Old 08-12-2017, 10:11 PM   #6
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, and whatever VMs I happen to be playing with
Posts: 12,359
Blog Entries: 16

Rep: Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146Reputation: 3146
In case it helps anyone, here is my Slackware update script, for which I do not claim authorship, as I learned it from a member of my LUG. It should be run as root.

Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
It should not be run unattended, as it requires interaction from root.

Because I have configured my blacklist file, when it asks what I want to do with new configuration files, I always answer "P" for "prompt," so I can decline overwrites of files I have configured to differ from default.

Last edited by frankbell; 08-12-2017 at 10:14 PM.
 
1 members found this post helpful.
Old 08-12-2017, 11:31 PM   #7
hitest
LQ Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 5,138

Rep: Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112Reputation: 1112
Quote:
Originally Posted by frankbell View Post
In case it helps anyone, here is my Slackware update script, for which I do not claim authorship, as I learned it from a member of my LUG. It should be run as root.

Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
The very first time I run slackpkg I run slackpkg update gpg, then the four commands that you mentioned. That command adds Slackware's GPG key.
 
Old 08-13-2017, 10:23 AM   #8
TarFile
Member
 
Registered: Mar 2003
Posts: 283

Rep: Reputation: 23
If you are running a mulitlib system you can get that error if you don't make sure to upgrade the mulitlib packages before you reboot. You need the multilib compatible version of GLIB to match the current version. Not sure if that was your problem.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
I just upgraded my Slackware current box .... navigium Slackware 3 05-27-2016 09:33 AM
Upgraded Slackware 64 current to 3.14.4 kernel panic will not boot wvragga Slackware 12 06-23-2014 11:21 PM
[SOLVED] Can't boot into -current partition after slackpkg upgrade-all, after kernel upgraded gabytf Slackware 7 08-12-2012 10:42 AM
[SOLVED] Upgraded to current - have a grub question Robert.Thompson Slackware 4 02-09-2011 09:56 AM
[current] rfkill upgraded? conraid Slackware 3 01-22-2011 12:02 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration