Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: /srv empty after booting, recovering folders after reboot

  1. #21
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    34

    Default Re: /srv empty after booting, recovering folders after reboot

    We progress ! I ran journalctl as soon as the problem appeared, and ...

    Code:
    erik@linux-5n3o:~> sudo journalctl | grep srv
    [sudo] Mot de passe de root : 
    août 21 19:46:40 linux-5n3o systemd[1]: Mounting /srv...
    août 21 19:46:40 linux-5n3o systemd[1]: Mounted /srv.
    août 21 19:46:47 linux-5n3o systemd[1]: Unmounting /srv...
    août 21 19:46:47 linux-5n3o systemd[1]: srv.mount: Succeeded.
    août 21 19:46:47 linux-5n3o systemd[1]: Unmounted /srv.
    So I just have to mount /srv, no need to reboot !

    Any idea about what could make /srv being unmounted during boot up ?

    (edit)
    At the same time, I found apache2 inactive, though it is normally launched at start up and I had to start it ... wow ...
    Last edited by Voronamanga; 21-Aug-2019 at 09:19. Reason: additional information

  2. #22
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: /srv empty after booting, recovering folders after reboot

    I see higher up in this thread that /srv is a Btrfs subvolume.
    I have no Btrfs knowledge (and do not use it). Thus others may try to explain this.
    Henk van Velden

  3. #23
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    34

    Default Re: /srv empty after booting, recovering folders after reboot

    @Henk : thanks anyway !

    I wonder why I limited journalctl to grep /srv. Next time I'll have to look at messages just preceding "unmount /srv"...

  4. #24
    Join Date
    Sep 2012
    Posts
    5,012

    Default Re: /srv empty after booting, recovering folders after reboot

    Quote Originally Posted by Voronamanga View Post
    Any idea about what could make /srv being unmounted during boot up ?
    Boot with "systemd.log_level=debug printk.devkmsg=on log_buf_len=8M" and provide full output of "journalctl -b".

  5. #25
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    34

    Default Re: /srv empty after booting, recovering folders after reboot

    Quote Originally Posted by arvidjaar View Post
    Boot with "systemd.log_level=debug printk.devkmsg=on log_buf_len=8M" and provide full output of "journalctl -b".
    Hi arvidjaar, thank you for replying.

    I booted this evening and encountered the issue which is the matter of this thread. Unfortunately I could'nt have read your post before. Then I rebooted the way you suggested but as usually, the problem did'nt show off again - anyway here is the result of journalctl -b :
    https://susepaste.org/46695941

    I noticed that many directories, and not only /srv, were told as unmounted in the former log. Being declared as unmounted sounds weird to me, because they are present in the system tree, the problem is that they look empty except hidden files. They all figure in my fstab :

    Code:
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /                       btrfs  defaults                      0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
    UUID=7f106034-fa4d-4db0-985e-d6cac4d28178  swap                    swap   defaults                      0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /var                    btrfs  subvol=/@/var                 0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /usr/local              btrfs  subvol=/@/usr/local           0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /tmp                    btrfs  subvol=/@/tmp                 0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /srv                    btrfs  subvol=/@/srv                 0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /root                   btrfs  subvol=/@/root                0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /opt                    btrfs  subvol=/@/opt                 0  0
    UUID=72aa2929-b98f-449b-935c-a833d98d5655  /home                   ext4   data=ordered                  0  2
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
    UUID=63d518af-52ff-4179-b186-340a7abd02b8  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
    UUID=58ED-09A0                             /boot/efi               vfat   defaults                      0  0
    LABEL=Media                                /home/erik/Media        ext4   user_xattr,data=ordered       0  0
    What suggested me to look into fstab was the fact that directories (which appeared to be the ones listed in fstab) were successively unmounted an mounted, and unmounted, in the journal report. I have no idea of the reason for that.

    The former output of journalctl, a couple of hours ago when I booted with unsuccessful mount of /srv (and probably other directories), showed errors with freedesktop and others, and asked for a fsck on dev/sdc1. I give it below in the case it would be useful.
    https://susepaste.org/64601347

    Thanks for anything that could make me wiser than today !
    Last edited by Voronamanga; 23-Aug-2019 at 09:33. Reason: typo

Page 3 of 3 FirstFirst 123

Tags for this Thread

Posting Permissions

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