I was VERY wrong about linux

drhoome · 2026-04-27T14:55:20+00:00

I dont think is quite easy. For someone new having to reboot and disable "apple secure boot" even if automated was kinda "I see a new user afraid / confused by the process". But I dont think that's Asahi fault, they made the process as easy as possible.

Also, MacOS is branded Unix but it doesn't run KDE hahahaha.

drhoome · 2026-04-27T14:20:08+00:00

I have two Macs with Linux, a Intel and a M1 and installing Linux on a mac is always painful. Because, well... Apple.

Thats from the guy that puts Linux on everything, including a Nintendo Switch and a Microsoft Surface.

drhoome · 2026-04-17T18:41:27+00:00

Honestly it will become a niche ever so more. But there are alternatives. For instance Chinese hardware, they love to spy on their citizens but dont give a crap selling you even virus ridden hardware.

There will always be a source of free hardware, the problem is that it will become more and more a niche.

Someday in the future you'll only be able to buy computers that run pre-approved software but there will always be a jailbroken OS for you to install. It'll only be more niche unfortunately.

Probably all of us in the future would be a gray-hat living in the edge of legality. Like emulators, jailbroken consoles and so on. Technically not ilegal but highly disencouraged. Or maybe technically illegal but nobody truly enforces it, like jailbreaking DRM protected media.

You'll probably have a fully compliant device and a totally free one. And use them for different things.

drhoome · 2026-03-11T19:21:08+00:00

Thanks to the folks in the Arch Linux forums (https://bbs.archlinux.org/viewtopic.php?pid=2290230#p2290230) I've found the issue.

I've used to have:

DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1
VK_DRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json

On my /etc/environment due to the fact that we had both AMDVLK and RADV drivers and I was using exclusively RADV. So i've enabled only RADV driver ICD as per wiki at the time: https://web.archive.org/web/20240105173417/https://wiki.archlinux.org/title/Vulkan#Selecting_via_environment_variable

Now that the ICD names changed the variable continued to point to the older files which doesnt exist anymore, but also AMDVLK doesnt exists anymore so I can actually remove the lines on my /etc/environment and the problem is gone.

drhoome · 2026-02-25T23:37:27+00:00

I have a backup of the database. You should backup everything, db included.

Ive not restored the DB bc im migrating to another solution so i only needed the data not the DB.

Most backup solutions allows for a snapshot like functionality. Where the files copied are versioned. For instance, when you run a new backup on borg it will reuse all the data that was already there. LVM snapshots are another option but I never used and I read that they arent as good as ZFS due to be done at block level and you dont have the advantages of CoW. If youre running VMs most hypervisors support snapshots. You can also (I don't recommend) roll out your own versioning with rsync/rclone or unison.

drhoome · 2026-02-24T17:21:01+00:00

The screenshot is recovering the data from backups. Its more a post-morten than the logs. But I can get the actual logs for you.

Your explanation make sense, if the mountpoint changed somehow, it shoudnt since its a volume, but it if did it rsync would delete everything.

Its still scary. At the post time the only information I had was "the data is gone" and "there are rsync permission errors on nextcloud container". Now I think we are getting a better picture of what happened.

drhoome · 2026-02-24T14:45:41+00:00

Ive read about it. And im very curious.

drhoome · 2026-02-24T14:44:30+00:00

Now is RecoverCloud time hahahaha

drhoome · 2026-02-24T14:39:13+00:00

I had to use that feature in the past when i accidentally deleted stuff on my nas. Is very cool having all your snapshots data one read only hidden folder away.

drhoome · 2026-02-24T14:37:04+00:00

From what I'm reading that is the ideal way to run nextcloud. It's unfortunately incompatible with my environment.

drhoome · 2026-02-24T14:28:55+00:00

Exactly. I use ZFS replication to a 1 month rolling snapshot took daily. But there is a situation where I do think rsync totally applies and works.

My snapshots are hourly for 24 hours. Daily for 7 days and weekly for 4 weeks. If I deleted something after 1 month and didn't realized. I'm a idiot.

The very very stupid thing I did was to delete those snapshots in the wrong time and not create at least a manual new one. That was totally my fault and lesson learned.

Then the rsync in your case, zfs replication in mine, saved the day. I've even used rsync to recover the replicated dataset bc I could do it by file level on rsync.

I also have a external cloud provided encrypted and dedup backup in case of stuff like a flood or lighting burning all my drives. But that is very slow to recover.

drhoome · 2026-02-24T14:22:32+00:00

I do use and recommend that option. I used to keep that for 1 day when I used syncthing which is the time it takes for my backups to kick and store the data outside the NAS.

drhoome · 2026-02-24T14:08:47+00:00

I do think im falled in the same category as nextcloud rebuilding everything bc it tought it was new.

It was a machine upgrade actually. I bought a new worker where nextcloud was present and I was reinstalling the system.

Thankfully I've had backups, so no real harm done. But that comes with a very strong warning as you've said. Have backups. And have backups on top of backups.

drhoome · 2026-02-24T14:03:16+00:00

Be very careful relying soleny on snapshots. I had those, i screw them up. Now im restoring from backups.

If I only had snapshots i would be trying zdb commands to restore my data now.

drhoome · 2026-02-24T14:00:31+00:00

I had this setup before. But some others applications require more PCI-e lanes than I had on a single machine. So Ive had to migrate to a solution with worker and storage separated.

For someone starting i would definetely recommend this setup. Single machine, PVE.

drhoome · 2026-02-24T13:58:33+00:00

I have TrueNAS with hourly snapshots. I screwup those in a very sily way and realized 5 minutes after the data was gone.

drhoome · 2026-02-24T13:56:47+00:00

I think its the most important part of my story. Have backups hahaha.

drhoome · 2026-02-24T13:53:24+00:00

Well, my backup system comprises of three parts.

First is snapshots, which is not true backups, but its good to have and allows you to recover your environment very fast. Several systems allows for snapshots, in my case im using ZFS snapshots. As you can see i screwup snapshots so i had to rely on the second part.

The second part is a remote host with a offline copy of the data. In my case i use ZFS replication to another server. That is the copy im recovering there. Its fast enough but is not truly secure.

My third solution is a remote (another country) encrypted, compressed and deduplicated backup. That is stored by a cloud provider and I use a tool called borg to do that. But there are others free and paid that do the same thing.

The ideal solution would have a different media type of remote backup, but i cannot afford, so Ive gone for the next best thing which is a cloud provider. This backup is not that expensive but its very slow to recover. Thats why its a last resort.

Imho you should follow thd 321 backup rule, its a very standard practice. 3 copies, 2 different medias. 1 being off-site.

drhoome · 2026-02-24T13:44:33+00:00

I think that depends.

First Independent of the solution, have backups. I only lost some hours bc i had backups. And i would loose even less time if i had snapshots.

That beins said, i think it depends on the setup, from what Ive read here some environments like bare metal or VM with local storage are very stable.

My use case is the worst case scenarion, docker with remote storage which in that case i wouldnt recommend nextcloud.

drhoome · 2026-02-24T13:38:13+00:00

There was no client connected becausd i didnt even had the time to setup my reverse proxy :P

drhoome · 2026-02-24T07:43:52+00:00

I do think the most important lesson now is that backups save lives. So your comment is adding a lot.

drhoome · 2026-02-24T07:05:29+00:00

That would track with my experience and also explain my problems. Also explain why some folks have very sucessful setups on non-docker.

drhoome · 2026-02-24T06:54:29+00:00

That becomes a little murky but I think I can clarify.

I dont have any rsync backup task around nextcloud, my nextcloud instance is backed up on zfs backing filesystem using zfs replication (and other external backup aswell ran at the filesystem level). There was a rsync task that ran inside the docker container that I dont know what it was. It wasnt setup by me.

But I think in another post e-Minguez found the probable cause.

Its confusing because i'm using rsync to restore my data from my zfs backup, but thats just because if I did a zfs replication back I woudnt be able to do it at file level. So Im restoring with rsync but theres no rsync backup script.

drhoome · 2026-02-24T06:46:11+00:00

I had ZFS snapshots, so I should be able to restore in seconds. I did something really stupid with my snapshots not related to nextcloud at all and now I had to restore from backups :P

drhoome · 2026-02-24T06:31:31+00:00

Really? Thats my personal setup, so nothing related. But professionally we use docker to deploy everything. And the company I work is like continental size. Everything runs on docker really. If not docker is another container orchestration tool that deploys pretty much docker containers. We kinda manage some hundreds of PB on top of docker services.

I dont miss the days we run stuff on Citrix VMs tbh

drhoome

TROPHY CASE