Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #161975 > unrolled thread

Stretch installation boots to read only

Started byGary Roach <gary719_list1@verizon.net>
First post2015-12-22 02:10 +0100
Last post2015-12-22 12:50 +0100
Articles 10 — 6 participants

Back to article view | Back to linux.debian.user

Contents

  Stretch installation boots to read only Gary Roach <gary719_list1@verizon.net> - 2015-12-22 02:10 +0100
    Re: Stretch installation boots to read only Sven Hartge <sven@svenhartge.de> - 2015-12-22 04:30 +0100
      Re: Stretch installation boots to read only Marc Shapiro <marcnshap@gmail.com> - 2015-12-22 04:50 +0100
        Re: Stretch installation boots to read only Sven Hartge <sven@svenhartge.de> - 2015-12-22 06:20 +0100
          Re: Stretch installation boots to read only Gary Roach <gary719_list1@verizon.net> - 2015-12-22 09:00 +0100
            Re: Stretch installation boots to read only Felix Miata <mrmazda@earthlink.net> - 2015-12-22 10:20 +0100
            Re: Stretch installation boots to read only anxiousmac@gmail.com - 2015-12-22 10:40 +0100
              Re: Stretch installation boots to read only(SOLVED) Gary Roach <gary719_list1@verizon.net> - 2015-12-22 21:40 +0100
                Re: Stretch installation boots to read only(SOLVED) Sven Hartge <sven@svenhartge.de> - 2015-12-22 22:30 +0100
            consolekit in jessie (Re: Stretch installation boots to read only) Michael Biebl <biebl@debian.org> - 2015-12-22 12:50 +0100

#161975 — Stretch installation boots to read only

FromGary Roach <gary719_list1@verizon.net>
Date2015-12-22 02:10 +0100
SubjectStretch installation boots to read only
Message-ID<qIjCF-5Bi-15@gated-at.bofh.it>
Hi all;

I Just upgraded from jessie to stretch. I needed a piece of software 
that wasn't available in jessie. Since then, my system boots to a 
command line prompt. Since /dev/sda1 has been mounted ro, Xwindows 
doesn't start. I have to log in as root, run mount -o remount,rw 
/dev/sda1 /, exit from root and then run startx each time I reboot the 
system. If i run mount -a, an error occurs in fstab at line 9 which 
happens to be the mounting instructions for /dev/sda1. I re-wrote the 
line to read /dev/sda1    /  ext4  rw, noatime    0   1 and commented 
out the old line. The error still happens at the same place.

During boot sda1 passes the system check and after hand rebooting the 
system works fine. An fsck check passes with flying colors.  Does anyone 
have a clue as to what is going on here.

Gary R.

[toc] | [next] | [standalone]

#161977

FromSven Hartge <sven@svenhartge.de>
Date2015-12-22 04:30 +0100
Message-ID<qIlO9-6X3-1@gated-at.bofh.it>
In reply to#161975
Gary Roach <gary719_list1@verizon.net> wrote:

> I Just upgraded from jessie to stretch. I needed a piece of software 
> that wasn't available in jessie. Since then, my system boots to a 
> command line prompt. Since /dev/sda1 has been mounted ro, Xwindows 
> doesn't start. I have to log in as root, run mount -o remount,rw 
> /dev/sda1 /, exit from root and then run startx each time I reboot the 
> system. If i run mount -a, an error occurs in fstab at line 9 which 
> happens to be the mounting instructions for /dev/sda1. I re-wrote the 
> line to read /dev/sda1    /  ext4  rw, noatime    0   1 and commented 
> out the old line. The error still happens at the same place.

Without you providing the exact error nobody will be able to help you.

So please paste the complete /etc/fstab as it is without any
modifications, deletions or alterations, the output of "systemctl
--failed" without any omissions and the exact error you get after "mount
-a" without any own interpretations.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#161978

