1Fuji2Taka3Nasubi

joined 2 months ago

Yes, piefed 1.2 just released, piefed.zip might have upgraded.

[–] 1Fuji2Taka3Nasubi@piefed.zip 20 points 1 week ago

Why was there no mention from Steam that they have belatedly sent out the emails? Were the people who wishlisted the game still not notified? This is no way to fix a issue.

[–] 1Fuji2Taka3Nasubi@piefed.zip 1 points 1 week ago* (last edited 1 week ago) (2 children)

The problem seemed to have fixed itself today. I see an update for voyager is available in browser but I have not updated yet, still on 2.39.2. I don't see any update on iOS app store, but 2.39.2 is working.

There was no announcement of change on piefed.zip but perhaps something changed there? I'm not sure. I have not received additional notifications since last time I replied.

EDIT:

I went into dev tools again and it seems piefed.zip did not return 404 this time.

collapsed inline media

[–] 1Fuji2Taka3Nasubi@piefed.zip 1 points 1 week ago (1 children)

I deliberately did not clear the notifications (I could see them if I use piefed directly but I did not mark them read), I've received a few more notifications since then but there has been no change in voyager, still getting the same error consistently.

[–] 1Fuji2Taka3Nasubi@piefed.zip 1 points 1 week ago (6 children)

@aeharding@vger.social It is still occurring. Is there any logs I can collect to help you diagnose this?

[–] 1Fuji2Taka3Nasubi@piefed.zip 2 points 2 weeks ago* (last edited 2 weeks ago) (7 children)

Just ran into the same thing on piefed.zip. Happened (still happening) on both PC running browser and iOS app.

It worked fine when I received the last notification 10 hours ago, I don't think piefed.zip changed their software between then and now.

collapsed inline media

There are 2 new replies to my post which caused the notification, I can see in developer tools the replies loaded and the json response looked okay at a first glance. Not familiar enough with piefed api to know what the "list" call that got a 404 is for or whether that is a problem.

collapsed inline media

 

I am trying to set up a home server. Here is how I'm planning to do it:

/dev/nvme0n1 SSD, Proxmox, VMs & CTs /dev/sda HDD, Media library /dev/sdb HDD, Backup

I've installed Proxmox on the NVMe SSD and created a few VMs and CTs to play with.

I have also partitioned /dev/sda and created a ZFS partition on /dev/sda1, made a pool /pool and a datastore /pool/data.

I plan to put media files on /pool/data, bind mount it on a container and run Jellyfin to serve them.

I can schedule backup jobs for the VMs and CTs themselves on Proxmox, but I'm not sure how to backup the media files on /pool/data to /dev/sdb.

  1. How would one go about setting up such backups? Do I need to setup something like a cronjob with rsync or is there some easier ready-made solution? Ideally it'd be something like Proxmox's VM backup jobs that let me prune and keep some copies daily / weekly / monthly / yearly.

  2. What filesystem should I use for the backup drive / partition? Is there advantage of using ZFS to backup ZFS?

  3. Can ZFS snapshots be used on /pool/data for additional protection? If so how do I set up, for example, automatic daily snapshots? Do snapshots take up little space if the files rarely change?

Thanks.

[–] 1Fuji2Taka3Nasubi@piefed.zip 1 points 2 weeks ago

I believe that is a piece of Star Fruit.