fsck and reboot, and make sure your backups work
this post was submitted on 07 Jul 2023
12 points (87.5% liked)
Selfhosted
40157 readers
588 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
I turned it off after taking the pic. Will try, thanks
Shut down, check all the wires and plugs. So many times it is the simple things.
If it's not hardware, then it's the filesystem: Either some disk (or quota) is full, or not mounted, or a filesystem is damaged.
Did you run a short or long SMART test? How old is the drive? Usually those errors are the beginnings a failing drive in my experience unless you are doing mass I/O (like TB/s) and it can’t update the filesystem meta fast enough for some reason.
Short SMART test, the drive is 5 years old at most. The most I'm doing on the drive is MB/s... So it should be fine
I'll try to get a new drive, probably SSD. Can it be related to the drives card? I have an hardware RAID drive aggregator card, with a single disk on it (had 3 in the past and the 2 oldest ones just died at the same time, making scratching noises ; they were 10+ years old but SMART said everything is fine (short one, haven't tried a long one as smartctl -a tells me it will take about 5-10 for all disks).
Yeah the long test does a surface inspection and checks all of the sectors so it will take a while, you can run it in the background though and it might default to that.
Do backup important data though as if it is in fact failing the extra I/O might tip it over the edge, can’t be too careful.
If it was me, I would probably run fsck and reboot the first time in case it was a fluke and then investigate the drive if it happens repeatedly.
If you are worried about it’s age, the SMART will also tell you the power on hours of the drive, that’s the age that matters (well, and TB written sometimes). Each manufacturer has different mean time between failure ratings depending on the type of drive as well, you can also check backblaze data sometimes.
Hope that helps!
Can you boot from disk?
It boots "fine", but I'm now pretty sure it will crash again the same way. The disk is only 5 years old, I hope it's not an hardware problem.
5 years. Gees haha. Not a bad innings.
5 years old is pretty old for a hard drive
Maybe an issue with ram? Could be loose, dusty, going bad.
view more: next ›