FromMarc Shapiro <marcnshap@gmail.com>
Date2015-12-22 04:50 +0100
Message-ID<qIm7v-75a-17@gated-at.bofh.it>
In reply to#161977
On 12/21/2015 07:19 PM, Sven Hartge wrote:
> Gary Roach <gary719_list1@verizon.net> wrote:
>
>> I Just upgraded from jessie to stretch. I needed a piece of software
>> that wasn't available in jessie. Since then, my system boots to a
>> command line prompt. Since /dev/sda1 has been mounted ro, Xwindows
>> doesn't start. I have to log in as root, run mount -o remount,rw
>> /dev/sda1 /, exit from root and then run startx each time I reboot the
>> system. If i run mount -a, an error occurs in fstab at line 9 which
>> happens to be the mounting instructions for /dev/sda1. I re-wrote the
>> line to read /dev/sda1    /  ext4  rw, noatime    0   1 and commented
>> out the old line. The error still happens at the same place.
> Without you providing the exact error nobody will be able to help you.
>
> So please paste the complete /etc/fstab as it is without any
> modifications, deletions or alterations, the output of "systemctl
> --failed" without any omissions and the exact error you get after "mount
> -a" without any own interpretations.
>
> Grüße,
> Sven.
>
I believe that there should not be any spaces in the options, so if the 
line in /etc/fstab actually reads:

	/dev/sda1    /  ext4  rw, noatime    0   1

It should be:

	/dev/sda1    /  ext4  rw,noatime     0   1


Marc

[toc] | [prev] | [next] | [standalone]

#161980

FromSven Hartge <sven@svenhartge.de>
Date2015-12-22 06:20 +0100
Message-ID<qInwB-84N-5@gated-at.bofh.it>
In reply to#161978
Marc Shapiro <marcnshap@gmail.com> wrote:
> On 12/21/2015 07:19 PM, Sven Hartge wrote:
>> Gary Roach <gary719_list1@verizon.net> wrote:

>>> I re-wrote the line to read /dev/sda1    /  ext4  rw, noatime    0
>>> 1 and commented out the old line. The error still happens at the
>>> same place.

>> Without you providing the exact error nobody will be able to help
>> you.
>>
>> So please paste the complete /etc/fstab as it is without any
>> modifications, deletions or alterations, the output of "systemctl
>> --failed" without any omissions and the exact error you get after
>> "mount -a" without any own interpretations.

> I believe that there should not be any spaces in the options, so if
> the line in /etc/fstab actually reads:

>        /dev/sda1    /  ext4  rw, noatime    0   1

> It should be:

>        /dev/sda1    /  ext4  rw,noatime     0   1


This is correct. But without an unaltered copy of the fstab from Gary we
will never know and only be able to guess.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#161986

FromGary Roach <gary719_list1@verizon.net>
Date2015-12-22 09:00 +0100
Message-ID<qIq1s-14E-13@gated-at.bofh.it>
In reply to#161980
OK

systemctl --failed gives
root@supercrunch:/etc# systemctl --failed
   UNIT                                 LOAD   ACTIVE SUB DESCRIPTION
● anacron.service                      loaded failed failed Run anacron jobs
● apache2.service                      loaded failed failed LSB: Apache2 
web server
● autofs.service                       loaded failed failed Automounts 
filesystems on demand
● colord.service                       loaded failed failed Manage, 
Install and Generate Color Profiles
● console-kit-log-system-start.service loaded failed failed Console 
System Startup Logging
● exim4.service                        loaded failed failed LSB: exim 
Mail Transport Agent
● munin-node.service                   loaded failed failed Munin Node
● postgresql@9.1-main.service          loaded failed failed PostgreSQL 
Cluster 9.1-main
● postgresql@9.4-main.service          loaded failed failed PostgreSQL 
Cluster 9.4-main
● systemd-hostnamed.service            loaded failed failed Hostname Service
● systemd-tmpfiles-setup.service       loaded failed failed Create 
Volatile Files and Directories
● systemd-update-utmp.service          loaded failed failed Update UTMP 
about System Boot/Shutdown

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

12 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

And fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type> <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
/dev/sda1          /            ext4     rw noatime      0 1
# UUID=3b06b2a3-6daa-4b9f-983b-84501950bc9c  / ext4    rw, noatime  
0       1
# swap was on /dev/sda5 during installation
/dev/sda5        none            swap     sw               0 0
# UUID=0a63cffb-6edb-4d5c-a1f6-a2438d4a7745  none swap    
sw              0       0
   /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto 0       0

This didn't work with the UUID's either.

And the mount -a error is:
root@supercrunch:/etc# mount -a
mount: /etc/fstab: parse error: ignore entry at line 9.

I think that covers everything. I went through the apt-get process until 
no more files needed updating. Ran apt-get check etc. Nothing showed up.

Gary R.



On 12/21/2015 09:18 PM, Sven Hartge wrote:
> Marc Shapiro <marcnshap@gmail.com> wrote:
>> On 12/21/2015 07:19 PM, Sven Hartge wrote:
>>> Gary Roach <gary719_list1@verizon.net> wrote:
>>>> I re-wrote the line to read /dev/sda1    /  ext4  rw, noatime    0
>>>> 1 and commented out the old line. The error still happens at the
>>>> same place.
>>> Without you providing the exact error nobody will be able to help
>>> you.
>>>
>>> So please paste the complete /etc/fstab as it is without any
>>> modifications, deletions or alterations, the output of "systemctl
>>> --failed" without any omissions and the exact error you get after
>>> "mount -a" without any own interpretations.
>> I believe that there should not be any spaces in the options, so if
>> the line in /etc/fstab actually reads:
>>         /dev/sda1    /  ext4  rw, noatime    0   1
>> It should be:
>>         /dev/sda1    /  ext4  rw,noatime     0   1
>
> This is correct. But without an unaltered copy of the fstab from Gary we
> will never know and only be able to guess.
>
> Grüße,
> Sven.
>

[toc] | [prev] | [next] | [standalone]

#161987

FromFelix Miata <mrmazda@earthlink.net>
Date2015-12-22 10:20 +0100
Message-ID<qIrgU-23R-29@gated-at.bofh.it>
In reply to#161986
Gary Roach composed on 2015-12-21 23:57 (UTC-0800):

> # <file system> <mount point>   <type> <options>       <dump>  <pass>
> # / was on /dev/sda1 during installation
> /dev/sda1          /            ext4     rw noatime      0 1

Invalid, so due to the bad entry, / gets mounted ro. You cannot have
whitespace except where the header line shows you. White is for separating
fields, so with the extra in place of a comma, you have too many parameters,
and a bad type in field 5.

s/rw noatime/rw,noatime/ should fix it.

> # UUID=3b06b2a3-6daa-4b9f-983b-84501950bc9c  / ext4    rw, noatime   0       1

The space between "," and noatime makes the line similarly invalid, for the
same reason - 7 instead of 6, and bad type in #5.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#161988

