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-07-2017, 08:07 PM   #1
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Rep: Reputation: 93
Cannot boot, permission denied


I have a big problem. I rebooted my Slackware64 14.1 server and it comes up with the root file system as read only and won't boot. Most of the messages scroll off the screen, but I can see messages like:
Code:
/etc/rc.d/rc.S: line 372: /sbin/mount: permission denied
touch: cannot touch '/var/run/utmp': Read-only file system
chmod: changing permissions of '/etc/random-seed': Read-only file system.
:
/usr/sbin/klogd -c 3 -x
It hangs for a several minutes at that "klogd" message, then continues trying to boot, with lots of "Read-only file system" failures. Eventually, I get a log-in prompt (with screen text in the large font), but I cannot enter any login id -- no keyboard response.

The boot "drive" is a mdadm RAID-1 /dev/md0 consisting of 2 drives, /dev/sda and /dev/sdb. There were no RAID errors reported last time I checked /proc/mdstat a couple of days ago.

I did boot from DVD and did fsck on /dev/md0 -- no errors.

What is wrong and what can I do to fix this?

More Info ...

At the beginning of the boot, I get messages like:
Code:
ata5: link is slow to respond, please be patient (read=0)
ata5: COMRESET failed (errorno=-16)
These messages are repeated several times.

Last edited by mfoley; 08-07-2017 at 08:22 PM. Reason: More Info
 
Old 08-07-2017, 08:19 PM   #2
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,862

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
You can probably find more information about the problem in /var/log/kern.log. Rather than start reading at the beginning of the log I suggest that you use the tail command to start reading at the end of the log.

--------------------
Steve Stites
 
Old 08-07-2017, 09:53 PM   #3
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Original Poster
Rep: Reputation: 93
Quote:
Originally Posted by jailbait View Post
You can probably find more information about the problem in /var/log/kern.log. Rather than start reading at the beginning of the log I suggest that you use the tail command to start reading at the end of the log.

--------------------
Steve Stites
The problem with this idea is that the filesystem is read-only so I don't think I'm getting a /var/log/kern.log, right?
 
Old 08-07-2017, 10:09 PM   #4
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,147
Blog Entries: 3

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
Look for a stale socket file in /tmp . seems it may be stopping you from creating a new one. give it a shot. clean /tmp out even the ".*" files reboot it.
 
Old 08-07-2017, 10:39 PM   #5
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Original Poster
Rep: Reputation: 93
jailbait: As I suspected, there is nothing logged in messages or syslog since I initially rebooted. There is not /var/log/kern.log

Quote:
Originally Posted by Drakeo View Post
Look for a stale socket file in /tmp . seems it may be stopping you from creating a new one. give it a shot. clean /tmp out even the ".*" files reboot it.
Worth a try, but didn't work. Same error and non-boot.

Interestingly, when I boot from the installation DVD and mount /dev/md0, I can read/write/delete files on that drive to my heart's content.
 
Old 08-07-2017, 10:55 PM   #6
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,147
Blog Entries: 3

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
seems like your not getting past init 1 that is only ro. look at your lilo or grub command at start up.
install disk uses the disk kernel and boot instruction. you update the the kernel 3.10.107 thats the new kernel strange.
june 29th 2017 http://mirrors.kernel.org/slackware/.../ChangeLog.txt

Last edited by Drakeo; 08-07-2017 at 11:11 PM. Reason: chanh\ge log
 
Old 08-07-2017, 11:37 PM   #7
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Original Poster
Rep: Reputation: 93
Drako: what are you suggesting when you say, "look at your lilo or grub command"? What should I look for? It appears unchanged to me.
 
Old 08-07-2017, 11:48 PM   #8
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,147
Blog Entries: 3

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
I am saying you upgraded your system you may not be loading the modules do to if you did a upgrade-all and did not run lilo if using lilo then you have this problem. if using grub and you use an initrd.gz it is causing issues with the module to load. when you boot from the disk you are booting the vmlinuz-huge with all the modules that allow you to to run the system.
Did you upgrade the kernel forget to run lilo ?slackpkg upgrade-all would do that.
What is your boot program Lilo or grub.

