Disks are not showing up in GUI

B

blooshades

New Member
Mar 24, 2025
4
0
1
Hi,

Novice here, not sure why several disks are not appearing in the GUI. When I go to node>disks it will sit there and spin for a bit and eventually error out with 'connection failure'

The disks do show up sda - sdg:

Code: 
 root@prox1:~# lsblk
NAME               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                  8:0    0   1.8T  0 disk
sdb                  8:16   0   1.8T  0 disk
sdc                  8:32   0   1.8T  0 disk
sdd                  8:48   0   1.8T  0 disk
sde                  8:64   0   1.8T  0 disk
sdf                  8:80   0   1.8T  0 disk
sdg                  8:96   0   1.8T  0 disk
sdh                  8:112  0 119.2G  0 disk
├─sdh1               8:113  0  1007K  0 part
├─sdh2               8:114  0     1G  0 part /boot/efi
└─sdh3               8:115  0 118.2G  0 part
  ├─pve-swap       252:0    0     8G  0 lvm  [SWAP]
  ├─pve-root       252:1    0  39.6G  0 lvm  /
  ├─pve-data_tmeta 252:2    0     1G  0 lvm 
  │ └─pve-data     252:4    0  53.9G  0 lvm 
  └─pve-data_tdata 252:3    0  53.9G  0 lvm 
    └─pve-data     252:4    0  53.9G  0 lvm

This a fresh install of 8.3.0 onto an MSI z87-GD65 GAMING motherboard with an Intel 4770K and 16GB of RAM

some more detail:

Code: 
root@prox1:~# fdisk -x
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HUA72302
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: gpt
Disk identifier: F7CB986E-71DE-6C4F-B290-D0B0F88A3752
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HUA72302
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: gpt
Disk identifier: A0F7C98F-1DDF-0641-965E-ACF745FF73A6
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HUA72302
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: gpt
Disk identifier: 962FFD0B-BA83-B84F-9011-C16001920376
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sdd: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HUA72302
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: gpt
Disk identifier: 7E744F60-60D3-9B4C-B3E7-4B2E206D738F
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sde: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM001-1CH1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F34C2991-6263-FA44-8F99-A4D9E52E5089
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sdf: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HUA72302
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: gpt
Disk identifier: 5365FB9A-87BF-B44E-9DDA-16A398E519B5
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sdg: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HUA72302
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: gpt
Disk identifier: 87F42C85-ADD6-3A45-8FF8-443C77F2A5FE
First usable LBA: 2048
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33


Disk /dev/sdh: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: Samsung SSD 840
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: gpt
Disk identifier: DE9D556D-8750-41BC-8813-AB79F11ADBCB
First usable LBA: 34
Last usable LBA: 250069646
Alternative LBA: 250069679
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33

Device       Start       End   Sectors Type-UUID                            UUID                                 Name Attrs
/dev/sdh1       34      2047      2014 21686148-6449-6E6F-744E-656564454649 8DF66A90-64C0-400F-BC80-44FCF3F564FC     
/dev/sdh2     2048   2099199   2097152 C12A7328-F81F-11D2-BA4B-00A0C93EC93B CD23C5F2-AD4E-43B7-A0B4-8F6EB54B3405     
/dev/sdh3  2099200 250069646 247970447 E6D6D379-F507-44C2-A23C-238F2A3DF928 164B5CB2-79E7-4254-B381-A6CA7B9BF987     


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 39.56 GiB, 42475716608 bytes, 82960384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Thanks for any insights!
 
Hello and welcome to the Proxmox community :cool:.

Let the livelogger run while you click on “Disks” in the WebUI. Maybe we can see more there:

Code: 
journalctl -f
 
mariol said:
Hello and welcome to the Proxmox community :cool:.

Let the livelogger run while you click on “Disks” in the WebUI. Maybe we can see more there:

Code: 
journalctl -f
Click to expand...
Hi Mario,

Thanks for the reply,

The 'communication failure' error occured around the time of this output:

Code: 
Mar 24 08:53:09 prox1 systemd[1]: smartmontools.service: Failed with result 'timeout'.

Full output:

Code: 
root@prox1:~# journalctl -f
Mar 24 08:52:00 prox1 systemd[1805]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 08:52:00 prox1 systemd[1805]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 24 08:52:00 prox1 systemd[1805]: Reached target sockets.target - Sockets.
Mar 24 08:52:00 prox1 systemd[1805]: Reached target basic.target - Basic System.
Mar 24 08:52:00 prox1 systemd[1805]: Reached target default.target - Main User Target.
Mar 24 08:52:00 prox1 systemd[1805]: Startup finished in 100ms.
Mar 24 08:52:00 prox1 systemd[1]: Started user@0.service - User Manager for UID 0.
Mar 24 08:52:00 prox1 systemd[1]: Started session-1.scope - Session 1 of User root.
Mar 24 08:52:00 prox1 login[1823]: ROOT LOGIN  on '/dev/pts/0'
Mar 24 08:52:03 prox1 pvestatd[1688]: status update time (22.209 seconds)
Mar 24 08:52:35 prox1 smartd[1343]: Device: /dev/sde [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 08:52:35 prox1 smartd[1343]: Device: /dev/sdf, type changed from 'scsi' to 'sat'
Mar 24 08:52:35 prox1 smartd[1343]: Device: /dev/sdf [SAT], opened
Mar 24 08:52:35 prox1 smartd[1343]: Device: /dev/sdf [SAT], Hitachi HUA723020ALA641, S/N:YGH8HE9D, WWN:5-000cca-224d1f464, FW:MK7OA840, 2.00 TB
Mar 24 08:52:35 prox1 smartd[1343]: Device: /dev/sdf [SAT], found in smartd database 7.3/5319: Hitachi Ultrastar 7K3000
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdf [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg, type changed from 'scsi' to 'sat'
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], opened
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], Samsung SSD 840 PRO Series, S/N:S1ANNEAD532510X, WWN:5-002538-55034c2fb, FW:DXM05B0Q, 128 GB
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], found in smartd database 7.3/5319: Samsung based SSDs
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 08:52:36 prox1 smartd[1343]: Monitoring 7 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar 24 08:52:38 prox1 smartd[1343]: Device: /dev/sdd [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 176 to 171
Mar 24 08:52:42 prox1 chronyd[1495]: Selected source 162.159.200.1 (2.debian.pool.ntp.org)
Mar 24 08:52:43 prox1 chronyd[1495]: Source 23.150.41.122 replaced with 23.111.186.186 (2.debian.pool.ntp.org)
Mar 24 08:52:57 prox1 systemd[1]: smartmontools.service: start operation timed out. Terminating.
Mar 24 08:53:09 prox1 systemd[1]: smartmontools.service: Failed with result 'timeout'.
Mar 24 08:53:09 prox1 systemd[1]: Failed to start smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
Mar 24 08:53:09 prox1 systemd[1]: Reached target multi-user.target - Multi-User System.
Mar 24 08:53:09 prox1 systemd[1]: Reached target graphical.target - Graphical Interface.
Mar 24 08:53:09 prox1 systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Mar 24 08:53:09 prox1 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Mar 24 08:53:09 prox1 systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Mar 24 08:53:09 prox1 systemd[1]: Startup finished in 2.844s (kernel) + 1min 46.030s (userspace) = 1min 48.874s.
 
Please try the following: Stop Smartmoontool, then make sure that the service is really stopped. Once it is stopped, start it again.

Code: 
systemctl stop smartmontools.service

systemctl status smartmontools.service

systemctl start smartmontools.service

First question: Did that work?
Second question: Does the behavior change in the WebUI?
 
mariol said:
Please try the following: Stop Smartmoontool, then make sure that the service is really stopped. Once it is stopped, start it again.

Code: 
systemctl stop smartmontools.service

systemctl status smartmontools.service

systemctl start smartmontools.service

First question: Did that work?
Second question: Does the behavior change in the WebUI?
Click to expand...


It does not seem to have worked, and the behavior in the GUI did not change, here is all outputs:

Code: 
root@prox1:~# systemctl stop smartmontools.service


root@prox1:~# systemctl status smartmontools.service
× smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon
     Loaded: loaded (/lib/systemd/system/smartmontools.service; enabled; preset: enabled)
     Active: failed (Result: timeout) since Mon 2025-03-24 08:53:09 PDT; 11h ago
       Docs: man:smartd(8)
             man:smartd.conf(5)
    Process: 1343 ExecStart=/usr/sbin/smartd -n $smartd_opts (code=killed, signal=TERM)
   Main PID: 1343 (code=killed, signal=TERM)
     Status: "Checking 7 devices ..."
        CPU: 57ms

Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], Samsung SSD 840 PRO Series, S/N:S1ANNEAD532510X, WWN:5-002538-55034c2fb, FW:DXM05B0Q, 128 GB
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], found in smartd database 7.3/5319: Samsung based SSDs
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Mar 24 08:52:36 prox1 smartd[1343]: Device: /dev/sdg [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 08:52:36 prox1 smartd[1343]: Monitoring 7 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar 24 08:52:38 prox1 smartd[1343]: Device: /dev/sdd [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 176 to 171
Mar 24 08:52:57 prox1 systemd[1]: smartmontools.service: start operation timed out. Terminating.
Mar 24 08:53:09 prox1 systemd[1]: smartmontools.service: Failed with result 'timeout'.
Mar 24 08:53:09 prox1 systemd[1]: Failed to start smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.


root@prox1:~# systemctl start smartmontools.service
Job for smartmontools.service failed because a timeout was exceeded.
See "systemctl status smartmontools.service" and "journalctl -xeu smartmontools.service" for details.

=====================================================================================================

root@prox1:~# systemctl status smartmontools.service
× smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon
     Loaded: loaded (/lib/systemd/system/smartmontools.service; enabled; preset: enabled)
     Active: failed (Result: timeout) since Mon 2025-03-24 20:18:38 PDT; 7min ago
       Docs: man:smartd(8)
             man:smartd.conf(5)
    Process: 109565 ExecStart=/usr/sbin/smartd -n $smartd_opts (code=killed, signal=TERM)
   Main PID: 109565 (code=killed, signal=TERM)
     Status: "Checking 7 devices ..."
        CPU: 52ms

Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], opened
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], Samsung SSD 840 PRO Series, S/N:S1ANNEAD532510X, WWN:5-002538-55034c2fb, FW:DXM05B0Q, 128 GB
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], found in smartd database 7.3/5319: Samsung based SSDs
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:18:06 prox1 smartd[109565]: Monitoring 7 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar 24 20:18:27 prox1 systemd[1]: smartmontools.service: start operation timed out. Terminating.
Mar 24 20:18:38 prox1 systemd[1]: smartmontools.service: Failed with result 'timeout'.
Mar 24 20:18:38 prox1 systemd[1]: Failed to start smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.

===========================================================================================================

root@prox1:~# journalctl -xeu smartmontools.service
Mar 24 20:16:57 prox1 smartd[109565]: Opened configuration file /etc/smartd.conf
Mar 24 20:16:57 prox1 smartd[109565]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Mar 24 20:16:57 prox1 smartd[109565]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Mar 24 20:16:57 prox1 smartd[109565]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Mar 24 20:16:57 prox1 smartd[109565]: Device: /dev/sda [SAT], opened
Mar 24 20:16:57 prox1 smartd[109565]: Device: /dev/sda [SAT], Hitachi HUA723020ALA641, S/N:YFHGEE3A, WWN:5-000cca-223d4a716, FW:MK7OA840, 2.00 TB
Mar 24 20:16:57 prox1 smartd[109565]: Device: /dev/sda [SAT], found in smartd database 7.3/5319: Hitachi Ultrastar 7K3000
Mar 24 20:16:58 prox1 smartd[109565]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:16:58 prox1 smartd[109565]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Mar 24 20:16:58 prox1 smartd[109565]: Device: /dev/sdb [SAT], opened
Mar 24 20:16:58 prox1 smartd[109565]: Device: /dev/sdb [SAT], Hitachi HUA723020ALA641, S/N:YGHHARPA, WWN:5-000cca-224d5115b, FW:MK7OA840, 2.00 TB
Mar 24 20:16:58 prox1 smartd[109565]: Device: /dev/sdb [SAT], found in smartd database 7.3/5319: Hitachi Ultrastar 7K3000
Mar 24 20:16:59 prox1 smartd[109565]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:16:59 prox1 smartd[109565]: Device: /dev/sdc, type changed from 'scsi' to 'sat'
Mar 24 20:16:59 prox1 smartd[109565]: Device: /dev/sdc [SAT], opened
Mar 24 20:16:59 prox1 smartd[109565]: Device: /dev/sdc [SAT], Hitachi HUA723020ALA641, S/N:YGHGZ6KA, WWN:5-000cca-224d4e61c, FW:MK7OA840, 2.00 TB
Mar 24 20:16:59 prox1 smartd[109565]: Device: /dev/sdc [SAT], found in smartd database 7.3/5319: Hitachi Ultrastar 7K3000
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sdd, type changed from 'scsi' to 'sat'
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sdd [SAT], opened
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sdd [SAT], Hitachi HUA723020ALA641, S/N:YFHHH9XA, WWN:5-000cca-223d52294, FW:MK7OA840, 2.00 TB
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sdd [SAT], found in smartd database 7.3/5319: Hitachi Ultrastar 7K3000
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sdd [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sde, type changed from 'scsi' to 'sat'
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sde [SAT], opened
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sde [SAT], ST2000DM001-1CH164, S/N:Z1E3KBF4, WWN:5-000c50-0504475d5, FW:CC26, 2.00 TB
Mar 24 20:17:00 prox1 smartd[109565]: Device: /dev/sde [SAT], found in smartd database 7.3/5319: Seagate Barracuda 7200.14 (AF)
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sde [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdf, type changed from 'scsi' to 'sat'
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdf [SAT], opened
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdf [SAT], Hitachi HUA723020ALA641, S/N:YGH8HE9D, WWN:5-000cca-224d1f464, FW:MK7OA840, 2.00 TB
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdf [SAT], found in smartd database 7.3/5319: Hitachi Ultrastar 7K3000
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdf [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg, type changed from 'scsi' to 'sat'
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], opened
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], Samsung SSD 840 PRO Series, S/N:S1ANNEAD532510X, WWN:5-002538-55034c2fb, FW:DXM05B0Q, 128 GB
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], found in smartd database 7.3/5319: Samsung based SSDs
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], can't monitor Current_Pending_Sector count - no Attribute 197
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], can't monitor Offline_Uncorrectable count - no Attribute 198
Mar 24 20:18:06 prox1 smartd[109565]: Device: /dev/sdg [SAT], is SMART capable. Adding to "monitor" list.
Mar 24 20:18:06 prox1 smartd[109565]: Monitoring 7 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar 24 20:18:27 prox1 systemd[1]: smartmontools.service: start operation timed out. Terminating.
Mar 24 20:18:38 prox1 systemd[1]: smartmontools.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit smartmontools.service has entered the 'failed' state with result 'timeout'.
Mar 24 20:18:38 prox1 systemd[1]: Failed to start smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
░░ Subject: A start job for unit smartmontools.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit smartmontools.service has finished with a failure.
░░
░░ The job identifier is 720 and the job result is failed.
lines 78-133/133 (END)

I rebooted the machine and ran through this again with pretty much the same results.
 
Thanks for the output. Could it be that your drives are connected externally via USB, for example? Perhaps a special case?
 
mariol said:
Thanks for the output. Could it be that your drives are connected externally via USB, for example? Perhaps a special case?
Click to expand...
No these are all connected to the onboard sata interfaces. I suppose I'll try just connecting them one at a time and see if that makes a difference.

I'll point out that when installing proxmox, all of the drives did appear as options to install to.
 
No these are all connected to the onboard sata interfaces. I suppose I'll try just connecting them one at a time and see if that makes a difference.
Click to expand...
OK, sounds good.
Also take a look at the smart values of the drives, maybe there is a problem there. After Smartd times out, I hope the manual check works with the drives.

Code: 
smartctl -a /dev/disk/by-id/<drivename>


I'll point out that when installing proxmox, all of the drives did appear as options to install to.
Click to expand...
Yes, that's okay, there are no restrictions.
 
You must log in or register to reply here.
Top Bottom