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

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

MacBook pro 2014 stopped booting

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

Contents

  MacBook pro 2014 stopped booting nsrxnst <nsrxnst@bruttocarattere.org> - 2024-12-06 03:10 +0100
    Re: MacBook pro 2014 stopped booting Greg Wooledge <greg@wooledge.org> - 2024-12-06 03:50 +0100
      Re: MacBook pro 2014 stopped booting Felix Miata <mrmazda@stanis.net> - 2024-12-06 06:00 +0100
    Re: MacBook pro 2014 stopped booting nsrxnst <nsrxnst@bruttocarattere.org> - 2024-12-06 03:50 +0100
      Re: MacBook pro 2014 stopped booting eben@gmx.us - 2024-12-06 04:40 +0100
      Re: MacBook pro 2014 stopped booting <tomas@tuxteam.de> - 2024-12-06 10:50 +0100
        Re: MacBook pro 2014 stopped booting Felix Miata <mrmazda@stanis.net> - 2024-12-06 17:40 +0100
          Re: MacBook pro 2014 stopped booting nsrxnst <nsrxnst@bruttocarattere.org> - 2024-12-06 18:10 +0100
          Re: MacBook pro 2014 stopped booting nsrxnst <nsrxnst@bruttocarattere.org> - 2024-12-07 17:30 +0100
    Re: MacBook pro 2014 stopped booting eben@gmx.us - 2024-12-06 04:10 +0100
    Re: MacBook pro 2014 stopped booting David Christensen <dpchrist@holgerdanske.com> - 2024-12-06 05:40 +0100
      Re: MacBook pro 2014 stopped booting nsrxnst <nsrxnst@bruttocarattere.org> - 2024-12-06 18:20 +0100
        Re: MacBook pro 2014 stopped booting Chris Green <cl@isbd.net> - 2024-12-06 20:30 +0100
          Re: MacBook pro 2014 stopped booting David Wright <deblis@lionunicorn.co.uk> - 2024-12-06 21:30 +0100

#275325 — MacBook pro 2014 stopped booting

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

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?

[toc] | [next] | [standalone]

#275326

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.

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

#275333

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

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

#275327

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

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 <nsrxnst@bruttocarattere.org> 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?

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

#275330

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?

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

#275334

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

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

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

#275344

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

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

#275345

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

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 <mrmazda@stanis.net> 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
>

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

#275379

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

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 <mrmazda@stanis.net> 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
>

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

#275328

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.

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

#275332

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

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

#275347

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

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 <dpchrist@holgerdanske.com> 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
>

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

#275353

nsrxnst <nsrxnst@bruttocarattere.org> 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
·

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

#275354

On Fri 06 Dec 2024 at 19:14:51 (+0000), Chris Green wrote:
> nsrxnst <nsrxnst@bruttocarattere.org> 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.

[toc] | [prev] | [standalone]

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

csiph-web