LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 04-24-2021, 10:38 AM   #1
GustavusHolmiensis
LQ Newbie
 
Registered: Apr 2021
Posts: 13

Rep: Reputation: Disabled
Computer with Debian 10.6 won't boot after several freezing incidents


I have a custom built computer with the following hardware specs:

*Motherboard: ASRock B550 Pro4
*Processor: AMD Ryzen 5 3600 6-Core
*RAM: Two 8 GiB DDR4-2400 modules for a total of 16 GiB RAM
*Storage: Kingston SA2000M8500G 500 GiB NVMe SSD mounted in an M.2 port
*Graphics card: ASUS PCIe GT710-SL-2GD5

I installed Debian 10.6 on the computer, and it ran well for a while. I recall installing Nvidia drivers at some point, and that I had trouble afterwards because I forgot to purge the nouveau drivers. Unfortunately, I don't remember if I ended up removing the Nvidia drivers or not in order to solve the problem.

At a few occasions, at least two but possible more, I've had the computer seemingly freeze completely. It did not respond to keyboard or mouse input, and I had to reboot the computer by pressing the power button.

On at least one of these occasions, I was participating in a video conference over Zoom. At this occasion, the video and sound feed from my computer to the other participant still worked, and I was also able to receive the sound feed from the other participant. Aside from that, the computer was completely frozen and I had to attempt a reboot by pressing the power button.

However, I have not been able to boot the computer since. If I try, the following happens:

*I get the following info on the screen:
Code:
 [    0.004219] do_IRQ: 1.55 No irq handler for vector
 [    0.004219] do_IRQ: 2.55 No irq handler for vector
 [    0.004219] do_IRQ: 3.55 No irq handler for vector
 [    0.004219] do_IRQ: 4.55 No irq handler for vector
 [    0.004219] do_IRQ: 5.55 No irq handler for vector
 [    0.004219] do_IRQ: 6.55 No irq handler for vector
 [    0.004219] do_IRQ: 7.55 No irq handler for vector
 [    0.004219] do_IRQ: 8.55 No irq handler for vector
 [    0.004219] do_IRQ: 9.55 No irq handler for vector
 [    0.004219] do_IRQ: 10.55 No irq handler for vector
 /dev/nvme0n1p2: recovering journal
 /dev/nvme0n1p2: clean, 626654/4890624 files, 6477569/19531264 blocks
 [    3.950331] sp5100-tco sp5100-tco: Watchdog hardware is disabled
 fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress
[Note that the do_IRQ messages have always appeared, before the problems started to appear]

*I press Ctrl+C but nothing happens. After waiting for a while, I get some messages that seem related to my NVMe SSD:
Code:
 [  242.827095] INFO: task jbd2/nvme0n1p2-:313 blocked for more than 120      
  seconds.
 [  242.827114]       Not tainted 4.19.0-14-amd64 #1 Debian 4.19.171-2
 [  242.827120] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"   
  disables this message.
 [  242.827222] INFO: task fsck.ext4:504 blocked for more than 120 
  seconds.
 [  242.827228]       Not tainted 4.19.0-14-amd64 #1 Debian 4.19.171-2
 [  242.827233] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"   
  disables this message.
 [  242.827285] INFO: task kworker/0:2H:614 blocked for more than 120 
  seconds.
 [  242.827290]       Not tainted 4.19.0-14-amd64 #1 Debian 4.19.171-2
 [  242.827295] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"   
  disables this message.
 [246.623079] nvme nvme0: Device not ready: aborting reset
*After waiting a little more (or possible after pressing Esc), I get a lot
of messages, mostly consisting of a repeat of the following:
Code:
           Unmounting /boot/efi/...
           Deactivating swap /dev/disk/by-uuid/4fc3549b-84a0-4b33-
   bf8a-9884c65e7958.
  [FAILED] Failed unmounting /boot/efi...
  [FAILED] Failed deactivating swap /dev/disk/by-uuid/4fc3549b-84a0-4b33-
   bf8a-9884c65e7958.