Fromanxiousmac@gmail.com
Date2015-12-22 10:40 +0100
Message-ID<qIrAe-2af-31@gated-at.bofh.it>
In reply to#161986
On Tuesday, 22 December 2015 08:00:05 UTC, Gary Roach  wrote:
> OK
> 
> systemctl --failed gives
> root@supercrunch:/etc# systemctl --failed
>    UNIT                                 LOAD   ACTIVE SUB DESCRIPTION
> ● anacron.service                      loaded failed failed Run anacron jobs
> ● apache2.service                      loaded failed failed LSB: Apache2 
> web server
> ● autofs.service                       loaded failed failed Automounts 
> filesystems on demand
> ● colord.service                       loaded failed failed Manage, 
> Install and Generate Color Profiles
> ● console-kit-log-system-start.service loaded failed failed Console 
> System Startup Logging
> ● exim4.service                        loaded failed failed LSB: exim 
> Mail Transport Agent
> ● munin-node.service                   loaded failed failed Munin Node
> ● postgresql@9.1-main.service          loaded failed failed PostgreSQL 
> Cluster 9.1-main
> ● postgresql@9.4-main.service          loaded failed failed PostgreSQL 
> Cluster 9.4-main
> ● systemd-hostnamed.service            loaded failed failed Hostname Service
> ● systemd-tmpfiles-setup.service       loaded failed failed Create 
> Volatile Files and Directories
> ● systemd-update-utmp.service          loaded failed failed Update UTMP 
> about System Boot/Shutdown
> 
> LOAD   = Reflects whether the unit definition was properly loaded.
> ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
> SUB    = The low-level unit activation state, values depend on unit type.
> 
> 12 loaded units listed. Pass --all to see loaded but inactive units, too.
> To show all installed unit files use 'systemctl list-unit-files'.
> 
> And fstab:
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point>   <type> <options>       <dump>  <pass>
> # / was on /dev/sda1 during installation
> /dev/sda1          /            ext4     rw noatime      0 1
> # UUID=3b06b2a3-6daa-4b9f-983b-84501950bc9c  / ext4    rw, noatime  
> 0       1
> # swap was on /dev/sda5 during installation
> /dev/sda5        none            swap     sw               0 0
> # UUID=0a63cffb-6edb-4d5c-a1f6-a2438d4a7745  none swap    
> sw              0       0
>    /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto 0       0
> 
> This didn't work with the UUID's either.
> 
> And the mount -a error is:
> root@supercrunch:/etc# mount -a
> mount: /etc/fstab: parse error: ignore entry at line 9.
> 
> I think that covers everything. I went through the apt-get process until 
> no more files needed updating. Ran apt-get check etc. Nothing showed up.
> 
> Gary R.

/etc/fstab uses spaces to separate the fields. There may, once upon a time, have been a good reason for that design decision.

So your line:

/dev/sda1          /            ext4     rw noatime      0 1

needs the space between rw and noatime to be replaced by a comma and no space.

As Marc pointed out above.

anxiousmac

[toc] | [prev] | [next] | [standalone]

#162001 — Re: Stretch installation boots to read only(SOLVED)

FromGary Roach <gary719_list1@verizon.net>
Date2015-12-22 21:40 +0100
SubjectRe: Stretch installation boots to read only(SOLVED)
Message-ID<qIBSW-e4-11@gated-at.bofh.it>
In reply to#161988
Thanks all;
The corrections in fstab fixed all of the problems. Thanks for the tip 
to get rid of ConsoleKit.
That said, what caused this problem. I did not edit the fstab file 
during upgrade and the system was working just fine before. Is this a 
bug in the upgrade process? I have seen several other web questions on 
the same problem. I had the same problem when I upgraded to jessie. That 
time I ended up reinstalling the whole system since it needed a good 
housecleaning anyway.

Gary R.

