Timeline for Linux Failing Drives Cant Find the Drives
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 30, 2020 at 5:30 | history | suggested | binki | CC BY-SA 4.0 |
make formatting of command output more like the reading of a shell session
|
| Oct 25, 2020 at 8:25 | answer | added | Hannu | timeline score: 0 | |
| Oct 25, 2020 at 5:47 | comment | added | paddywan |
Try cat /var/log/syslog | grep kernel | grep '/dev/sd\|/dev/zd' to filter for any error messages being reported by disks. You say you are being told you have failing disks; by who or what? If it is unable to tell you which disk and why, it isn't exactly a reliable source.
|
|
| Oct 25, 2020 at 4:46 | review | Suggested edits | |||
| S Oct 30, 2020 at 5:30 | |||||
| Oct 25, 2020 at 4:45 | comment | added | binki |
I normally use lsscsi to list things. It looks like lsblk has a -a option which shows empty drives. Depending on how it is failing, maybe that would show some other drives? Once you identify the failing drive, you can use hdparm -i /dev/sda to get it to print out the serial, etc., which hopefully corresponds to stuff printed on a physical label on the drive.
|
|
| Oct 25, 2020 at 4:33 | comment | added | davidgo | I posit you are running zfs and the zd* block devices are zvols. What does "sudo zpool status" say? | |
| Oct 25, 2020 at 2:25 | review | First posts | |||
| Oct 26, 2020 at 17:25 | |||||
| Oct 25, 2020 at 2:18 | history | asked | user1687407 | CC BY-SA 4.0 |