*The system then gets stuck after the following message:
Code:
  [OK] Stopped File System Check on /dev/disk/by-uuid/A909-2B14
I have tried to further diagnose the error by booting in rescue mode from a Debian live USB. Running fdisk -l gives the following output (sans stuff about the USB device):

Code:
Device     Boot   Start      End   Sectors  Size  Id  Type
/dev/sda1  *          0  7758431   7758432  3.7G   0  Empty
/dev/sda2         23680    29343      5664   2.8M  ef EFI (FAT-12/16/32)
I try to mount /dev/sda1 for my root system, but it fails.

Any suggestions for how I might solve this issue would be greatly appreciated!

Last edited by GustavusHolmiensis; 04-26-2021 at 09:12 AM. Reason: Cleaned up the formatting.
 
Old 04-24-2021, 08:12 PM   #2
michaelk
Moderator
 
Registered: Aug 2002
Posts: 26,517

Rep: Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224
sda1 is your USB i.e. the live system so you can't mount it. From the posted error messages nvme appears to be recognized at first but then just dies. I am guessing it isn't listed in the output of fdisk.

I am guessing it is broken.
 
1 members found this post helpful.
Old 04-24-2021, 08:46 PM   #3
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
Blog Entries: 1

Rep: Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196
When you booted from live USB, the USB was assigned /dev/sda. /dev/sda1 was the / filesystem on USB already mounted. Running fdisk -l from the USB boot should have shown your Kingston as /dev/nvme0n1. The error messages seem to suggest the Kingston has failed.
Code:
blkid
efibootmgr -v
from USB boot should shed additional light on the meaning of A909-2B14.

Try a normal boot again, but at the Grub menu, hit the E key and append either nomodeset or 3 to the end of the line that begins linu. If the NVME boot problem is related to graphics, either or both may enable more troubleshooting steps to be taken. The 3 stops the GUI environment from trying to startup, while nomodeset may facilitate troubleshooting when graphics drivers are an issue.

You may have a root filesystem that is corrupted beyond what auto fsck on startup can handle. If parted -l on the USB boot shows the presence of the NVME device, manual fsck from a USB boot may be able to save its root filesystem.

When you post command input and output, wrap it in code tags as you can see I have done by clicking on the "Quote" button.
 
1 members found this post helpful.
Old 04-26-2021, 09:04 AM   #4
GustavusHolmiensis
LQ Newbie
 
Registered: Apr 2021
Posts: 13

Original Poster
Rep: Reputation: Disabled
Thank you for your feedback, and apologies for my late reply. I attempted to reply yesterday, but something went wrong. The thread disappeared for a while, so I started a new thread here: https://www.linuxquestions.org/quest...sd-4175694259/. However, I expect the new thread to be deleted since it's no longer needed.

I have now tried the following:

*Try a normal boot, and hit E in the Grub menu. I get the following:
Code:
setparams 'System setup'

        fwsetup
Thus, there is no line beginning with "linu". Should I add such a line myself?

*I then rebooted the computer in rescue mode from my debian live USB. This time, my NVMe was apparently detected. In the window where I pick a device to use as root file system, I got the following:
Code:
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
/dev/nvme0n1p4
/dev/sda1
/dev/sda2
Assemble RAID array
Do not use a root file system.
*Because I was unsure what to do, I picked "Do not use a root file system", and opened an interactive shell. I ran blkid and got the following:
Code:
/dev/nvme0n1: PTUUID="9f5a6318-2b4e-4ad8-b58d-269e7445b202" PTTYPE="gpt"
/dev/nvme0n1p1: UUID="A909-2B14" TYPE="vfat" PARTUIID="fb0938f6-2d49-4895-902d-73d38110a938"
/dev/nvme0n1p2: UUID="d163bcb3-a38e-4691-a183-a27b729d57c6" TYPE="ext4" PARTUUID="b7e6a481-400d-4be1-bd25-b023cfe8287"
/dev/nvme0n1p3: UUID="4fc3549b-84a0-4b33-bf8a-9884c65d7958" TYPE="swap" PARTUUID="3dee7513-4f57-4c26-bc01-88351440246a"
/dev/nvme0n1p4: UUID="52684e96-3941-438e-a85a-bbf9458fca70" TYPE="ext4" PARTUUID="edb45be3-beaa-408e-9963-f78d4c3ee6b5"
/dev/sda1: UUID=2020-09-26-11-15-10-00" LABEL="Debian 10.6.0 amd64 1" TYPE="iso9660" PTUUID="7533593e" PTTYPE="dos" PARTUUID="7533593e-01"
/dev/sda2: SEC_TYPE="msdos" UUID="6201-48E3" TYPE=vfat" PARTUUID="7533593e-02"
*Next, I tried to run efibootmgr -v, but the command was not found.

