Custom Query (1405 matches)
Results (52 - 54 of 1405)
Ticket |
---|
#14 |
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? |
#16 |
Description |
Latest FreeBSD has new ahci(4) driver for AHCI SATA controllers. SATA disks on these controllers are represented as 'ada' disks. These are "normal" SATA disks that support usual ATA/SATA commands. The difference from traditional 'ad' disks is that 'ada' disks do not support ata(4) ioctls, instead commands can be sent using cam(3). Proposed patch adds initial support for such disks. To achieve this freebsd_ata_device is subclassed to reuse the code for building ATA commands. Then cam(3) transport is used to send commands to disks (this is somewhat similar to scsi disks code). Currently auto-discovery of ada disks is not implemented. |
#20 |
Description |
I've bought a brand new 1T Seagate drive yesterday. kotik tmp # dmesg | grep ST31 [ 0.834822] ata1.00: ATA-8: ST31000528AS, CC35, max UDMA/133 [ 0.847168] scsi 0:0:0:0: Direct-Access ATA ST31000528AS CC35 PQ: 0 ANSI: 5 I was quite surprised to see its Head_Flying_Hours to be some n-teen digit number when I first run smartctl on it, however, Power_On_Hours value was sane. To be sure that everything is ok with my eyes I ran smrtctl again. This time the value was completely different although of the same order of magnitude. After quick investigation it became quite obvious that there is something wrong with the byte order of the raw value kotik tmp # smartctl -d ata -A /dev/sda | grep ^240 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 102838696935451 kotik tmp # printf "%x\n" 102838696935451 5d880000001b When I read the values with my programme (see attachment) I found that one of the bytes of the value is stored in the reserv field of the ata_smart_attribute structure. The right order to read the value seems to be raw[3], raw[2], raw[1], raw[0], reserv, raw[5], raw[4] However, I am not sure about more significant bytes (raw[1-3]). The value itself is almost for sure number of milliseconds. |