Should I just start this node over?

This node was remote and I just recently got it back under control. It’s a Synology nas that is now in our office. Should I just start it over since it’s DQ’d on a satellite

I’d cap its size to whatever it is using now, then start a second node (to keep getting any ingress). Your old node will still payout what it can… and eventually you can delete it when your new node needs the space instead.

That’s an option too, I’ll look into starting a second node on it. I did just move it to a new static IP so hopefully it will go smoothly.

Hello @ryan,
Welcome back!

Since it’s disqualified only on one satellite, you may delete its data (How To Forget Untrusted Satellites) and continue run the node, the remaining satellites will still pay for the usage.


Well I just got suspension notice on the other satellites. Found a bunch of this in my logs:

2024-07-11T12:54:50Z ERROR piecestore download failed {“Process”: “storagenode”, “Piece ID”: “F75EKFIGPHGAUXSXDGIZXTTUA2OLL6I6VE7BC2IOQIQRBH52K6OQ”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Action”: “GET_REPAIR”, “Offset”: 0, “Size”: 2319360, “Remote Address”: “”, “error”: “pieces error: filestore error: unable to open "config/storage/blobs/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/f7/5ekfigphgauxsxdgizxttua2oll6i6ve7bc2ioqiqrbh52k6oq.sj1": open config/storage/blobs/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/f7/5ekfigphgauxsxdgizxttua2oll6i6ve7bc2ioqiqrbh52k6oq.sj1: permission denied”, “errorVerbose”: “pieces error: filestore error: unable to open "config/storage/blobs/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/f7/5ekfigphgauxsxdgizxttua2oll6i6ve7bc2ioqiqrbh52k6oq.sj1": open config/storage/blobs/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/f7/5ekfigphgauxsxdgizxttua2oll6i6ve7bc2ioqiqrbh52k6oq.sj1: permission denied\n\*Dir).Open:354\n\*blobStore).Open:94\n\*Store).Reader:301\n\*Endpoint).Download:671\n\\n\*Mux).HandleRPC:33\n\*Handler).HandleRPC:61\n\*Handler).HandleRPC:42\n\*Server).handleRPC:167\n\*Server).ServeOne:109\n\*Server).Serve.func2:157\n\*Tracker).track:35”}

Well, usually for unable-to-open errors I’d suggest a fsck… but here it mentions “permission denied” a few times. Was the node moved or copied or something done that would change file permissions/ownership?

No, I did move the box to another location and in the interim Synology had a DSM update. I didn’t change anything else. Time to dig into this a bit more.

Then you need to recursively update the owner for this data to your current user.
For example:

sudo chown $(id -u):$(id -g) -R /volumes/data1/Storj/storagenode

Sadly this NAS has a hardware problem and I’m just replacing it with a different device and letting the data go. There wasn’t much there anymore.

What Synology model will you use?

Honestly not sure, maybe the rumored DS1825+ that should be out “soon”. This is in our office so we could put it to use for other things besides Storj.

If you are replacing it with another Synology you can move disks to the new device as is.

But I would not recommend Synology in the first place for any usecase, especially the newer models. There are better solutions. Synology today is a marketing company, they sell lipstick on a pig to customers that should know better. They have peaked at DS1618+. It’s all downhill from there.

I guess the DSM is the selling point, like iOs in iPhones. People like simpler ways to get things done, and not dive into CLI, and manual settings, and tunings and stuff. They have the most used apps that just work on their OS, and you don’t have to botter with manual installs and settings.
For ex. I set up email notifications in DSM, very easy, with 2FA and everything.
In Ubuntu, I didn’t even tryed because they say something about keeping your password in plain text, and I don’t even know how to bypass the 2FA (gmail), plus the huge list of notifications you can choose from in DSM, I guess it would take months to get them all figure out in Ubuntu.
So… easy to setup and use, this is what you pay for.

Check the models with Ryzen and ECC memory. I believe they are better than Intel ones. And with Ryzen, you can go up to 64GB RAM (Kingston - Micron chips), even though it’s “not supported”. :shushing_face:

Yes, this is absolutely the reason people, including myself, get duped into buying synology.

De facto, this simplicity and eye candy turn out to be a lipstick on a pig, and to get that thing working in a slightly changed environment, or even have multiple sinology tools work together – you have to not only become an expert in command line, but also in how to walk on eggshells around their stupid middleware that screws everything up. Ultimately everyone I know stopped using synology apps – the reason that contributed to buying decision (bravo marketing) – and switched to something else, leaving NAS just serve files.

And even that sucks on synology – the performance is abysmal, samba persistently broken (Time Machine is failing, they only test with windows clients evidently)

And this is not to mention the absolutely abhorrent software quality and security of the DSM as a whole.

They publish the open source packages they mangled, you can verify yourself. Things like calls into opaque shim layer from the authentication path in the openSSH, and in the past they were caught with hardcoded login credentials in there.

It’s just shit all around. Nobody shall use it. Just stay away from that garbage.

Once I realized that I replaced all my synologys with TrueNAS, and my life improved significantly.

This is to address your point of not messing with CLI – everything is doable in the UI, it’s based on a clean (arguably, superior to linux) OS and is stable as an iceberg. I spent zero time fighting it, or working around issues (there were none). It just works. Including third party apps – like Plex, NetData, Storagenode, Homebdrige, anything you want. It’s also cheaper – you don’t take synology marketing chief’s kids through college.

You can do the same with intel.

I’ll show myself out.

Yeah I could go that route, but my instance is already on the downward trend. But the time I got a new NAS installed and drives moved over my uptime would be negligible. I’m just starting it over with something else.

I did have a raspberry Pi 5 with 4TB SSD on it so I went that route to get this started again. Super low power (and quiet) device. Not as much space as the synology but it can sit on my desk next to me and I can’t hear anything.

1 Like

Interesting. Did you DIY the case and setup? How did this go for you the first time you set it up?