Last edited by Drakeo; 08-07-2017 at 11:59 PM.
 
Old 08-08-2017, 12:41 AM   #9
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Original Poster
Rep: Reputation: 93
boot program is lilo. I did upgrade the system July 1st and did run lilo.

Interesting --- I restored backup to completely new hardware and got the same problem! Will now try restoring from an older version, before the upgrade.
 
Old 08-08-2017, 01:25 AM   #10
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,558

Rep: Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495
Quote:
Originally Posted by mfoley View Post
More Info ...

At the beginning of the boot, I get messages like:
Code:
ata5: link is slow to respond, please be patient (read=0)
ata5: COMRESET failed (errorno=-16)
These messages are repeated several times.
I have had that with a dying drive. First thing to do: a backup of all that's on it that you care about.

I mean a full backup from scratch, not an update of an existing one.

Last edited by Didier Spaier; 08-08-2017 at 01:29 AM.
 
Old 08-08-2017, 02:29 AM   #11
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,406

Rep: Reputation: 1291Reputation: 1291Reputation: 1291Reputation: 1291Reputation: 1291Reputation: 1291Reputation: 1291Reputation: 1291Reputation: 1291
After you have made sure your data is safe you can use the Install Disk Boot Prompt to boot whatever kernel you prefer or want to test and ro or rw as you wish. Love that little lifesaver.
 
Old 08-08-2017, 12:11 PM   #12
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Original Poster
Rep: Reputation: 93
So, after spending 8 continuous hours on this restoring backups from the full backup on July 2nd (which did boot!), and differential since, I found that backups after and including July 19th would not boot. So, something must have happened during the day on July 19th to corrupt some important system file. That backup was actually done on a Sunday and no one was in the office. No special updates were scheduled. A mystery!

I was able to restore a bootable system as of July 18th, then I restored user/data/application directories from there forward (/root, /home, /etc/mail, etc.). It looks like I'm back in action, but I've no idea what happened. I'll check out the log files for the 18th and 19th and see if there are any clues. If I find something, I'll post back.

Last edited by mfoley; 08-08-2017 at 12:12 PM.
 
Old 08-08-2017, 01:00 PM   #13
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,558

Rep: Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495
Check your disks' and file systems' health and don't wait to replace any failing one.
 
Old 08-08-2017, 09:39 PM   #14
mfoley
Member
 
Registered: Oct 2008
Posts: 977

Original Poster
Rep: Reputation: 93
Quote:
Originally Posted by Didier Spaier View Post
Check your disks' and file systems' health and don't wait to replace any failing one.
Not sure how old the physical drives are. They are 500G WDC WD5003AZEX configured as RAID-1 with mdadm. The RAID setup is a bit less than 18 months old. Drives are older. I get a weekly /proc/mdstat report which shows the status of each RAID member. Whatever happened was probably not physical as the "corruption" was copied to both RAID members. To test that, I removed each member in-turn and tried booting from the solo drive. Same result in both cases. That led me to believe it was a soft error -- though I am currently at a loss as to what happened. I'm pretty sure it wasn't an update because I did that at the end of June (2 weeks prior to July 19th). It might be too labor intensive to checksum all possible system files from the good and bad backups.

Last edited by mfoley; 08-08-2017 at 09:41 PM.
 
Old 08-09-2017, 03:31 AM   #15
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 319

Rep: Reputation: 145Reputation: 145
Check:
smartctl -H /dev/sda
smartctl -a /dev/sda
 
1 members found this post helpful.
  


Reply

Tags
boot failure, permission denied


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
Trying to mount loop device during boot: permission denied openSauce Linux - Newbie 5 10-06-2008 12:07 PM
Cannot boot FC5 after installing (permission denied) rjswilson Fedora 3 04-26-2006 01:48 AM
Permission denied on boot up mikieboy Debian 3 04-06-2006 04:25 PM
BOOT DISK PERMISSION DENIED? plz help fucxt Slackware 1 03-18-2006 03:26 PM
Permission denied to drive when mounted at boot wr3ck3d Linux - General 2 12-30-2003 03:38 AM

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

All times are GMT -5. The time now is 09:04 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