On 12/22/2015 01:14 AM, anxiousmac@gmail.com wrote:
> On Tuesday, 22 December 2015 08:00:05 UTC, Gary Roach  wrote:
>> OK
>>
>> systemctl --failed gives
>> root@supercrunch:/etc# systemctl --failed
>>     UNIT                                 LOAD   ACTIVE SUB DESCRIPTION
>> ● anacron.service                      loaded failed failed Run anacron jobs
>> ● apache2.service                      loaded failed failed LSB: Apache2
>> web server
>> ● autofs.service                       loaded failed failed Automounts
>> filesystems on demand
>> ● colord.service                       loaded failed failed Manage,
>> Install and Generate Color Profiles
>> ● console-kit-log-system-start.service loaded failed failed Console
>> System Startup Logging
>> ● exim4.service                        loaded failed failed LSB: exim
>> Mail Transport Agent
>> ● munin-node.service                   loaded failed failed Munin Node
>> ● postgresql@9.1-main.service          loaded failed failed PostgreSQL
>> Cluster 9.1-main
>> ● postgresql@9.4-main.service          loaded failed failed PostgreSQL
>> Cluster 9.4-main
>> ● systemd-hostnamed.service            loaded failed failed Hostname Service
>> ● systemd-tmpfiles-setup.service       loaded failed failed Create
>> Volatile Files and Directories
>> ● systemd-update-utmp.service          loaded failed failed Update UTMP
>> about System Boot/Shutdown
>>
>> LOAD   = Reflects whether the unit definition was properly loaded.
>> ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
>> SUB    = The low-level unit activation state, values depend on unit type.
>>
>> 12 loaded units listed. Pass --all to see loaded but inactive units, too.
>> To show all installed unit files use 'systemctl list-unit-files'.
>>
>> And fstab:
>> # /etc/fstab: static file system information.
>> #
>> # Use 'blkid' to print the universally unique identifier for a
>> # device; this may be used with UUID= as a more robust way to name devices
>> # that works even if disks are added and removed. See fstab(5).
>> #
>> # <file system> <mount point>   <type> <options>       <dump>  <pass>
>> # / was on /dev/sda1 during installation
>> /dev/sda1          /            ext4     rw noatime      0 1
>> # UUID=3b06b2a3-6daa-4b9f-983b-84501950bc9c  / ext4    rw, noatime
>> 0       1
>> # swap was on /dev/sda5 during installation
>> /dev/sda5        none            swap     sw               0 0
>> # UUID=0a63cffb-6edb-4d5c-a1f6-a2438d4a7745  none swap
>> sw              0       0
>>     /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto 0       0
>>
>> This didn't work with the UUID's either.
>>
>> And the mount -a error is:
>> root@supercrunch:/etc# mount -a
>> mount: /etc/fstab: parse error: ignore entry at line 9.
>>
>> I think that covers everything. I went through the apt-get process until
>> no more files needed updating. Ran apt-get check etc. Nothing showed up.
>>
>> Gary R.
> /etc/fstab uses spaces to separate the fields. There may, once upon a time, have been a good reason for that design decision.
>
> So your line:
>
> /dev/sda1          /            ext4     rw noatime      0 1
>
> needs the space between rw and noatime to be replaced by a comma and no space.
>
> As Marc pointed out above.
>
> anxiousmac
>
>

[toc] | [prev] | [next] | [standalone]

#162003 — Re: Stretch installation boots to read only(SOLVED)

FromSven Hartge <sven@svenhartge.de>
Date2015-12-22 22:30 +0100
SubjectRe: Stretch installation boots to read only(SOLVED)
Message-ID<qICFj-JT-5@gated-at.bofh.it>
In reply to#162001
Gary Roach <gary719_list1@verizon.net> wrote:

> That said, what caused this problem. I did not edit the fstab file 
> during upgrade and the system was working just fine before. Is this a 
> bug in the upgrade process? 

As far as I know the upgrade process does not touch /etc/fstab. So my
guess is that this entry was already broken a long time but you never
noticed because the SysV-Init scripts are very forgiving and papered
over many errors like this while systemd is very strict.

This is why you so many "systemd is bad, my Debian is broken now!" posts
and emails all over the place but on most cases systemd is only the
messenger of brokeness and not the main cause.


Grüße,
S°

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#161990 — consolekit in jessie (Re: Stretch installation boots to read only)

FromMichael Biebl <biebl@debian.org>
Date2015-12-22 12:50 +0100
Subjectconsolekit in jessie (Re: Stretch installation boots to read only)
Message-ID<qItC2-3qD-13@gated-at.bofh.it>
In reply to#161986

[Multipart message — attachments visible in raw view] — view raw

Am 22.12.2015 um 08:57 schrieb Gary Roach:
> ● console-kit-log-system-start.service loaded failed failed Console

This is an unrelated comment, but since I've seen consolekit in the list
of services:

With jessie, that service is in the vast majority of cases not necessary
anymore. Unfortunately it's not removed automatically on upgrades.
So I would suggest anyone reading this list to run

apt-get remove --purge consolekit libck-connector0 libpam-ck-connector

If that doesn't want to remove any important package, proceed with the
removal. Und you have one system process less.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web