[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: shitware.png (528 KB, 1268x664)
528 KB
528 KB PNG
>try setting up a FAT32 USB in LXC for Syncthing
>mount it in host
>can't parse Unicode
>fix that
>now mounts in Unicode
>mount point it in LXC
>can't parse Unicode again
>read only as well
>not a single documentation exists on how to do it
>official documentation shows unexplained config lines that don't work
>every forum thread and Reddit post is unhelpful as shit
>the WebUI treats the USB drive like an alien object
>can't pass it through to an LXC
>refuses to show it as a storage device anywhere
>wants to turn it into an LVM for me to use it

Seriously, how fucking hard is it for those retards to implement a basic support of using physical removable media throughout PVE? Do they not realize some people would like to have this type of direct connection to media that can be removed and plugged into any computer? Why the fuck do they insist on using LVM's and other esoteric retarded bullshit for everything where you'll have to at least set up a network share with a sane file system to do something as fundamentally basic as a backup schedule?
>>
>>103217546
>Year of Our Lord 2k24+
>Not one (1) single good homelab OS
Just why do we have to suffer like this, no wonder the cloud jews won with normies
>>
Bare metal servers don't have any of these problems.
>>
>>103217546
>using usb for server storage
do you have brain damage by any chance?
>>
>>103217657
But they also are a bigger PITA to manage and don't have the easy virtualization and redeployment features that Proxmox has. When I moved my containers, it was trivial and painless. Reinstall Proxmox, copy the backups, restore the backups, done, 1:1 parity, no need to reinstall shit one by one, copy configs and all that shit you'd have to do on bare metal Linux.

>>103217680
It's a handful of cross-device files, less than 100MB total. I use the USB stick as an extra redundancy sync point outside my PC and phone, but as of right now it only syncs to it when my PC is on, and I'd like for it to be a 24/7 sync point.
>>
>>103217712
>I'd like for it to be a 24/7 sync point
...then you shouldn't be using usb.
>>
>>103217729
It's 100MB worth of data. Most of the time it writes a few kilobytes on update, be it an .md note or a .kdbx update, assuming anything changed. It's not doing anything so heavy that flash memory durability would be a concern. It's been doing Unison checks every 5 minutes whenever my PC is running and it's still doing fine.
>>
its literally Debian, how hard can it be?
>>
>>103219647
>Android is literally Linux, how hard can it be?
>>
>>103217770
OP, I was ready to be sympathetic until you flat out admitted to being a retard
>>
>>103217546
Why not just use ext4?

It's not like the filesystem has any bearing while syncing between the devices and fat32 is just causing you issues
>>
>>103222623
I want it to be accessible outside of Linux machines as well. Thing is, FAT32 works just fine, the issue is with how Proxmox handles passing through mount points to it's LXC's. Mounting the drive in Proxmox is trivial, set up a mount point, fstab, boom, reads it in UTF-8, can write to it no prob. The moment I want this to be accessible on the LXC as well is when trouble starts, and Proxmox themselves don't have a clear and concise documentation on how to make a writable UTF-8 mount point in an unprivileged LXC.

>>103221638
Well I'm glad you keep calling me a retard without ever elaborating on why, what I'm doing wrong and what I should do instead. I hold your valuable opinions and sympathy within the deepest parts of my rectum.
>>
>>103217770
nigga if it's that little just email yourself that shit. or make a telegram channel for yourself
>>
>>103217546
>not using OmniOS
ngmi
>>
>>103222964
>bro just send your private files to 3rd party service bro u so dumb y u make it hard for urself
It's fucking baffling this level of retardation is so prevalent on this board. You might as well suggest using Google Drive because it's "easy".
>>
>>103222939
I see. I don't have much experience with LXC containers, since the few times I did use them it was a drag.

So unfortunately, from my perspective, the best way would either be turn it into an NTFS filesystem or use docker (I've never had mounting issues with it via proxmox vms)

Good luck though.
>>
>>103223260
Yeah, I might try setting up a VM instead of an LXC. Slightly bigger overhead but at least it might be less painful.
>>
>>103223275
> less painful

Definitely. All I have to do is set the whole USB to be pass-through and it'll show up in the vm. If pass-through isn't available on your machine, then it's still easy to just set the port to it.

> bigger overhead
Honestly, not by much. I have a Debian 12 cloud-init vm that only takes up about 512MB of memory and 10GB of storage
>>
>>103223352
> 10GB

Granted, that's cause I wanted extra space. I should note that I haven't had any issues going down to 1GB, but I just didn't want to have to worry about storage down the line
>>
>>103223352
To be fair, LXC's also have device passthroughs, but since you have to define it via /dev/sdb and Proxmox decided to randomly assign the same device to /dev/sdc I have doubts about it's reliability. Unless my Linux knowledge is lacking and you can define the device via the UUID, which would be more foolproof.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.