What's going on here? Why was my node disqualified?

I happened to see on the dashboard that my oldest node (41 months) was disqualified. Why???

My node has been migrated to Hashstore for weeks and was running without any problems. The HDD also has no issues.

I was offline several times in the past weeks, my ISP had problems, but that should be fixed now. And it was only 2-3 hours, not days, not weeks. And now I get disqualified? I had an uptime of >85% and >95% audit.

I also wasn’t informed by email! There’s nothing unusual in my log file either.

I am still receiving data.

I’ve been a SNO for 6 years and never had problems! Is Storj shutting down its business and secretly turning off nodes???

I ask for my node to be reviewed.
1soeCdzgKjmfANohriuA5j6mrUSAnpUAhS3zXNMbhL8L6wYgCJ

Thanks

You can check it why:

Disqualified

October 9, 2026

Reason: Audit Failure

Your node managed to lost or corrupt pieces :person_shrugging:

Since it’s disqualified not on all satellites, the remained ones will still pay you. However, usually if the data is corrupted, then other satellites will likely disqualify it soon too.

Please, figure out, why is it happened to do not have the same issue for your new node (if you would like to start over).

Are you serious right now?

My node was online for almost 4 years.

I’m not talking about the online score. It’s disqualified for failed audits. It happens, when a lot of audited pieces are failed:

  1. Your node was online
  2. It returned “not found” or a wrong hash, or didn’t answer three times in a row on the audit or repair request for the same piece.
  3. Made this a lot of times, to have the audit score below 96%

So, I’m pretty serious, please check your logs, why your node is failed to pass audits to fall below 96%.
We are not talking about uptime, the data is either lost or corrupted.

Could it be that your machine have memory corruption A short (xmas?) story on silent failing audits

Have you checked with a fsck/chkdsk/scrub? Even if one Satellite already DQ’d you, it’s still worth looking to hopefully protect others from also failing audits. I’ve seen that happen a couple of times: where the node was online fine… but the filesystem was unhappy :slight_smile:

upload bw saturated? node cannot audit.. probably

This is why. You lost massive amount of data and audit caught it.

Describe your setup. There must be something very wrong that you keep losing (including corrupting) data. If you lost node data you probably are going to also lose your important data. Do this for yourself, not storj. Storj does not care if you lose data - that what audit and redundancy is for.

It can be poor power supply (replace with a known good one) or cables (replace, not from amazon), or memory (run memory test available on your platform, like memtest86), or storage itself, or filesystem (if it’s NTFS for example, and you look at it weird one day lol)

Audit requesting only a random part of the piece, so it is a few kb. If the node cannot read a few kb from the disk, it’s indicating a problem with the hardware.

I mean , upload is getting hammered recently , luckily not out doing my 1000mbps upload though

We’re getting dozens of kilobytes per second, DOZENS!!

i had this happened. but eventually it came back. I think i had a bad hard drive. Or was it a router setting that was not letting things upload.

Their node is disqualified for the lost or corrupted data, so I believe that you comment should be in the another thread, right?

i think my node at the time failed to upload things so my audit score went down. My router had a duplicate gateway which caused a conflict. When my cable modem goes offline it gives out local ips. and the router picket it up. anyways that was one of the strange issues i had. I have an edge router. the only way to fix it was a reboot. The ip it grabbed even though it had a public ip messed things up as it conflicted with its local ip. So packets went to a black hole. Another issue i had one time was the port was closed, as some requests use a different port then my firewall rules had. so i had to patch that.

What if the node is not able to respond to audit requests? wouldn’t the score go down?

What do you think?

There is this one trick storj does not want you to know – if you never respond to audits you can never fail audit, and therefore never get disqualified.

It’s sarcasm.

By default, when audit and node fail to response, satellite will put it back to reverification queue table, it will try 3 more times (in total of 4), if storagenode still fail to response, it will fail audit.

Oh FFS. If you have reproducible bug – provide steps and mechanism, better yet, report on GitHub. If you can’t - STFU.

It’s easy to reproduce - just pull the AC cord.

Using hashstore from it’s start, hundreds of random resets, 0 nodes DQ