Press Ctrl+C to skip file checks on every boot.

[makem2]

SMART tools, there are many, don't know about file systems at all or partitions. They are useful in looking at what the drive knows about itself.

However, for nvme storage, you shouldn't use smartctl. Need to use the NVMe tool instead. It is conveniently named nvme. Regardless, both the smartctl and nvme programs aren't pre-installed, so they need to be installed on the system to be used - if you are running in a Try Ubuntu environment (off an install ISO), then you will still install them, but they will not be there the next time you boot from that same ISO. ISOs are write-once. No updates that we do when running an ISO will be retained.

Thank you, have installed nvme and wow it does have a lot of options. Will leave that for another day.

[TheFu]

Thank you, have installed nvme and wow it does have a lot of options. Will leave that for another day.

There's 1 option near the top of the "help" output ... to show SMART data. That's the only one I've ever used with NVMe storage.

Get help:

$ nvme --help | less

$ sudo nvme smart-log /dev/nvme0n1  | less

or something like that. If you have multiple nvme devices, the number at the end probably changes for each one. The nvme0n1p1 is for the 1st partition and SMART doesn't care about partitions, so don't point at those.

[makem2]

There's 1 option near the top of the "help" output ... to show SMART data. That's the only one I've ever used with NVMe storage.

Get help:

$ nvme --help | less

$ sudo nvme smart-log /dev/nvme0n1  | less

or something like that. If you have multiple nvme devices, the number at the end probably changes for each one. The nvme0n1p1 is for the 1st partition and SMART doesn't care about partitions, so don't point at those.

Thank you. Real life catches up at the moment but I will be revisiting shortly.

[makem2]

There's 1 option near the top of the "help" output ... to show SMART data. That's the only one I've ever used with NVMe storage.

Get help:

$ nvme --help | less

$ sudo nvme smart-log /dev/nvme0n1  | less

or something like that. If you have multiple nvme devices, the number at the end probably changes for each one. The nvme0n1p1 is for the 1st partition and SMART doesn't care about partitions, so don't point at those.

I have 3 nvme and all checked. all identical, no errors or anything different.

Very strange because all checks negative yet I still have to press Ctrl+C. The period I had to do that seems to be getting longer as if it is checking and taking longer to complete the check.

[TheFu]

What are the settings for each file system? Might they be set run an fsck more often than every 30 days? For ext4, you can see that using the tune2fs tool.

[1fallen]

I lost site of this thread, but I disabled mine boot wise.

 sudo tune2fs -c 0 /dev/sdb2
tune2fs 1.47.0 (5-Feb-2023)
Setting maximal mount count to -1

To re-enable if needed:

# tune2fs -c 1 -f /dev/sdx2

But do change the /dev/sd?? to your ext4 partition.

[TheFu]

tune2fs is for the file system, wherever that resides. It can be on a partition or inside a logical volume. Also, the tune2fs command only works with ext2/3/4 file systems.
From the manpage:

NAME
       tune2fs  -  adjust  tunable  filesystem  parameters on ext2/ext3/ext4 filesystems
...
DESCRIPTION
       tune2fs allows the system administrator to adjust var‐
       ious tunable  filesystem  parameters  on  Linux  ext2,
       ext3,  or  ext4  filesystems.   The  current values of
       these options can be displayed by using the -l  option
       to  tune2fs(8)  program,  or  by using the dumpe2fs(8)
       program.

Something similar should exist for others, but tuning those file systems would use different commands. BTRFS and ZFS would definitely have different methods, for example.

[makem2]

As I have previously said, I have 3 nvme drives.

2 of those are formatted NTFS for interaction with Windows during Covid for gaming to fill in the time.

Today in /ect/fstab I '#' out both of the nvme drives and noticed no change in booting. I still had the file system check warning.

The third nvme /dev/nvme0n1 has Ubuntu and Windows 10 side by side. Thw Windows partition is formatted NTFS.

On that nvme are my /home and a small ext4 partition for games.

If 'removing' the two NTFS drive from the equation and still the file system error occurs, does it not point to that particular nvme drive?

All checks on that drive have proved negative but concentration has been on the NTFS drives.

I am thinking of searching the output of dmesg to find any error but do not know what keyword to look for in dmesg | grep <keyword>.

I will use journalctl | grep "error" to see what that turns up.

The machine was last re-booted with both nvme drives '#' out of the fstab.

[makem2]

What are the settings for each file system? Might they be set run an fsck more often than every 30 days? For ext4, you can see that using the tune2fs tool.

I have tried the tool but cannot seem to get the correct syntax correct to output the current settings. Even the Linux man page does not seem to work for me.

makem@makem-22:~$ tune2fs  -i
tune2fs 1.47.0 (5-Feb-2023)
tune2fs: option requires an argument -- 'i'
Usage: tune2fs [-c max_mounts_count] [-e errors_behavior] [-f] [-g group]
	[-i interval[d|m|w]] [-j] [-J journal_options] [-l]
	[-m reserved_blocks_percent] [-o [^]mount_options[,...]]
	[-r reserved_blocks_count] [-u user] [-C mount_count]
	[-L volume_label] [-M last_mounted_dir]
	[-O [^]feature[,...]] [-Q quota_options]
	[-E extended-option[,...]] [-T last_check_time] [-U UUID]
	[-I new_inode_size] [-z undo_file] device
makem@makem-22:~$ dumpe2fs
dumpe2fs 1.47.0 (5-Feb-2023)
Usage: dumpe2fs [-bfghimxV] [-o superblock=<num>] [-o blocksize=<num>] device
makem@makem-22:~$ dumpe2fs -i
dumpe2fs 1.47.0 (5-Feb-2023)
Usage: dumpe2fs [-bfghimxV] [-o superblock=<num>] [-o blocksize=<num>] device
makem@makem-22:~$

[makem2]

As I have previously said, I have 3 nvme drives.

2 of those are formatted NTFS for interaction with Windows during Covid for gaming to fill in the time.

Today in /ect/fstab I '#' out both of the nvme drives and noticed no change in booting. I still had the file system check warning.

The third nvme /dev/nvme0n1 has Ubuntu and Windows 10 side by side. Thw Windows partition is formatted NTFS.

On that nvme are my /home and a small ext4 partition for games.

If 'removing' the two NTFS drive from the equation and still the file system error occurs, does it not point to that particular nvme drive?

All checks on that drive have proved negative but concentration has been on the NTFS drives.

I am thinking of searching the output of dmesg to find any error but do not know what keyword to look for in dmesg | grep <keyword>.

I will use journalctl | grep "error" to see what that turns up.

The machine was last re-booted with both nvme drives '#' out of the fstab.

I have made a dmesg and journalctl record before I need to reboot:


https://dpaste.com/ESETH82TS

https://dpaste.com/HSDXXBM4A

I appreciate that in the journalctl many of the errors are not errors but it may contain some relevant errors hopefully.

Although I am not sure what to look for I will see what I find.

I have made another post about failing to run fsck: https://ubuntuforums.org/showthread.php?t=2501421

I did this because of the 'rcs' errors which I have a vague memory is something to do with Wayland.

I hope this does not offend. I do check back.