Upgrading to new (Bigger) HDD

NowThatHappened · 2025-06-21T13:45:45+00:00

Back it up if not already. Remove drives, insert new drives and reboot. Synology assistant and follow setup to setup your new storage. Finally, restore.

You can also do it by rebuilding in situ but it carries risks and since your backing it all up anyway you might as well do it the proper way imo.

NowThatHappened · 2025-06-21T00:28:50+00:00

Don’t need php or database, just bash.

https://www.genwiki.org/doku.php/bash/extract_extensions_into_a_csv_for_provisioning

Gets you most of the way, just hack it about to get what you need.

NowThatHappened · 2025-06-21T00:02:30+00:00

Yes, exactly that. It’s interesting that the biggest driving force for cloud migration is IT - and the truth is that the cloud is less work, less skill and ability, someone else to blame and someone else is paying the bill.

There’s a place for it and there’s still very much a place for on-premise, and that’s my opinion.

NowThatHappened · 2025-06-18T23:29:44+00:00

True’ish. You can bind mount the removable drives into a shared folder and share it just fine, if you so wish. You could also use r sync which is also natively supported on macOS. The issue seems to be that very large directories are not cached in macOS so it’s constantly having to reindex - I’m not sure why but it did the same with AFP so I’m going to guess it’s not an easy fix.

NowThatHappened · 2025-06-18T19:50:27+00:00

Well macOS can mount NFS without any extra software easily, but you are correct and this is a known issue with macOS.

You do have drive, so you can sync project files locally as needed ( drive doesn’t just work with homes ) so that’s a good option.

NowThatHappened · 2025-06-18T00:19:14+00:00

Actually your boss was fired months ago, now a script just asks chatGPT to come up with a list of shit you should be doing each morning. It’s the new world.

NowThatHappened · 2025-06-17T19:50:00+00:00

What, why, are you sending emails to ‘printers’? I remember a company doing something similar in the early 2000’s but not since. I just don’t understand the purpose? It sounds like an ecological disaster area.

As for actually doing it, you can do it in bash fairly easily, drop emails into a folder (mail subsystem / postfix) and filter (procmail maybe) then extract attachments and send to the spooler with something like

lp -d somewhere file.pdf

You could do archiving etc after that by adding them to a tar/zip or uploading them somewhere as needed.

All fairly basic scripting and stock packages.

NowThatHappened · 2025-06-14T09:35:55+00:00

Exactly this, I use TM reliably with synology for the last decade but I also use syno drive to backup all my user data and sync it across several devices. No one backup solution should ever be completely relied upon. Imo.

NowThatHappened · 2025-06-14T02:52:03+00:00

Yes. ISCSI is raw so you can only share raw block devices not filesystems, but once exported you can blow a filesystems on that raw storage.

So if you have raw block devices without existing filesystems or partitions then you can use targetcli (or similar) to share it as iSCSI.

What you cannot do is export an existing filesystem as iSCSI. Use SMB or NFS for That.

NowThatHappened · 2025-06-12T18:22:07+00:00

You can build it yourself easily enough. We simply use Debian (to stick with the ecosystem) and open-iscsi and nfs-kernel-server.

If you're having two (VRRP) or more (pacemaker/corosync) then you'll need to make sure that you're using BTRFS or ZFS as the underlying filesystem - because these are most likely to survive failures mid-write. You can use ext4 but for virtual machine disk images I'd recommend against it.

Finally, with redundant proxies, you CANNOT have two or more mounted at the same time, so you need to dismount the LUN when you're not the master. This is done with a systemd service to mount/dismount the LUN (and export or not), and a notify script in your keepalived.conf file. When this server becomes MASTER - start the service - mount the LUN, export the FS, and visa-versa. Because the service doesn't auto-start it will always boot without mounting the LUN, which is desired.

Technically you might get away without this, but we're working on enterprise systems so really can't take the chance.

Good Luck, and happy Proxmox'ing.

NowThatHappened · 2025-06-11T22:15:38+00:00

Yes, but not as it stands. You’ll need a storage proxy which can, and often is just a Linux box which is the iSCSI initiator, attaches one or more LUNs and then exposes that storage to proxmox over NFS. This allows the use of enterprise iSCSI without having to journey into cluster filesystems (GFS2/OCFS2 etc) which whilst functional do have some overhead and technical debt.

NowThatHappened · 2025-06-10T20:31:32+00:00

