this post was submitted on 13 Dec 2023
982 points (98.9% liked)
linuxmemes
21280 readers
1096 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Can a linux/systemd nerd explain what the error is? I know it's a shutdown sequence, but I'm curious on the fault
These kinds of public errors are almost always a hard drive failure.
Using an actual hard drive for an embedded system like this would be a failure in and of itself.
Unless it literally has to store several hours' worth of HD video content, no reason the entire system couldn't fit on an SD card.
It's been my experience that SD cards are almost always what causes a failure on a SBC. Given the cost of the screens, i'd probably choose something that could boot off nvme storage. Or at least tape a new, configured SD card to the case of the SBC for when this inevitably happens.