public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [SOLVED] hibernate... /bin/echo: write error: No such device
Date: Tue, 11 Oct 2022 23:13:37 -0400	[thread overview]
Message-ID: <Y0Yw4clrEkR9hmJo@waltdnes.org> (raw)
In-Reply-To: <YuGzxFy3Gti11o3Q@waltdnes.org>

On Wed, Jul 27, 2022 at 05:53:08PM -0400, Walter Dnes wrote
>   One of the last few items on the laptop setup.  I emerged hibernate
> and copied over the /etc/hibernate/ directory from my desktop.  When I
> try to hibernate the laptop, I get...
> 
> [thimk][root][~] hibernate
> /bin/echo: write error: No such device
> 
> ...with a beep, and the machine comes back.

  PEBKAC++.  Multiple facepalm.  I outdid myself here.  I got lazy on
the laptop install by copying config files from another machine... and
it came back to bite me.  Here was my /etc/fstab ...

/dev/sda1     /boot       vfat     defaults,noatime                    1 2
/dev/sda2     /           ext3     noatime,nodiratime,async,user_xattr 0 1
/dev/sda3     none        swap     sw                                  0 0

...but, but, but... this is a used Lenovo laptop, too old for UEFI, with
only 75 gigs of disk and I've only got two partitions on it.  I
corrected fstab to the proper...

/dev/sda1     /           ext3     noatime,nodiratime,async,user_xattr 0 1
/dev/sda2     none        swap     sw                                  0 0

  I'm surprised that LILO booted at all with the bad fstab.  There were
only some error message lines that scrolled by really fast at bootup.
Otherwise a perfectly normal bootup.  I finally got around to stopping
the laptop in mid-bootup tonight, and looking at the error message.
Something about fsck.ext3 not finding a magic superblock on /dev/sda2.
This prompted me to dig through the system and find the problem.

  And, oh yeah, hibernate now works with one quirk.  I assume hibernate
was reading the swap partition name from /etc/fstab for hibernation.  Of
course it got "write error: No such device" when trying to save to a
non-existant swap partition /dev/sda3.  The one quirk is that bootup
comes from the first menu item in LILO, unless I manually over-ride.  I
can parse the boot image name from /proc/cmdline and feed it into "lilo -R".
Then I'll have to insert it into the hibernate shutdown scripts.

-- 
I've seen things, you people wouldn't believe; Gopher, Netscape with
frames, the first Browser Wars.  Searching for pages with AltaVista,
pop-up windows self-replicating, trying to uninstall RealPlayer.  All
those moments, will be lost in time like tears in rain... time to die.


      parent reply	other threads:[~2022-10-12  3:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 21:53 [gentoo-user] hibernate... /bin/echo: write error: No such device Walter Dnes
2022-07-27 22:57 ` Adam Carter
2022-07-27 23:40   ` Walter Dnes
2022-07-27 23:42 ` Neil Bothwick
2022-08-01 10:02 ` J. Roeleveld
2022-08-03 21:30   ` Walter Dnes
2022-08-03 22:59     ` Jack
2022-08-03 23:17     ` Neil Bothwick
2022-10-12  3:13 ` Walter Dnes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y0Yw4clrEkR9hmJo@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox