Opened 10 years ago
Closed 10 years ago
#540 closed enhancement (wontfix)
smartd config option to monitor only boot drive
Reported by: | miknik | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | smartd | Version: | 6.3 |
Keywords: | Cc: |
Description
i found it handy if smartd can be set to monitor only first hdd(ssd) in system that used as boot. with auto detection of drive type (hdd ssd scsi etc).
Change History (10)
comment:1 by , 10 years ago
Milestone: | → Release 6.4 |
---|
comment:2 by , 10 years ago
Milestone: | Release 6.4 |
---|
comment:3 by , 10 years ago
Milestone: | → Release 6.4 |
---|
yes, but i want to do it in image for automatic deploying on different hardwares such sata, ssd (which requires -d sat option), scsi etc. there's a need for universal option like devicescan, but only for boot drive. thanks.
comment:4 by , 10 years ago
Milestone: | Release 6.4 → none |
---|---|
Priority: | major → minor |
In general, determining "boot drive" is platform specific and non-trivial in many cases.
According to ticket #539, you are using the Windows version of smartd. On many Windows systems, it may work if drive letter C: is used as the device name in smartd.conf.
If this does not work for you, create a wrapper script for smartd which creates a system specific smartd.conf and then starts smartd daemon.
comment:5 by , 10 years ago
i dont find how to use windows drive letter in smartd.config.
C: -t -R 5! -R 188! -C 197 -U 198 -m event@…
that is what you mean? it should work for hdd and ssd (requires -d sat option) for both?
comment:6 by , 10 years ago
Yes.
The autodetection of -d TYPE
may work or not. This requires that Windows ATA/SCSI layer, device driver, SAT layer etc. return the correct device type information. "HDD or SSD" does not matter, "ATA or SCSI or SAT or ..." does.
comment:7 by , 10 years ago
ok, does that config (C: -t -R 5! -R 188! -C 197 -U 198 -m event@…) will work if
config "/dev/sda -C 197 -U 198 -m event@…" not work, exit with error that -d sat required and config "/dev/sda -d sat -C 197 -U 198 -m event@…" work?
comment:8 by , 10 years ago
i have tried and that didn't not work. it would be handy if directive DRIVESCAN can be limited for scanned devices to specified drive by option c: (boot drive)
comment:9 by , 10 years ago
If C: does not work for machines where C: partition is the Windows system partition (located on the boot drive), there might be various issues unrelated to this feature request. For example the -d TYPE
autodetection may not work because Windows reports the wrong device type.
It would not help to add a 'monitor only boot drive' feature to smartd then.
For further help, provide detailed problem info on the smartmontools-support mailing list.
comment:10 by , 10 years ago
Milestone: | none |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Determining 'boot drive' is platform specific, may be non-trivial and the use cases are rare. There are no plans to add this feature to smartd in the near future.
Feel free to reopen this ticket if you could provide a working patch.
Remove
DEVICESCAN
from smartd.conf and add the boot drive only.