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


Groups > linux.debian.user > #224277

Re: Cannot get systemd to forget about swap space on a failed disk

From David Wright <deblis@lionunicorn.co.uk>
Newsgroups linux.debian.user
Subject Re: Cannot get systemd to forget about swap space on a failed disk
Date 2020-07-02 03:30 +0200
Message-ID <AnWd3-8iG-1@gated-at.bofh.it> (permalink)
References <Ani5Y-6Fh-9@gated-at.bofh.it> <Anipj-6LF-1@gated-at.bofh.it> <AnDtM-3KM-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue 30 Jun 2020 at 22:04:02 (-0700), Bob McGowan wrote:
> On 6/29/2020 11:37 PM, Reco wrote:
> > On Mon, Jun 29, 2020 at 11:10:44PM -0700, Bob McGowan wrote:
> > > But I cannot figure out where this might be, or even if this is the correct interpretation.
> > Check out the contents of /etc/systemd/system first.
> > Rebuild initramfs second.
> 
> It seems my troubleshooting skills are not up to snuff. :(
> 
> I isolated the wrong disk.  This is partly due to the complexity
> (excessive, I think) of the systemd system, partly due to the fact
> that the startup reports of running jobs associated with disks
> overwrite each other, and I just grabbed the wrong one.
> 
> Regardless, upon commenting the correct disk out of fstab, and adding
> back my new secondary swap, everything works again as expected.
> 
> It may help others to know what I did.
> 
> Part of my original failure to find anything was because I was focused
> on the /lib/systemd, /usr/lib/systemd and /etc/systemd directories. 
> Even though I had read the documentation that referenced /run/systemd,
> I had not checked it out.
> 
> When I did, I immediately found the correct UUID information for the
> actual failing disk.  And the rest is history.

I've never consulted those directories, but just use the files
/etc/fstab and /etc/crypttab (written by yourself), a listing
of /dev/disk, and the appropriate commands for handling swap.
Also lsblk gives a neat overview.

So I would stop your broken partition with:

# swapoff foo
# swapon --show		(to see the remaining one and check it out)
# nano /etc/fstab	(and comment the bad entry)
# systemctl daemon-reload

rather than editing fstab while the partition is in use.

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Cannot get systemd to forget about swap space on a failed disk Bob McGowan <ramjr0915@gmail.com> - 2020-06-30 08:40 +0200
  Re: Cannot get systemd to forget about swap space on a failed disk Reco <recoverym4n@enotuniq.net> - 2020-06-30 09:00 +0200
    Re: Cannot get systemd to forget about swap space on a failed disk Bob McGowan <ramjr0915@gmail.com> - 2020-07-01 07:30 +0200
      Re: Cannot get systemd to forget about swap space on a failed disk David Wright <deblis@lionunicorn.co.uk> - 2020-07-02 03:30 +0200
  Re: Cannot get systemd to forget about swap space on a failed disk deloptes <deloptes@gmail.com> - 2020-06-30 09:20 +0200

csiph-web