Custom Query (1365 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (67 - 69 of 1365)

Ticket Resolution Summary Owner Reporter
#91 fixed smartctl, standby mode not detected properly on FreeBSD Dan Lukes drsweety
Description

Hi!

I've enabled the standby timer on all my harddisks with "camcontrol standby adaX -t 900" (=which sends the STANDBY ATA cmd to the drive (=idle now, arm standby timer to 900s)). This works fine and "smartctl" recognises that the drive is in standby mode:

# smartctl -A -n standby /dev/ada3
smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 8.1-RELEASE amd64] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Device is in STANDBY mode, exit(2)
# camcontrol cmd ada3 -a "E5 00 00 00 00 00 00 00 00 00 00 00" -r -
50 00 00 00 00 40 00 00 00 00 00

However, if a drive is currently active it still thinks that the drive is in standby mode even though it clearly is not:

# dd if=/dev/ada0 of=/dev/null count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.034235 secs (14955 bytes/sec)
# ./smartctl -A -n standby /dev/ada0
smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 8.1-RELEASE amd64] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Power mode: 00
Device is in STANDBY mode, exit(2)
# camcontrol cmd ada0 -a "E5 00 00 00 00 00 00 00 00 00 00 00" -r -
50 00 00 00 00 00 00 00 00 FF 00
#

Note that the "Power mode: 00" output was added by me to atacmds.cpp for debugging purposes. It outputs the value of "result" from within "ataCheckPowerMode". As you can see from the "camcontrol" output the device is active (sector count=FF). I'm not sure why the output for sector count from "camcontrol" and "smartctl" differ... Is this working as designed?

#486 worksforme smartctl tool is giving error ----- " Error Counter logging not supported Device does not support Self Test logging " while fetching the life of SSD. Dinesh Rathee Dinesh Rathee
Description

Hi Team,

The smartctl tool is giving some error while fetching the life of ssd ; the output is shared below.

Can you please check and provide the solution asap as this info is needed and very critical for our environment.

[root@ukna50sr-vf ~]# smartctl -a /dev/sda smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/

Device: LSI MR9261-8i Version: 2.90 Serial number: 00f329f7056cce821560f1e102b00506 Device type: disk Local Time is: Thu Nov 6 03:54:16 2014 UTC Device does not support SMART

Error Counter logging not supported Device does not support Self Test logging

Thanks & Regards, Dinesh Rathee M.No. ; +91-9650463332

#1220 invalid smartctl tests are not logged for SanDisk SDSSDA240G drive Artem S. Tashkinov
Description

It looks like smartctl tools cannot properly handle the SanDisk SDSSDA240G drive: whenever I try to run long/short/etc. tests, they are not stored in the SMART log. According to "Self-test execution status" they are indeed run.

SanDisk SSD Dashboard utility can run both short and long tests but no matter which test is run, short logs are always recorded:

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%        36         -
# 2  Short offline       Completed without error       00%        35         -
# 3  Short offline       Completed without error       00%        30         -
# 4  Short offline       Completed without error       00%        18         -
# 5  Short offline       Completed without error       00%         5         -

Also LifeTime is completely wrong. I've used this drive for at least 1000 hours.

SanDisk SSD Dashboard utility does not show logs at all.

I'm curious what's going on, whether it's special firmware which is not handled correctly or some issue with my drive.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.