Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Disk in stout may be dying #3

Open
inducer opened this issue May 31, 2020 · 2 comments
Open

Disk in stout may be dying #3

inducer opened this issue May 31, 2020 · 2 comments
Labels
datacenter This needs to be done in person, in the datacenter preventative Something isn't actually broken, but may be at some point

Comments

@inducer
Copy link
Contributor

inducer commented May 31, 2020

Continued from https://gitlab.tiker.net/inducer/machine-shop-maintenance/-/issues/2
@inducer
Copy link
Contributor Author

inducer commented Sep 22, 2020

We bought a replacement disk, but #8.

@inducer inducer added the datacenter This needs to be done in person, in the datacenter label Nov 9, 2020
@inducer inducer added the preventative Something isn't actually broken, but may be at some point label Jan 26, 2021
@inducer
Copy link
Contributor Author

inducer commented Dec 14, 2021

This got a more stern warning this morning:

root@stout.cs.illinois.edu (59 mins. ago) (inbox)
Subject: SMART error (CurrentPendingSector) detected on host: stout
To: root@stout.cs.illinois.edu
Date: Tue, 14 Dec 2021 08:35:16 -0600

This message was generated by the smartd daemon running on:

   host name:  stout
   DNS domain: cs.illinois.edu

The following warning/error was logged by the smartd daemon:

Device: /dev/sdb [SAT], 1 Currently unreadable (pending) sectors

Device info:
WDC WD20EFRX-68EUZN0, S/N:WD-WCC4M3AS3DHL, WWN:5-0014ee-2b6a90847, FW:82.00A82, 2.00 TB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.

/proc/mdstat still shows the drive as "up".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
datacenter This needs to be done in person, in the datacenter preventative Something isn't actually broken, but may be at some point
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@inducer