Raspberry Pi 5 NVME problems - new install

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version

G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=8
G_DIETPI_VERSION_RC=0
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN

bookworm 0

  • Kernel version | uname --all
    Linux DietPi 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture
    arm64

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
    RPi5

  • Power supply used | (EG: 5V 1A RAVpower)

Official Raspberry power supply

  • SD card used | (EG: SanDisk ultra)

Raspberry 16G

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

New install on RPi5. Using the Geekboard 4xNVME expansion HAT. First NVME slot has a 4TB stick installed. The drive seemed to install and work at first, but, after a few hours stopped working properly.

I get the following error when trying to list a directory on /mnt/nvme

ls: reading directory '.': Input/output error

dmesg is showing the following

[  385.673564] nvme nvme0: failed to mark controller live state
[  385.673569] nvme nvme0: Disabling device after reset failure: -19
[  385.689720] Aborting journal on device nvme0n1p1-8.
[  385.689753] Buffer I/O error on dev nvme0n1p1, logical block 488144896, lost sync page write
[  385.689776] JBD2: I/O error when updating journal superblock for nvme0n1p1-8.
[  385.696526] EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:84: comm kworker/u11:2: Detected aborted journal
[  385.696572] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
[  385.696589] EXT4-fs (nvme0n1p1): I/O error while writing superblock
[  385.696600] EXT4-fs (nvme0n1p1): Remounting filesystem read-only
[  385.696611] EXT4-fs (nvme0n1p1): ext4_do_writepages: jbd2_start: 256 pages, ino 160432131; err -30
[  385.696863] JBD2: Detected IO errors while flushing file data on nvme0n1p1-8
[  529.014293] EXT4-fs warning: 54 callbacks suppressed

Not really sure of the best way to try and sort this out. Any help or advice is appreciated. :slight_smile:

Steps to reproduce

  1. …
  2. …

Expected behaviour

  • …

NVME drive should function normally

Actual behaviour

  • …

suspect corrupt files / data or possible power issue?

Extra details

  • .
2

Can you check for kernel error messages

dmesg -l 0,1,2,3

Do you use original power supply?

3

dmesg returns quite a lot. I am using the original power supply.

[  385.665604] I/O error, dev nvme0n1, sector 26454784 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665603] I/O error, dev nvme0n1, sector 26799104 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665616] I/O error, dev nvme0n1, sector 26763264 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665638] I/O error, dev nvme0n1, sector 26455040 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665654] I/O error, dev nvme0n1, sector 26763520 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665668] I/O error, dev nvme0n1, sector 26455296 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665683] I/O error, dev nvme0n1, sector 26763776 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665697] I/O error, dev nvme0n1, sector 26455552 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665711] I/O error, dev nvme0n1, sector 26764032 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 2
[  385.665725] I/O error, dev nvme0n1, sector 26455808 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 2
[  385.665770] Buffer I/O error on device nvme0n1p1, logical block 3344384
[  385.665783] Buffer I/O error on device nvme0n1p1, logical block 3344385
[  385.665795] Buffer I/O error on device nvme0n1p1, logical block 3344386
[  385.665798] Buffer I/O error on device nvme0n1p1, logical block 3305472
[  385.665807] Buffer I/O error on device nvme0n1p1, logical block 3344387
[  385.665818] Buffer I/O error on device nvme0n1p1, logical block 3305473
[  385.665834] Buffer I/O error on device nvme0n1p1, logical block 3344388
[  385.665839] Buffer I/O error on device nvme0n1p1, logical block 3305474
[  385.665850] Buffer I/O error on device nvme0n1p1, logical block 3344389
[  385.665861] Buffer I/O error on device nvme0n1p1, logical block 3305475
[  385.689720] Aborting journal on device nvme0n1p1-8.
[  385.689753] Buffer I/O error on dev nvme0n1p1, logical block 488144896, lost sync page write
[  385.689776] JBD2: I/O error when updating journal superblock for nvme0n1p1-8.
[  385.696526] EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:84: comm kworker/u11:2: Detected aborted journal
[  385.696572] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
[  385.696589] EXT4-fs (nvme0n1p1): I/O error while writing superblock
[  385.696600] EXT4-fs (nvme0n1p1): Remounting filesystem read-only
[  385.696611] EXT4-fs (nvme0n1p1): ext4_do_writepages: jbd2_start: 256 pages, ino 160432131; err -30
4

Some problem from the NVME, either the disk is not healthy or the power supply is not adequate or some issue with HAT.

5

trendy- You might be right, however, i’d like to try and fix. The only thing I’m not 100% on is the ribbon between the HAT’s. Given the drive is detected and works okay for a time I think it might be alright.

6

Trial and error, I don’t see any other way :confused:

7

I believe the problem is caused by a missed step when setting up the drive. I didn’t partition or label it correctly.

The above thread is based on how I resolved this or seem to. I used Gparted to partition and lable the drive, then I had to add the user. I don’t recall doing this with the other NVME drive i setup so it amounts to learning experience :slight_smile:

8

Normally, the DietPi drive manager should also be able to format drives with the ext4 Linux file system