this post was submitted on 12 Nov 2023
11 points (86.7% liked)

Linux

7796 readers
56 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
 

Hi all,

Long story as short as possible:

Lenovo Ideapad 3. I had windows 11 on SSD. Installed Ubuntu on HDD, dual boot with windows on SSD. Later decided I like Linux, no need for Windows. Installed Kubuntu on the SSD. Worked fine. Manually deleted partitions etc on HDD, made it one big partition for backintime and timeshift to use. All is good.

Now, when booting the laptop, it will start (I can hear the HDD spin up, and I see the screen come on, but nothing displays) then the laptop switches off, and immediately comes on again as above. This happens three times, on the fourth reboot the system starts normally. I have tried changing every single setting in the BIOS, no difference. I do not know much about grub, it seems OK to me, but the problem is probably there.

Please, does anybody know what I can do to fix this?

Thanks!

Some info below:

There is a lot of stuff in /boot/grub/grub.cfg, let me know if I should post it.

johann@sny:~$ grep -v '#' /etc/fstab
UUID=53b002cd-053a-43fe-9e73-9db8c9d545cf /               ext4    errors=remount-ro 0       1
UUID=9A55-24AD  /boot/efi       vfat    umask=0077      0       1
/swapfile
Drives:
  Local Storage: total: 1.82 TiB used: 379.35 GiB (20.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
    speed: 31.6 Gb/s lanes: 4 tech: SSD serial:  fw-rev: 2B4QFXO7
    temp: 35.9 C scheme: GPT
  ID-2: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
    speed: 6.0 Gb/s tech: HDD rpm: 5400 serial:  fw-rev: 0E scheme: GPT
Partition:
  ID-1: / size: 915.32 GiB used: 182.67 GiB (20.0%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
top 6 comments
sorted by: hot top controversial new old
[–] surewhynotlem@lemmy.world 4 points 10 months ago (1 children)

Old advice. Might be out of date. But when I had issues like this it was because my master boot record was on both drives, but the second one was first in the BIOS boot order. It had to cycle through that failing before it tried the MBR on the correct drive

[–] Dakspyker@lemmy.world 1 points 10 months ago (2 children)

I think it is something like this, it looks for something before timing out and moving on to the correct drive. I don't know how to fix it though. I'll start with man journalctl as was suggested elsewhere. Thanks!!

[–] PlasticExistence@lemmy.world 2 points 10 months ago

This tool might make fixing the issue easy:

https://sourceforge.net/projects/boot-repair-cd/files/boot-repair-disk-64bit.iso/download

It will scan for Grub installations and attempt to fix errors. It's possible to fix things manually, but this is often easier.

[–] marswarrior@lemmy.world 2 points 10 months ago

I recommend disconnecting the HDD to prevent installing anything on it, then repair the boot / EFI / Grub issues, then reconnect the HDD. That way you know for certain all linux partitions are on the SSD.

[–] kaleid@lemmy.world 3 points 10 months ago (1 children)

Check for errors in journalctl. If not sure what options/ flags, start with 'man journalctl', this will show you manual page for systemd log.

[–] Dakspyker@lemmy.world 1 points 10 months ago

thanks, I'll do that!