Custom Query (1415 matches)
Results (262 - 264 of 1415)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12 | wontfix | smartmontools: In Self-test log, LifeTime wraps at 65536 hours | ||
| Description |
smartctl -a gives here: [...] ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE [...]
[...] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 572 - # 2 Short offline Completed without error 00% 548 - # 3 Short offline Completed without error 00% 524 - # 4 Short offline Completed without error 00% 500 - # 5 Short offline Completed without error 00% 476 - # 6 Short offline Completed without error 00% 452 - # 7 Short offline Completed without error 00% 428 - # 8 Short offline Completed without error 00% 404 - # 9 Short offline Completed without error 00% 380 - #10 Short offline Completed without error 00% 356 - #11 Short offline Completed without error 00% 332 - #12 Short offline Completed without error 00% 308 - #13 Short offline Completed without error 00% 284 - #14 Short offline Completed without error 00% 260 - #15 Short offline Completed without error 00% 236 - #16 Short offline Completed without error 00% 212 - #17 Short offline Completed without error 00% 188 - #18 Short offline Completed without error 00% 164 - #19 Short offline Completed without error 00% 140 - #20 Short offline Completed without error 00% 116 - #21 Short offline Completed without error 00% 92 - As you can see, in the SMART attributes, the life time (Power_On_Hours) is OK: 66120. But in the log, it has wrapped at 65536. Found in 5.38 and svn revision 2879 Original bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535298 |
|||
| #14 | wontfix | ``Usage Attribute: 194 Temperature_Celsius'' is confusing to parse | ||
| Description |
There's probably too much history now, but now I'll be able to say, "I tried and it was rejected." Folks around my work place don't like the transcribed message because they think this means "381 deg. F." If there were a way to tell smartd to print, say:
instead, then my internal clients would have a more difficult time misunderstanding the meaning. Maybe the:
option? |
|||
| #19 | wontfix | smartmontools-5.38 repeatedly freeze Macbook (OS X) | ||
| Description |
When I install smartmontools via MacPorts (default build), the 'smartd' daemon is automatically registered as a StartupItem. After that, it will periodically - every 30 minutes - query my harddisk and log the following:
during which my computer freezes for about five to ten seconds (possibly because not HDD access is possible). Removing smartmontools and killing smartd also stopped the repeated freeze. Issue: Querying SMART attributes should not freeze the computer (I am running several Linux machines where smartmontools and smartd work fine without freeze). Hardware: Modellname: MacBook Pro Modell-Identifizierung: MacBookPro5,5 Prozessortyp: Intel Core 2 Duo Prozessorgeschwindigkeit: 2,26 GHz Anzahl der Prozessoren: 1 Gesamtzahl der Kerne: 2 L2-Cache: 3 MB Speicher: 2 GB Busgeschwindigkeit: 1,07 GHz Boot-ROM-Version: MBP55.00AC.B03 SMC-Version (System): 1.47f2 Harddisk: Kapazität: 500,11 GB (500.107.862.016 Byte) Modell: WDC WD5000BEVT-22ZAT0 Version: 01.01A01 Seriennummer: WD-WXB0A8948221 Native Command Queuing: Ja Queue Depth: 32 Wechselmedien: Nein Absteckbares Laufwerk: Nein BSD-Name: disk0 Rotationsrate: 5400 Partitionstabellentyp: GPT (GUID-Partitionstabelle) S.M.A.R.T.-Status: Überprüft Also, 'smartctl' will report SMART as "disabled" when querying the disk, although OS X reports the SMART status as 'OK'. |
|||
