Opened 14 years ago
Closed 10 years ago
#37 closed defect (fixed)
'smartctl -n standby' wakes up drive
| Reported by: | Christian Franke | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | Release 5.39.1 |
| Component: | all | Version: | 5.38 |
| Keywords: | linux | Cc: |
Description
If 'smartctl -n standby' is used on Linux, smartctl properly detects the standby mode and exits, but the drive spins up then.
If 'hdparm -C' is used instead, the drive does not spin up.
Related thread:
http://sourceforge.net/mailarchive/forum.php?thread_name=4B40CF2C.8020405%40t-online.de&forum_name=smartmontools-support
Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/497256
Change History (4)
comment:1 by , 14 years ago
| Milestone: | Release 5.40 → Release 5.39.1 |
|---|
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 10 years ago
| Keywords: | freebsd added; linux removed |
|---|---|
| Milestone: | Release 5.39.1 |
| Resolution: | fixed |
| Status: | closed → reopened |
| Version: | 5.38 → 6.2 |
The same behaviour under FreeBSD 9.2 and FreeBSD 9.3-PRERELEASE with smartctl 6.2.
ATA drives spin up even the status (standby) is detected correctly.
Drive information:
START OF INFORMATION SECTION
Model Family: SAMSUNG SpinPoint T166
Device Model: SAMSUNG HD501LJ
Serial Number: S0MUJ1CP318973
LU WWN Device Id: 5 0000f0 01b318973
Firmware Version: CR100-10
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 3b
SATA Version is: SATA 2.5, 3.0 Gb/s
Local Time is: Thu Jun 5 09:19:55 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
comment:4 by , 10 years ago
| Keywords: | linux added; freebsd removed |
|---|---|
| Milestone: | → Release 5.39.1 |
| Resolution: | → fixed |
| Status: | reopened → closed |
| Version: | 6.2 → 5.38 |
This Linux-specific issue was fixed 4 years ago in 5.39.1.
Please do not reopen a Linux-specific ticket to report a FreeBSD-specific problem. Create a new ticket instead.
r3052, r3053.