Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

boot issue, do I have a hardware problem?

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
graemev2
Posts: 95
Joined: 2019-01-08 17:28
Has thanked: 2 times

boot issue, do I have a hardware problem?

#1 Post by graemev2 »

From time to time I've had trouble with boot . No obvious pattern. Boots fine dozens of times then suddenly fails. Recently shutdown, hour later rebooted and it failed. I need to show a photo as there are no logs.

Previously I booted a "live CD (USB stick)" and found various fsck(8) errors and the missing grub files, had to reinstalled grub, This time the live CD can find no issues and it's not grub reporting an error:

Image

Now this is the /boot disk. (/dev/sdb1) So my 1st guess would be the device is not responding, but following the long timeout (see photo)
it eventually gets to "enter root password or ctrl-D ...hitting ctrl-D gets me to a normal desktop. I can mount /boot just fine. It passes fsck(8) all seems fine with it. the UUID also appears in the list:

Code: Select all

graeme@real:~$ sudo ls -l /dev/disk/by-uuid/ | grep 0732
lrwxrwxrwx 1 root root 10 Jun  5 18:49 b1aa87e8-8e0e-48d6-aa7a-062472100732 -> ../../sdb1

graeme@real:~$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 447.14 GiB, 480113590272 bytes, 937721856 sectors
Disk model: SanDisk SSD PLUS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x53e4e91d

Code: Select all

root@real:/var/log# mount  | grep boot
/dev/sdb1 on /boot type ext4 (rw,relatime)

root@real:/var/log# ls -l /boot
total 248149
-rw-r--r-- 1 root root       83 Dec  9 05:54 System.map-6.0.0-6-amd64
-rw-r--r-- 1 root root       83 Apr  8 16:36 System.map-6.1.0-7-amd64
-rw-r--r-- 1 root root       83 Apr 22 19:48 System.map-6.1.0-8-amd64
-rw-r--r-- 1 root root       83 May  8 21:16 System.map-6.1.0-9-amd64
drwxr-xr-x 3 root root     1024 May 23 15:52 boot
...elided...

Code: Select all

root@real:/var/log# cat /etc/*release*
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
...
Attachments
sid-boot-errors.jpg

User avatar
kent_dorfman766
Posts: 529
Joined: 2022-12-16 06:34
Location: socialist states of america
Has thanked: 56 times
Been thanked: 69 times

Re: boot issue, do I have a hardware problem?

#2 Post by kent_dorfman766 »

image shows that you've got a disk that is sometimes unreachable when it attemtps to mount filesystems. That's why your going to emergency mode.

User avatar
graemev2
Posts: 95
Joined: 2019-01-08 17:28
Has thanked: 2 times

Re: boot issue, do I have a hardware problem?

#3 Post by graemev2 »

Tried the following:

edited /etc/fstab:

Code: Select all

#UUID=b1aa87e8-8e0e-48d6-aa7a-062472100732  /boot           ext4        defaults          0       2
LABEL=boot  /boot           ext4        defaults          0       2
In case it was some kind of race.. creating the by-uuid link
Didn't help. Then tried:

Code: Select all

UUID=b1aa87e8-8e0e-48d6-aa7a-062472100732  /boot           ext4        noauto,defaults          0       2
This comes up fine, but obviously without /boot mounted (so won't create a new initrd correctly, not a "solution")

Right now it's a "hard fault" (not the case in the past) ...so

1: It's not available late in the boot (when systemd is mounting fstab)
2: it is available post boot (when I do mount /boot)
...but
3: It is available very early in boot, when grub is accessing it? ...it must have read the kernel and initrd from there ?

so available ...unavailable ...available ... now in a reliable pattern ...seems odd.

User avatar
graemev2
Posts: 95
Joined: 2019-01-08 17:28
Has thanked: 2 times

Re: boot issue, do I have a hardware problem?

#4 Post by graemev2 »

Golly , found it.

Earlier in the day I added:

Code: Select all

root@real:/etc/udev/rules.d/DONT# cat /etc/udev/rules.d/98-usb-disk-mount.rules
#
# GPV 05jun23 from: https://unix.stackexchange.com/questions/560358/how-do-i-automount-usb-drives-in-linux-debian
# GPV don't do it, it causes: https://forums.debian.net/viewtopic.php?t=154795

ACTION=="add", KERNEL=="sd?[0-9]", SUBSYSTEM=="block", RUN+="/bin/systemctl start local-fs.target"
The comment in the file gives the reason I added it. It worked great with it recognising my camera but had this huge downside.

I've just added added removed this rule TWICE, rebooting each time . With the rule it times out mounting /boot, without the rule it boots clean .

(I'll add a comment on stackexchange)

...I guess I could probably limit it to just USB devices ...assuming I won't be booting from them (which probably not a safe assumption)

Post Reply