*I then ran parted -l, and got the following:
Code:
Warning: The driver descriptor says the physical block size  is 2048 bytes, but Linux says it is 512 bytes.
Ignore/Cancel?
I picked Cancel, and then got the following:
Code:
Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sda: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Model: KINGSTON SA2000M8500G (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  538MB   537MB   fat32                 boot, esp
 2      538MB   80.5GB  80.0GB  ext4
 3      80.5GB  101GB   20.0GB  linux.swap(v1)
 4      101GB   500GB   400GB   ext4
*Since it appeared that the NVMe disk was now found, I tried a normal reboot. I got the following info on the screen. Note, that it is not identical to what I had before.
Code:
 [    0.004218] do_IRQ: 1.55 No irq handler for vector
 [    0.004218] do_IRQ: 2.55 No irq handler for vector
 [    0.004218] do_IRQ: 3.55 No irq handler for vector
 [    0.004218] do_IRQ: 4.55 No irq handler for vector
 [    0.004218] do_IRQ: 5.55 No irq handler for vector
 [    0.004218] do_IRQ: 6.55 No irq handler for vector
 [    0.004218] do_IRQ: 7.55 No irq handler for vector
 [    0.004218] do_IRQ: 8.55 No irq handler for vector
 [    0.004218] do_IRQ: 9.55 No irq handler for vector
 [    0.004218] do_IRQ: 10.55 No irq handler for vector
 [    3.441147] sd 6:0:0:0:0: [sda] No Caching mode page found
 [    3.441147] sd 6:0:0:0:0: [sda] Assuming drive cache: write through
 /dev/nvme0n1p2: recovering journal
 /dev/nvme0n1p2: clean, 626654/4890624 files, 6477569/19531264 blocks
 [    4.010116] sp5100-tco sp5100-tco: Watchdog hardware is disabled
 fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress
*After waiting for a while, I got the following (repeated a few times):
Code:
 [  242.827430] INFO: task jbd2/nvme0n1p2-:313 blocked for more than 120      
  seconds.
 [  242.827449]       Not tainted 4.19.0-14-amd64 #1 Debian 4.19.171-2
 [  242.827455] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"   
  disables this message.
*After waiting a little more, I got a lot
of messages, mostly consisting of a repeat of the following:
Code:
           Unmounting /boot/efi/...
           Deactivating swap /dev/disk/by-uuid/4fc3549b-84a0-4b33-
   bf8a-9884c65e7958.
  [FAILED] Failed unmounting /boot/efi...
  [FAILED] Failed deactivating swap /dev/disk/by-uuid/4fc3549b-84a0-4b33-
   bf8a-9884c65e7958.
*I hit Esc, and got the following:
Code:
[  OK  ] Stopped File System Check on /dev/disk/by-uuid/A909-2B14.
fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress.
*I left the system for a few hours, in case it was running a file system check. Nothing seemed to happen, so I rebooted using Alt+SysReq+B. Once again, I booted in rescue mode from my live Debian USB. This time, the NVMe was "not" found. In the window where I pick a device to use as root file system, I get the following:
Code:
/dev/sda1
/dev/sda2
Assemble RAID array
Do not use a root file system.

Last edited by GustavusHolmiensis; 04-26-2021 at 09:12 AM.
 
Old 04-26-2021, 10:26 AM   #5
michaelk
Moderator
 
Registered: Aug 2002
Posts: 26,517

Rep: Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224Reputation: 6224
The fact that sometimes the NVMe drive is recognized and sometime not usually after the system has been running indicates a hardware problem. I suspect the drive.

Last edited by michaelk; 04-26-2021 at 10:28 AM.
 
1 members found this post helpful.
Old 04-26-2021, 10:38 AM   #6
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
Blog Entries: 1

Rep: Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196
A909-2B14, referred to in #1, is the filesystem label for the ESP partition on /dev/nvme0n1p1. This means Debian is configured/installed in UEFI mode. For full support for the NVME while booted to rescue media, it needs to be booted in UEFI mode, which was not the case when the efibootmgr not found message was produced. I suggest entering BIOS to disable CSM (MBR compatibility support mode), so that booting will only take place in UEFI mode.

Based upon my experience booting many different Debian installations on different PCs, "[OK] Stopped File System Check on /dev/disk/by-uuid/A909-2B14" suggests boot actually completed, but only after a login prompt was erased from the tty1 screen, and that the login greeter (GDM or LightDM or SDDM or KDM or ???) failed due to X not starting. This erased login prompt on tty1 is routine here, quite some seconds after boot activity has stopped in multi-user.target. If you can reach this point again, try keying in Ctrl-Alt-F3. If successful, indicated by a distro identifier and login prompt, you have booted successfully, but X is broken. So, make this your next try.

If no progress after plenty of waiting, reboot, and try the E key as per post #3 if the Grub menu appears. If the Grub menu doesn't appear, trying getting the USB booted in UEFI mode to try
Code:
e2fsck /dev/nvme0n1p2
and then report back for further directions. At this point you might want to contact Kingston to report your trouble and ask whether this sounds like the device is faulty.

Quote:
Code:
setparams 'System setup'

        fwsetup
is an unfamiliar message probably triggered by /etc/grub.d/30_uefi-firmware, which seems to be a component of generating a new Grub menu using grub-mkconfig. It may be happening as a result of a corrupted or missing /boot/grub/grub.cfg. Without a valid /boot/grub/grub.cfg file, the expected boot menu fails to appear, and thus the E key does not have the expected effect.

Quote:
...I got the following:
Code:
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
/dev/nvme0n1p4
/dev/sda1
/dev/sda2
Assemble RAID array
Do not use a root file system.
If you see this again, select /dev/nvme0n1p2.
 
1 members found this post helpful.
Old 04-26-2021, 10:52 AM   #7
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675

Rep: Reputation: Disabled
As michaelk said, hardware problem. Disappearing and reappearing piece of hardware cannot be fixed with software. There is a slim chance re-seating it could fix the issue, it is at least worth a try. Then warranty replacement.
 
1 members found this post helpful.
Old 04-26-2021, 02:46 PM   #8
GustavusHolmiensis
LQ Newbie
 
Registered: Apr 2021
Posts: 13

Original Poster
Rep: Reputation: Disabled
Thank you very much for your replies. I understand that there may indeed be a hardware fault, but I would like to investigate further, if possible. I have therefore followed the instructions by mrmazda, and done the following:

*Again, I tried booting as normal. After eventually reaching "[OK] Stopped File System Check on /dev/disk/by-uuid/A909-2B14" I entered Ctrl+Alt+F3. I did not get a proper prompt however, but only a blinking underscore in the upper left corner.

*I then rebooted by entering Alr+SysReq+B. I was met with the following message:
Code:
Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key.
*I turned the computer off using the power button, then booted it, entered the Grub menu and hit "E". I got the following output
Code:
setparams 'Debian GNU/Linux'

        load_video
        insmod gzio
        if  [ x$grub_platform = xxen ]; then insmod xzio; insmod izopio; fi
        insmod part_gpt
        insmod ext2
        if [x $feature_platform_search_hint = xy ]; then
         search --no-floppy --fs-uuid --set=root  d163bcb3-a38e-4691-a183-a27b729d57c6
        else
         search --no-floppy --fs-uuid --set=root d163bcb3-a38e-4691-a183-a27b729d57c6
        fi
        echo       'Loadin^ Linux 4.19.0-14-amd64 ...'
        linux      /boot/vmlinuz-4.19.0-14-amd64 root=UUID=d163bcb3-a38e-4691-a183-a27b729d57c6 ro quiet
        echo       'Loading^ initial ramdisk ...'
        initrd      /boot/initrd.img-4.19.0-14-amd64
^The word "Loading" is not actually a quote, but a translation from my local language.

I was unsure what to do (technically, the line with linux starts with "linu", but I assume this is not the line that was intended in post #3), so I hit F10 in an attempt to boot, but to no avail.

*I disabled CSM in the boot menu, and started to boot into rescue mode from my live Debian USB. Again, I got the following list of devices
Code:
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
/dev/nvme0n1p4
/dev/sda1
/dev/sda2
Assemble RAID array
Do not use a root file system.
As suggested, I selected /dev/nvme0n1p2 and received the following question:
Code:
The installed system appears to use a separate /boot/efi partition.

It is normally a good idea to mount it as it will allow operations such as reinstalling the boot loader. However, if the file system on /boot/efi is corrupt then you may want to avoid mounting it.

Mount separate /boot/efi partition?
This is where I currently am. Any suggestions on how to proceed? I apologize if my questions are a bit "nooby". I just want to make sure I don't mess up my system.
 
Old 04-26-2021, 06:10 PM   #9
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
Blog Entries: 1

Rep: Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196
Quote:
Originally Posted by GustavusHolmiensis View Post
*I turned the computer off using the power button, then booted it, entered the Grub menu and hit "E". I got the following output
Code:
...
        linux      /boot/vmlinuz-4.19.0-14-amd64 root=UUID=d163bcb3-a38e-4691-a183-a27b729d57c6 ro quiet
...

Quote:
...
I was unsure what to do (technically, the line with linux starts with "linu", but I assume this is not the line that was intended in post #3), so I hit F10 in an attempt to boot, but to no avail.
Wrong assumption. The string "linu" can begin either "linux" or "linuxefi". After the "quiet" appearing there is where to append as directed in post #3.

Quote:
*I disabled CSM in the boot menu, and started to boot into rescue mode from my live Debian USB. Again, I got the following list of devices
Code:
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
/dev/nvme0n1p4
/dev/sda1
/dev/sda2
Assemble RAID array
Do not use a root file system.
As suggested, I selected /dev/nvme0n1p2 and received the following question:
Code:
The installed system appears to use a separate /boot/efi partition.

It is normally a good idea to mount it as it will allow operations such as reinstalling the boot loader. However, if the file system on /boot/efi is corrupt then you may want to avoid mounting it.

Mount separate /boot/efi partition?
This is where I currently am. Any suggestions on how to proceed? I apologize if my questions are a bit "nooby". I just want to make sure I don't mess up my system.
I expect if you answer yes, the installed Debian 10.6 will attempt to boot.

I wonder if this ASRock has a BIOS quirk where a full powerdown boot may be required for good behavior following configuration changes, or following a USB stick boot? From any Linux UEFI boot, please copy and paste here input/output from:
Code:
sudo efibootmgr -v
If it's easier, you can do instead:
Code:
sudo efibootmgr -v | pastebinit
 
1 members found this post helpful.
Old 04-27-2021, 08:03 AM   #10
GustavusHolmiensis
LQ Newbie
 
Registered: Apr 2021
Posts: 13

Original Poster
Rep: Reputation: Disabled
Thanks for all the help, mrmazda!

Ok, I picked 'No' and executed a shell in /dev/nvme0n1p2.

Ok, I'll try to stop the GUI through Grub next time I reboot. However, I don't want to reboot yet since I currently have a shell mounted on /dev/nvme0n1p2, and want to make sure I extract as much information as possible. For the same reason, I have not been able to run e2fsck /dev/nvme0n1p2 yet.

I did however run efibootmgr -v. I got the following output:
Code:
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0005.0006.0007
Boot0005* debian        HD(1,GPT,fb0938f6-2d49-4895-902d-73d38110a938,0x800,0x100000)/File(\EFI\DEBIAN\GRU
Bx64.EFI)..BO
Boot006* UEFI: SanDisk Cruzer Blade 8.02        PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(6.0)/CDROM(1,0x
5c80,0x5880)..BO
Boot007* UEFI: SanDisk Cruzer Blade 8.02,  Partition 2  PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(6,0)/HD
(2,MBR,0x7533593e,0x5c80,0x1620)..BO

Last edited by GustavusHolmiensis; 04-27-2021 at 08:06 AM. Reason: Fixed the formatting
 
Old 04-28-2021, 04:49 PM   #11
GustavusHolmiensis
LQ Newbie
 
Registered: Apr 2021
Posts: 13

Original Poster
Rep: Reputation: Disabled
Hi again,

I have tried a few more things, but I have not found a solution. Do you have any comments on the output from efibootmgr -v in post #10 or the points below?

*I went back in the installation process and executed a shell without using a root file system, in order to be able to run e2fsck /dev/nvme0n1p2. Doing so, I got the following:
Code:
e2fsck /dev/nvme0n1p2
e2fsck 1.44.5 (15-Dec-2018)
/dev/nvme0n1p2: clean, 626655/4890624 files, 6477570/19531264 blocks.
*I tried again to boot the computer normally, but it didn't work.

*I rebooted, opened Grub, hit 'E' and added nomodeset at the end of the line beginning with linux (see post #8). I hit F10 in order to boot, but got the same messages as in post #4. The system stopped at the message "[OK] Stopped File System Check on /dev/disk/by-uuid/A909-2B14". I entered Ctrl+Alt+F3 and did not get a proper prompt however, but only a blinking underscore in the upper left corner.

*I rebooted and repeated the above steps, but 3 to the same line instead of nomodeset. Still the result was the same as in the above point.

*I turned off the computer and removed the NVMe SSD to inspect for damage. I found no damage, reinserted the NVMe SSD and tried to boot. Still, it didn't work.

*Again, I booted in rescue mode from my Debian live USB. I am now again in the position where the NVMe SSD does not appear to be detected.
 
Old 04-28-2021, 05:30 PM   #12
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
Blog Entries: 1

Rep: Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196
Regarding efibootmgr, I was looking for stale entries or corruption. I recognized neither in the posted output.

Regarding appending 3 or nomodeset: You did ensure that there was a space entered between what was there and what you added each time, correct? Was the line wrapped? A wrapped line is indicated by "" on the "linu" line. If yes, it necessitates you make your addition before the line break that is followed by "initrd" on the next line, not on the visibly same line as "linu".

Lastly, if necessary, please bring the failure to appear of the NVME to the attention of Kingston support for recommendations. Likewise to ASRock. Also, check for an available motherboard BIOS upgrade, and install if one is.
 
1 members found this post helpful.
Old 04-29-2021, 12:19 PM   #13
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
I have the exact same motherboard and processor, the only difference is I am using memory with 3600 speed.

When I initially booted fedora 33 with that mobo & processor I got the same messages about the IRQs which (I think) were fixed with a kernel update. I am using fedora and I think the 5.11 kernel was the solution to those messages. It also may have been a firmware update on the board, I'm not exactly certain.

You are using an nvme M.2 drive. Which connector did you attach it to? The one between the pcie slots which is a dedicated M.2 connector? Or the one lower and closer to the sata ports? That one is using the pcie/sata bus and disables sata ports 5 & 6. There is a difference in the architecture of the bus supplying those 2 ports and it is possible that may be the issue.

Check the manual, pages 39 and 42 for the details of the supported cards to verify you have installed a supported device.

It also, since this appears to be somewhat intermittent, possible that one of the card pins is not making good consistent contact in the connector and re-seating it may fix the issue.

Last, I also suggest, as has been noted before, that you run a manual fsck on the root filesystem (nvme0n1p2)
 
1 members found this post helpful.
Old 04-29-2021, 02:03 PM   #14
GustavusHolmiensis
LQ Newbie
 
Registered: Apr 2021
Posts: 13

Original Poster
Rep: Reputation: Disabled
Thank you both for your replies!

@mrmazda:

Regarding appending 3 or nomodeset:

To make sure, I tried this once again. Aside from the translation of the equivalent of 'Loading' in my local language, the Grub editor looks as in post #8.

*I first added nomodeset after quiet (with a space before) on the line starting with linux and before the line starting with echo, so that it looked as follows,
Code:
...
        linux      /boot/vmlinuz-4.19.0-14-amd64 root=UUID=d163bcb3-a38e-4691-a183-a27b729d57c6 ro quiet nomodeset
        echo       'Loading initial ramdisk ...'
        initrd      /boot/initrd.img-4.19.0-14-amd64
and then hit F10. Just to clarify: there is no need to further save the above change before hitting F10, right?

*I similarly tried adding 3 after quiet (with a space before) on the line starting with linux and before the line starting with echo, so that it looked as follows
Code:
...
        linux      /boot/vmlinuz-4.19.0-14-amd64 root=UUID=d163bcb3-a38e-4691-a183-a27b729d57c6 ro quiet 3
        echo       'Loading^ initial ramdisk ...'
        initrd      /boot/initrd.img-4.19.0-14-amd64
,
and then hit F10.

*In either case, the computer wouldn't boot. However, after trying with nomodeset, I actually got some messages which I had not seen before. Specifically, I got the the following:
Code:
[  489.071701] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[  489.071756] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.071041] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.071905] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.071991] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.072051] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.072137] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.072190] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.072277] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.072336] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.072421] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.072531] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.072540] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm  (swapoff): reading directory iblock 0
[  489.072617] EXT4-fs EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.072704] EXT4-fs (nvme0n1p2): previous I/O error to superblock detected
[  489.072757] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd systemd-journal: reading directory iblock 0
[  489.072806] EXT4-fs (nvme0n1p2): I/O error while writing superblock
[  489.072952] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
[  489.903725] nvme nvme0: failed to set APST feature (-19)
[  519.906204] EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1449: inode #2: comm systemd-journal: reading directory iblock 0
...
,
where the ... indicate that the last message was repeated several times.

