31
submitted 2 years ago* (last edited 2 years ago) by Lifebandit666@feddit.uk to c/selfhosted@lemmy.world

I've got 3 HDDs connected to my Proxmox machine via usb3. They worked fine until this week. I have them mounted and passed through to OMV.

One failed on Sunday. It was fine one minute, I rebooted and Proxmox wouldn't boot...

Couldn't work out why it wouldn't boot and reflashed Proxmox, losing all my machines (I have since learned the importance of backups since I had none).

I've spent 4 days rewriting it all. Rebooted last night and it happened again, but this time I noticed that it was struggling to find one of my drives and edited them out of Fstab and got it booting again.

I've since added 2/3 drives back in by adding "nofail" to my Fstab entries but my main storage drive is now showing as 100gb instead of 1tb and won't pass through to OMV.

I've come to the conclusion that they were mounted by label and "forgot" their label, hence wouldn't boot, they're now mounted by UUID.

So has anyone got any tips on the best way to mount these things without killing my whole setup?

Also if anyone knows why my storage is showing as 100gb in Proxmox and won't pass through to OMV now I would be eternally grateful. Kinda want to get the files off that drive...

you are viewing a single comment's thread
view the rest of the comments
[-] pyrosis@lemmy.world 1 points 2 years ago

Well specifically I'm referring to the internal hub on your system and how it shares port bandwidth. It doesn't really matter for things like a mouse or keyboard. However, when you are talking like permanent flash disks it's worth investigating how the bandwidth is shared between ports. Specifically the switching back and forth between the storage devices. Some filesystems handle this better than others.

I was was also referring to a way I found that stabilizes the connection. That being a USB to SATA controller via like one port. That way that port tends to take advantage of all the bandwidth without switching around.

Also keep in mind USB flash media is notorious for wear compared to something like nvme/msata disks.

It's possible to combat writes on flash media by utilizing things like ram disks in Linux. Basically migrating write heavy locations like temp and logs to the ram disk. Though you need to consider that restarting wipes those locations because they are living in ram now. Some operating systems do this automatically like opnsense with a check mark.

[-] Lifebandit666@feddit.uk 1 points 2 years ago

Well I'll keep it in mind for if I get any issues but it seems to be running ok ATM with USB ports passed through to OMV and then CIFS back to Proxmox so I can save backups.

As it is, at most 2 drives will be in use at a time with the third as a backup drive doing rsync at night (still to set up).

I'm not using flash storage. These are proper spinning Hard Drives with a usb 3 cable (and a power cable) to the host.

this post was submitted on 19 Apr 2024
31 points (100.0% liked)

Selfhosted

60861 readers
563 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS