USB Drive Fails to mount
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- operating-systems
Research direction
Start by reproducing the missing USB mount on Alpha OS 7 with the Wpilib Alpha 2 setup, checking the SystemCore UI's Storage Devices section and whether the U folder and sda1 directory appear. Compare the device state before and after a power cycle, and use the reported screenshots and terminal observations to identify what fails. Done means the USB drive mounts reliably and logs are accessible without cycling power.
Written by the indexing model from the issue text.
Description
We have a USB drive in our SystemCore that we are putting our logs too. We have noticed that twice now at MTTD that the drive has failed to mount.
We found the issue when we went to SSH our logs and found that the U folder is empty.
Checking the SystemCore UI after revealed that the thumb drive does not even show up under the "Storage Devices Section"
We ran some commands in terminal and found that sda1 directory doesn't exist.
During all of this the drive was securely in the USB port on the unit. Furthermore, if we power cycled the drive would mount and logs would be accessible again.
We are using Alpha OS 7, and Wpilib Alpha 2
- Dominant language
- Java
- Stars
- 188
- Forks
- 24
- Avg merge
- 5h 59m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wpilibsuite/SystemcoreTesting
-
Limelight Pending
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wpilibsuite/SystemcoreTesting#383 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#380 ·
Maintainers usually reply within 1 day
-
Limelight Pending
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#315 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
wpilibsuite/SystemcoreTesting#402 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wpilibsuite/SystemcoreTesting#401 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
geonetwork/geonetwork#227 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Netcracker/qubership-testing-platform-tdm3#138 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
synthetichealth/synthea#1726 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bisq-network/bisq#8097 ·
Maintainers usually reply within 1 day
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day