@computersavvy

*Yes, I should probably look into the IRQ messages also, but I'm unsure if they connect to the present problem.

*I installed my drive in the connector between the PCIe slots, i.e. the connector called M2_1 in the manual (see: https://download.asrock.com/Manual/B550%20Pro4.pdf p.7 and p.35). By the way, you are supposed to keep the grey thick pad on the bottom of the heat sink, right? Note that I think there was an green film on the grey pad initially. I have removed this green film but kept they grey pad, which I think is part of the heat sink.

*I actually note in the list of supported drives (https://www.asrock.com/mb/AMD/B550%2...ex.asp#Storage) that my drive, Kingston SA2000M8/500G is not listed. Perhaps this could be an issue. Note, however that other PCIe3 x4 drives are supported. It's also strange that the drive worked for at least about a month or so.

*Could you please clarify what you mean by running a manual fsck? Note that I ran e2fsck /dev/nvme0n1p2 (see post #11) at one point from my Debian live USB in rescue mode.
 
Old 04-29-2021, 06:59 PM   #15
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
Blog Entries: 1

Rep: Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196Reputation: 2196
OP, your Grub stanza appending looks all good, nothing to be saved. I agree you must have a Kingston or motherboard firmware or hardware problem.
 
1 members found this post helpful.
  


Reply

Tags
debian 10, nvme, ssd


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: How to approach router (and other) network incidents LXer Syndicated Linux News 0 01-22-2020 02:03 PM
What do you use to track security incidents? abefroman Linux - Security 8 10-03-2010 10:41 AM
A series of unfortunate incidents ... DavidMcCann General 11 05-12-2010 02:16 PM
My computer screen keeps freezing and I have to keep turning the computer on and off breddyy Linux - Hardware 3 01-23-2008 01:43 AM
Incidents recorder/manager nderitualex Linux - Software 1 04-01-2005 09:32 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 05:48 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration