• MacBook pro 2014 stopped booting

    From nsrxnst@21:1/5 to All on Fri Dec 6 03:10:01 2024
    ------ZA45J11BSS6TGFTJ5CSVCAYJ9LVINM
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    while I was at work, chaos happened in my house. my wife cleaned my office, and her nephew locked himself in there.

    my Debian install has never been ideal: the GUI is spotty, but the underlying system has always functioned just fine, and to that extent, I have used it as a home server.

    it was powered off when I got home.

    upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing that
    brings it back to life, but only so long as I don't try to boot the installed os.

    can someone help me troubleshoot this?
    ------ZA45J11BSS6TGFTJ5CSVCAYJ9LVINM
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html><html><body><div dir="auto">while I was at work, chaos happened in my house. my wife cleaned my office, and her nephew locked himself in there. <br><br>my Debian install has never been ideal: the GUI is spotty, but the underlying system
    has always functioned just fine, and to that extent, I have used it as a home server.<br><br>it was powered off when I got home.<br><br>upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays
    errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing that brings it back to life, but only so long as I don't try to boot the installed os.<br><br>can someone help me
    troubleshoot this?</div></body></html>
    ------ZA45J11BSS6TGFTJ5CSVCAYJ9LVINM--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From nsrxnst@21:1/5 to nsrxnst on Fri Dec 6 03:50:01 2024
    ------XVBVH8CX3GBQ9LFTGT7GM1RC0H5UO9
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    aha.

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    how do I go about recovering this???

    On December 5, 2024 9:03:45 PM EST, nsrxnst <[email protected]> wrote:
    while I was at work, chaos happened in my house. my wife cleaned my office, and her nephew locked himself in there.

    my Debian install has never been ideal: the GUI is spotty, but the underlying system has always functioned just fine, and to that extent, I have used it as a home server.

    it was powered off when I got home.

    upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing
    that brings it back to life, but only so long as I don't try to boot the installed os.

    can someone help me troubleshoot this?
    ------XVBVH8CX3GBQ9LFTGT7GM1RC0H5UO9
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <!doctype html><html><head></head><body><div dir="auto">aha. <br><br>booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.<br><br>how do I go about recovering this???</div><br><br><div
    class="gmail_quote"><div dir="auto">On December 5, 2024 9:03:45 PM EST, nsrxnst &lt;[email protected]&gt; wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;

    <div dir="auto">while I was at work, chaos happened in my house. my wife cleaned my office, and her nephew locked himself in there. <br><br>my Debian install has never been ideal: the GUI is spotty, but the underlying system has always functioned just
    fine, and to that extent, I have used it as a home server.<br><br>it was powered off when I got home.<br><br>upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend,
    and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing that brings it back to life, but only so long as I don't try to boot the installed os.<br><br>can someone help me troubleshoot this?</div></
    blockquote></div></body></html>
    ------XVBVH8CX3GBQ9LFTGT7GM1RC0H5UO9--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Greg Wooledge@21:1/5 to nsrxnst on Fri Dec 6 03:50:01 2024
    On Thu, Dec 05, 2024 at 21:03:45 -0500, nsrxnst wrote:
    my Debian install has never been ideal: the GUI is spotty, [...]

    upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing
    that brings it back to life, but only so long as I don't try to boot the installed os.

    Since you said there's a GUI, it sounds like X (or Wayland) is trying
    to start, and failing. So the first thing I'd do is boot without the
    GUI.

    Assuming you use GRUB (I don't know whether a "MacBook pro 2014" is an
    amd64 system), you should be able to interrupt the boot sequence, press
    the 'e' key to edit the boot parameters, and add

    systemd.unit=multi-user.target

    to the kernel parameters. I think you can also shorten this to just

    2

    but I haven't actually tried that.

    If this gets you to a console login prompt, then you can login on the
    console and try to figure out what's wrong. Everything should be
    working except the GUI, unless there's file system damage.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to nsrxnst on Fri Dec 6 04:10:01 2024
    On 12/5/24 21:03, nsrxnst wrote:
    upon selecting the appropriate option from grub, manually or
    automatically, it begins the boot process, displays errors too fast to comprehend,

    You may be able to read the errors if you video-record the screen during
    boot (higher fps=better) then single-step the recording on playback.

    Also, please wrap your text.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to nsrxnst on Fri Dec 6 04:40:01 2024
    On 12/5/24 21:39, nsrxnst wrote:

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    how do I go about recovering this???

    If you do something like

    mount /dev/sda1 /mnt/temp -o ro -t ext4

    (modify as appropriate)

    does it mount correctly, or is the filesystem damaged/overwritten?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Christensen@21:1/5 to nsrxnst on Fri Dec 6 05:40:01 2024
    On 12/5/24 18:03, nsrxnst wrote:
    while I was at work, chaos happened in my house. my wife cleaned my office, and her nephew locked himself in there.

    my Debian install has never been ideal: the GUI is spotty, but the underlying system has always functioned just fine, and to that extent, I have used it as a home server.

    it was powered off when I got home.

    upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing
    that brings it back to life, but only so long as I don't try to boot the installed os.

    can someone help me troubleshoot this?


    On 12/5/24 18:39, nsrxnst wrote:
    aha.

    booted a live USB. one of the partitions is now of type "swsuspend".
    my sleuthing has led me to decide it's a corrupted fs.

    how do I go about recovering this???


    Processor model? Memory size? SSD size?


    What version of Debian was installed?


    What services was it providing?


    Can you log in to the machine from another computer via ssh(1)?


    Do you have a recent image of the SSD?


    Do you have a recent backup of the data?


    What other computers, disks, etc., do you have available for
    trouble-shooting and repair?


    David

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Felix Miata@21:1/5 to All on Fri Dec 6 06:00:02 2024
    Greg Wooledge composed on 2024-12-05 21:41 (UTC-0500):

    Assuming you use GRUB (I don't know whether a "MacBook pro 2014" is an
    amd64 system), you should be able to interrupt the boot sequence, press

    Apple didn't drop Intel CPUs until 2023. My iMac 2007 is an Intel 64 bit.

    the 'e' key to edit the boot parameters, and add

    systemd.unit=multi-user.target

    to the kernel parameters. I think you can also shorten this to just

    2

    but I haven't actually tried that.

    [quote]
    The multi-user target is the state where the system can accept multiple non-graphical user sessions. It’s equivalent to SysV runlevels 2, 3, and 4. [/quote]
    https://www.baeldung.com/linux/systemd-target-multi-user
    Table mapping of targets to runlevels: https://www.freedesktop.org/software/systemd/man/latest/runlevel.html
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

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

    Felix Miata

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to nsrxnst on Fri Dec 6 10:50:01 2024
    On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
    aha.

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    I've got a different hunch from the others expressed in this
    thread: your computer is trying to restore from a (corrupted)
    hibernated session.

    But beware: it's only a hunch. At this point it is as (in)valid
    as all the others :-)

    What partitions do you see, apart of that one "swsuspend"
    thing?

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZ1LIJAAKCRAFyCz1etHa RqWYAJ0cfe1gejIFLMKqm8/M8Jm41Z9CpwCeLec5cenQ+r0fL7Ik65pTuwJsdH8=
    =kfJQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Felix Miata@21:1/5 to All on Fri Dec 6 17:40:01 2024
    tomas composed on 2024-12-06 10:47 (UTC+0100):

    On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
    aha.

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    I've got a different hunch from the others expressed in this
    thread: your computer is trying to restore from a (corrupted)
    hibernated session.

    But beware: it's only a hunch. At this point it is as (in)valid
    as all the others :-)

    /If/ this is correct, and the source of it is a swap partition, then recreating the swap /ought/ to be a simple solution. From a live boot, I might do:

    mkswap -L swapper /dev/<name>

    then edit /etc/fstab, changing the swap entry to use

    LABEL=swapper swap swap defaults 0 0

    instead of UUID=<yadayadayadayadayadayadayadayadayada> swap swap defaults 0 0

    However, easier would be to strike the E key at the installed system's Grub menu
    and replace the resume= entry with noresume, then proceed with boot, and when booted, do what I wrote above.
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

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

    Felix Miata

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From nsrxnst@21:1/5 to Felix Miata on Fri Dec 6 18:10:01 2024
    ------FMVFVJNZULQN80H7FYND110FGJTO1K
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    having dug through all the functioning partitions, I have concluded it is my swap partition. I even had the intuition to reformat the swap partition. I'm going to try the no resume option and see if that does it.

    On December 6, 2024 11:31:51 AM EST, Felix Miata <[email protected]> wrote: >tomas composed on 2024-12-06 10:47 (UTC+0100):

    On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
    aha.

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    I've got a different hunch from the others expressed in this
    thread: your computer is trying to restore from a (corrupted)
    hibernated session.

    But beware: it's only a hunch. At this point it is as (in)valid
    as all the others :-)

    /If/ this is correct, and the source of it is a swap partition, then recreating
    the swap /ought/ to be a simple solution. From a live boot, I might do:

    mkswap -L swapper /dev/<name>

    then edit /etc/fstab, changing the swap entry to use

    LABEL=swapper swap swap defaults 0 0

    instead of UUID=<yadayadayadayadayadayadayadayadayada> swap swap defaults 0 0

    However, easier would be to strike the E key at the installed system's Grub menu
    and replace the resume= entry with noresume, then proceed with boot, and when >booted, do what I wrote above.
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

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

    Felix Miata


    ------FMVFVJNZULQN80H7FYND110FGJTO1K
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body><div dir="auto">having dug through all the functioning partitions, I have concluded it is my swap partition. I even had the intuition to reformat the swap partition. I'm going to try the no resume option and see if that does it.</
    <br><br><div class="gmail_quote"><div dir="auto">On December 6, 2024 11:31:51 AM EST, Felix Miata &lt;[email protected]&gt; wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
    padding-left: 1ex;">
    <pre class="k9mail"><div dir="auto">tomas composed on 2024-12-06 10:47 (UTC+0100):<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">On Thu, Dec 05, 2024 at
    09:39:55PM -0500, nsrxnst wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><div dir="auto">aha. <br></div></blockquote></blockquote><div dir="auto"><br></div><blockquote
    class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><div dir="auto">booted a live
    USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.<br></div></blockquote></blockquote><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px
    solid #729fcf; padding-left: 1ex;"><div dir="auto">I've got a different hunch from the others expressed in this<br>thread: your computer is trying to restore from a (corrupted)<br>hibernated session.<br></div></blockquote><div dir="auto"><br></div><
    blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">But beware: it's only a hunch. At this point it is as (in)valid<br>as all the others :-)<br></div></blockquote><div dir="
    auto"><br>/If/ this is correct, and the source of it is a swap partition, then recreating<br>the swap /ought/ to be a simple solution. From a live boot, I might do:<br><br> mkswap -L swapper /dev/&lt;name&gt;<br><br>then edit /etc/fstab, changing the
    swap entry to use<br><br> LABEL=swapper swap swap defaults 0 0<br><br>instead of UUID=&lt;yadayadayadayadayadayadayadayadayada&gt; swap swap defaults 0 0<br><br>However, easier would be to strike the E key at the installed system's Grub menu<br>and
    replace the resume= entry with noresume, then proceed with boot, and when<br>booted, do what I wrote above.<br></div></pre></blockquote></div></body></html>
    ------FMVFVJNZULQN80H7FYND110FGJTO1K--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From nsrxnst@21:1/5 to David Christensen on Fri Dec 6 18:20:01 2024
    ------MKCYLFV6KTNL6UPIYKRRHNMR3BQVD6
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    The machine was gifted, and I was just so happy I could get Debian to boot then I never really investigated the hardware or thought much about it.

    it looks like there is a solution floating around this thread that I'm going to be trying.

    I have a Lenovo running Deb 12. The MacBook was also running Deb 12. I think it had SSH and a few other services like WeeChat and I think it was running a next cloud install.

    I won't get to actually troubleshoot it until I'm on a bus tomorrow afternoon. if I am unable to just reformat the swap partition and get it to boot, I'll follow up with you.

    On December 5, 2024 11:38:50 PM EST, David Christensen <[email protected]> wrote:
    On 12/5/24 18:03, nsrxnst wrote:
    while I was at work, chaos happened in my house. my wife cleaned my office, and her nephew locked himself in there.

    my Debian install has never been ideal: the GUI is spotty, but the underlying system has always functioned just fine, and to that extent, I have used it as a home server.

    it was powered off when I got home.

    upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power button long-presses seem to be the only thing
    that brings it back to life, but only so long as I don't try to boot the installed os.

    can someone help me troubleshoot this?


    On 12/5/24 18:39, nsrxnst wrote:
    aha.

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    how do I go about recovering this???


    Processor model? Memory size? SSD size?


    What version of Debian was installed?


    What services was it providing?


    Can you log in to the machine from another computer via ssh(1)?


    Do you have a recent image of the SSD?


    Do you have a recent backup of the data?


    What other computers, disks, etc., do you have available for trouble-shooting and repair?


    David


    ------MKCYLFV6KTNL6UPIYKRRHNMR3BQVD6
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body><div dir="auto">The machine was gifted, and I was just so happy I could get Debian to boot then I never really investigated the hardware or thought much about it. <br><br>it looks like there is a solution floating around this
    thread that I'm going to be trying. <br><br>I have a Lenovo running Deb 12. The MacBook was also running Deb 12. I think it had SSH and a few other services like WeeChat and I think it was running a next cloud install. <br><br>I won't get to actually
    troubleshoot it until I'm on a bus tomorrow afternoon. if I am unable to just reformat the swap partition and get it to boot, I'll follow up with you.</div><br><br><div class="gmail_quote"><div dir="auto">On December 5, 2024 11:38:50 PM EST, David
    Christensen &lt;[email protected]&gt; wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
    <pre class="k9mail"><div dir="auto">On 12/5/24 18:03, nsrxnst wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">while I was at work, chaos happened in my
    house. my wife cleaned my office, and her nephew locked himself in there.<br><br>my Debian install has never been ideal: the GUI is spotty, but the underlying system has always functioned just fine, and to that extent, I have used it as a home server.<br>
    <br>it was powered off when I got home.<br><br>upon selecting the appropriate option from grub, manually or automatically, it begins the boot process, displays errors too fast to comprehend, and the screen goes to a cursor, then black. repeated power
    button long-presses seem to be the only thing that brings it back to life, but only so long as I don't try to boot the installed os.<br><br>can someone help me troubleshoot this?<br></div></blockquote><div dir="auto"><br><br>On 12/5/24 18:39, nsrxnst
    wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto"> aha.<br><br> booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led
    me to decide it's a corrupted fs.<br><br> how do I go about recovering this???<br></div></blockquote><div dir="auto"><br><br>Processor model? Memory size? SSD size?<br><br><br>What version of Debian was installed?<br><br><br>What services was it
    providing?<br><br><br>Can you log in to the machine from another computer via ssh(1)?<br><br><br>Do you have a recent image of the SSD?<br><br><br>Do you have a recent backup of the data?<br><br><br>What other computers, disks, etc., do you have
    available for trouble-shooting and repair?<br><br><br>David<br><br></div></pre></blockquote></div></body></html>
    ------MKCYLFV6KTNL6UPIYKRRHNMR3BQVD6--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Green@21:1/5 to nsrxnst on Fri Dec 6 20:30:01 2024
    nsrxnst <[email protected]> wrote:
    [-- text/plain, encoding quoted-printable, charset: utf-8, 70 lines --]

    The machine was gifted, and I was just so happy I could get Debian to boot

    That doesn't mean what you intended! (at least not to me it didn't)
    It means the machine was clever (in itself). What you meant (and it
    took me a while to realise) was that the machine was given to you.

    --
    Chris Green
    ·

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Wright@21:1/5 to Chris Green on Fri Dec 6 21:30:01 2024
    On Fri 06 Dec 2024 at 19:14:51 (+0000), Chris Green wrote:
    nsrxnst <[email protected]> wrote:
    [-- text/plain, encoding quoted-printable, charset: utf-8, 70 lines --]

    The machine was gifted, and I was just so happy I could get Debian to boot

    That doesn't mean what you intended! (at least not to me it didn't)
    It means the machine was clever (in itself).

    Oh come now, that's a category mistake. Inanimate objects
    can't be gifted in that sense.

    What you meant (and it
    took me a while to realise) was that the machine was given to you.

    Given [away], donated, gifted: any of these might apply, according
    to circumstances. On an international mailing list, and without
    context, I'd treat them all as synonyms.

    Cheers,
    David.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From nsrxnst@21:1/5 to Felix Miata on Sat Dec 7 17:30:01 2024
    ------YMQRIBAWQI6WKC8TZXK4QBNNMCDGO8
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    holy smokes. I deleted the part, created ext4 on it, then mkswap'ed it, and I'm booting!!!!!

    On December 6, 2024 11:31:51 AM EST, Felix Miata <[email protected]> wrote: >tomas composed on 2024-12-06 10:47 (UTC+0100):

    On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
    aha.

    booted a live USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.

    I've got a different hunch from the others expressed in this
    thread: your computer is trying to restore from a (corrupted)
    hibernated session.

    But beware: it's only a hunch. At this point it is as (in)valid
    as all the others :-)

    /If/ this is correct, and the source of it is a swap partition, then recreating
    the swap /ought/ to be a simple solution. From a live boot, I might do:

    mkswap -L swapper /dev/<name>

    then edit /etc/fstab, changing the swap entry to use

    LABEL=swapper swap swap defaults 0 0

    instead of UUID=<yadayadayadayadayadayadayadayadayada> swap swap defaults 0 0

    However, easier would be to strike the E key at the installed system's Grub menu
    and replace the resume= entry with noresume, then proceed with boot, and when >booted, do what I wrote above.
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

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

    Felix Miata


    ------YMQRIBAWQI6WKC8TZXK4QBNNMCDGO8
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body><div dir="auto">holy smokes. I deleted the part, created ext4 on it, then mkswap'ed it, and I'm booting!!!!!</div><br><br><div class="gmail_quote"><div dir="auto">On December 6, 2024 11:31:51 AM EST, Felix Miata &lt;mrmazda@
    stanis.net&gt; wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
    <pre class="k9mail"><div dir="auto">tomas composed on 2024-12-06 10:47 (UTC+0100):<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">On Thu, Dec 05, 2024 at
    09:39:55PM -0500, nsrxnst wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><div dir="auto">aha. <br></div></blockquote></blockquote><div dir="auto"><br></div><blockquote
    class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><div dir="auto">booted a live
    USB. one of the partitions is now of type "swsuspend". my sleuthing has led me to decide it's a corrupted fs.<br></div></blockquote></blockquote><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px
    solid #729fcf; padding-left: 1ex;"><div dir="auto">I've got a different hunch from the others expressed in this<br>thread: your computer is trying to restore from a (corrupted)<br>hibernated session.<br></div></blockquote><div dir="auto"><br></div><
    blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">But beware: it's only a hunch. At this point it is as (in)valid<br>as all the others :-)<br></div></blockquote><div dir="
    auto"><br>/If/ this is correct, and the source of it is a swap partition, then recreating<br>the swap /ought/ to be a simple solution. From a live boot, I might do:<br><br> mkswap -L swapper /dev/&lt;name&gt;<br><br>then edit /etc/fstab, changing the
    swap entry to use<br><br> LABEL=swapper swap swap defaults 0 0<br><br>instead of UUID=&lt;yadayadayadayadayadayadayadayadayada&gt; swap swap defaults 0 0<br><br>However, easier would be to strike the E key at the installed system's Grub menu<br>and
    replace the resume= entry with noresume, then proceed with boot, and when<br>booted, do what I wrote above.<br></div></pre></blockquote></div></body></html>
    ------YMQRIBAWQI6WKC8TZXK4QBNNMCDGO8--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)