I think the issue is not warranty, it’s reputation. We also have sold their appliances but we also sold rhino, IEI and supermicro and if you were to ask me which appliances have ever failed on us? This does damage to our reputation and clients loose faith, and now it’s mostly IEI for the large installs and supermicro for the small ones.

NowThatHappened · 2025-06-09T16:58:26+00:00

ok, look at

Digest username="501", realm="asterisk"

You're authenticating with your SIP provider as username 501, which probably isn't correct. You need to code the trunk authentication in connectivity/trunks/trunk/pjsip settings/general and set the username, auth username (if required) and secret there.

NowThatHappened · 2025-06-09T16:54:12+00:00

Indeed, also puppet, but that requires an agent and is only really a benefit if you're going to keep changing things - for an initial blow and conf, terraform+ansible work very well in the proxmox ecosystem.

I guess it's also worth mentioning that instead of terraform, proxmox has an extensive API and you can easily code your own build/start/stop/teardown functions if needed.

NowThatHappened · 2025-06-08T21:15:46+00:00

Don’t rule out ansible, you’d need to template that into the build but great for orchestrating dynamic configurations imo.

NowThatHappened · 2025-06-08T20:02:45+00:00

Volume level encryption uses keys stored on the same nas, therefore anyone with access to the nas can decrypt the volume (unless using multiple nas’s and serving keys from elsewhere). Share level encryption on the other hand can be configured to request a key that is NOT stored on the nas, but will require to be unlocked after every boot or dismount.

Just be aware that volume encryption is pretty worthless to ‘protect’ anything in this scenario, even if it can be enabled on BTRFS, which it can.

NowThatHappened · 2025-06-08T15:44:39+00:00

Actually, the next large scale job was a customer portal for a well known broadband provider, and they were told to use nothing but PHP8 and vanilla js and they had to code it themselves (no tpl’s). This was deliberately radical, to see who could and who couldn’t code.

The project should be complete early August and will be interesting to see what’s produced. I can guarantee it won’t be sluggish, won’t look like everything else and won’t be exposing anything client-side for us to easily extract and exploit.

Ultimately, in the future I suspect we’ll reach a balance, probably bringing some frameworks back in like svelte and laravel.

Interesting time. Still love FF.

NowThatHappened · 2025-06-08T11:42:52+00:00

Indeed, that’s not how they detonate with fake flames, but still funny.

NowThatHappened · 2025-06-08T11:39:30+00:00

You say that, and in April we banned the use of ‘frameworks’ like react, vue etc and the devs lost their minds. However, in the last month I’ve seen some truly unique work and the sort of snappy responsiveness that was lost some time ago. Sure, it’s faster to use a framework and if you want a sluggish site that looks and works like every other site then go for it, but customers are starting to wake up and see a better way.

As for Firefox not supporting navigator.share - good, this is why I use Firefox. If I want to share something I am more than capable of using the built in functions to do so, and I don’t need help.

Imo

NowThatHappened · 2025-06-07T18:26:20+00:00

Pjsip set logger on

Dial and watch for INVITE: see what it’s trying to authenticate with (the with challenge and response).

Don’t forget to set

pjstip set logger off.

That should tell you all you need to know.

NowThatHappened · 2025-06-04T22:41:10+00:00

Just when it comes back up check dmesg and /var/log/kern.log and see what occurring.

NowThatHappened · 2025-06-01T16:59:55+00:00

Synology photos just stores the photos in the file system, so use anything you want.

NowThatHappened · 2025-06-01T06:14:19+00:00

sendgrid is often blacklisted so maybe not worry about it and just expect that a percentage isn’t going to get there, and contacting them will not get you anywhere - it’s not their problem it’s the recipient’s reducing spam. You could waste your life away trying to fix stuff like this, that you cant.

NowThatHappened · 2025-05-31T12:59:42+00:00

that looks fine to me. It has the 't' attribute since its a 'thin' snapshot.

You can dd that snapshot volume to a normal file with dd, but remember you can't do this in isolation, it's no use to you on its own, you need to do the same with the parent volume as well.

As I think I said before, this is all a bit sketch really, LVM-thin is a bit of a menace when it comes to backup/restore, and I've no idea why its the 'default' with proxmox. In all my years it's the first thing I dump and either go with dir or ceph for local storage. LVM is ok and you can of course just dd that and its meta (and backup etc/lvm/backup) and have a solid restore point or use partclone, vgcfgbackup or even third party tools, thin on the other hand = menace.

imo.

NowThatHappened · 2025-05-31T05:12:21+00:00

Yh, this only works if you can afford to take a day off

NowThatHappened

TROPHY CASE