Hello, here is the Samsung and Patriot NVME SSD SMART RAW output. Patriot PCIe Gen3 x4 NVMe SSD: sudo smartctl -a /dev/nvme1n1p1 smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.14.0-37-generic] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: Patriot M.2 P300 512GB Serial Number: P300NDCXXXXXXXXX17 Firmware Version: SN21875 PCI Vendor/Subsystem ID: 0x1e4b IEEE OUI Identifier: 0x3a5a27 Total NVM Capacity: 512,110,190,592...
Hi Jamie, Thanks for the quick fix, I've applied the commit fix manually and I will leave an attached screenshot for reference, I will also provide the SMART output status for two NVME brand drives Gen3x4 at the bottom for further reference. Regards
Hi Jamie, I've applied the commit fix manually and I will leave an attached screenshot for reference, I will also provide the SMART output status for two NVME brand drives Gen3x4 at the bottom for further reference. Regards
Hi Jamie, I've applied the commit fix manually and I will leave an attached screenshot for reference, I will also provide the SMART output status for two NVME drives a Gen3 and a Gen4 for at the bottom for further reference. Regards
SMART Drive Status on SAS Drives
Ok this should be fixed by this commit, which will be in the next release : https://github.com/webmin/webmin/commit/474ca81d4aa68efdc83b224bcc7f5951905baf5a
Hi Jamie Cameron, I've provided the RAW output of the disk in question, the serial number does not have any space between. Regards
Hi Ilia Ross, I've provided the RAW output of the disk in question from smartctl with the most common used options/flags for reference . Regards
Hi Jamie Cameron, I've provided the RAW output of the disk in question. Regards
@jcameron and @iliaross Thanks for the prompt review of this cosmetic bugs, I will provide the RAW SMART output for this SAS drive for further reference. Output for smartctl -a /dev/da1: smartctl 7.5 2025-04-30 r5714 [FreeBSD 14.3-RELEASE-p7 amd64] (local build) Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: TOSHIBA Product: MG08SDA800A Revision: 0104 Compliance: SPC-4 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Logical...
Can you provide the raw SMART output as text for this disk?
Thanks for this bug report! One question about the raw SMART output though - does the serial number have a space in it?
SMART Drive Status on SAS Drives
If the dnf command is installed, Webmin should just be using a command like dnf install package1 package2 etc.. I wonder if maybe a specific package cannot be upgraded? Perhaps instead of upgrading them all at once, try a few at a time?
Jamie, I have not tried to install anything else. My point of submitting this was that 1. the webmin processing failed; 2. But using the almalinux command line shell and the usual update command "dnf update" worked without any issues. This suggests that the "cockpit" issue reported by webmin's update process (which I have never dug into) had a problem BUT dnf did not. when using webmin's update on almalinux 9.6 what is the actual command? thanks for considering this. regards rich
Jamie, I have not tried to install anything else. My point of submitting this was that 1. the webmin processing failed; 2. But using the almalinux command line shell and the usual update command "dnf update" worked without any issues. This suggests that the "cockpit" issue reported by webmin's update process (which I have never dug into) had a problem BUT dnf did not. when using webmin's update on almalinux 9.6 what is the actual command? thanks for considering this. regards rich On 11/27/25 11:10...
That error with the package cockpit-bridge seems unrelated to Webmin! Can you install any other package successfully?
webmin 2.600 software update on almalinux 9.6 fails