You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, how can I check, normally command with: sudo smartctl -a /dev/sda
It doesn't show complete information,
I need temperature and error message from SMART.
RaidXpert2 GUI is deprecated from 2015 or 2017 and today I can't start on Ubuntu 20.04.
AMD Raid driver works for me, it shows in lsblk.
EDIT:
media@xero:~$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-166-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: AMD-RAID
Product: Array 02
Revision: 8.1
Compliance: SPC-3
User Capacity: 16,001,953,431,552 bytes [16.0 TB]
Logical block size: 512 bytes
LU is fully provisioned
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
no complete information from SMART, is that correct?
The text was updated successfully, but these errors were encountered:
Short answer: You can't, easily anyway.
Long answer: Manpages for smartctl do have options for getting around the RAID obfuscation of drives for popular professional hardware RAID solutions from LSI/Avago/Broadcom, Areca, HighPoint, etc. but not for software/hybrid RAID.
With the kind of licence that Dot Hill/Seagate put on RAIDCore, you'd be lucky to find someone willing to make the changes to smartctl to add RAIDCore support.
As the title says, how can I check, normally command with:
sudo smartctl -a /dev/sda
It doesn't show complete information,
I need temperature and error message from SMART.
RaidXpert2 GUI is deprecated from 2015 or 2017 and today I can't start on Ubuntu 20.04.
AMD Raid driver works for me, it shows in lsblk.
EDIT:
no complete information from SMART, is that correct?
The text was updated successfully, but these errors were encountered: