Try to turn off your machine and disconnect last failed drive, then attach it to another machine and scan with repair with Hard Disk Sentinel program or similar, after connect it back to machine with RAID5 and try to dring your RAID online. Is it mdraid?
Oh boy. I actually recovered the raid (I donāt know for how long) The second failed drive managed to spin, and I got access to the data. Unfortunately, most of he .db files are corrupted. I donāt know how much of the data was affected. Most certainly I could not do a graceful exit. My node was online for about 1 year, and the escrow held is about 200$.
I have already spent most of my day trying to recover the dbs, but to no avail.
I might have to call it quits, and remake each hdd into itās own node, in order to minimise the risk, if iām about to go further.
This āboyā, have another proposition for you
If you alredy bring your RAID5 up and running but canāt recover your dbāsā¦ just delete your dbās (it not a joke) and try run your node.
AFAIK the DBs arenāt even important. Only the data is. I think you should still be able to do a graceful exit if you only have the files and recreate empty db files.
yeah the db can be rebuild, its about getting your data outā¦ however if you might have 50% corrupt dataā¦ depending on how bad it isā¦ i believe most cases of lost data in raid5 will result in 50% corruption might depend on the number of drives thoā¦ i forgetā¦ but so long as you can read the data and try to restore it then you should be pretty okay
you should consider going to ZFS if you donāt mind linux and lots of new troublesā¦ but it is remarkably good at keeping the data goodā¦
SGC starts scrubbing his tankā¦ for the 6th time since fridayā¦ xD
fight the corruption xD if you get it running and your drives are really old, you might be able to make it into a raid6 by adding an extra oneā¦ might be worthwhile as the node grows
ofc that becomes a larger cost benefit calculation, but long term its never the worst choiceā¦ lol
but why would one want to do a graceful exit if he can get a few month more inā¦ that is worth more than the graceful exit would beā¦
besides graceful exit requirements i think are pretty high compared to just crashing and burning a few months laterā¦ i donāt see the cost / benefit aside from maybe if one didnāt have a choice and if it was over quickā¦ which graceful exit isnāt eitherā¦ infact it seems one can barely leave because of a bug with the new satellitesā¦ heh
Ok. Just deleted all db files and restarted the docker container.
Some context: I am running a Vcenter Virtualised raid 5 (5 x 900GB drives) 3.6TB total.
The Storj machine is an Ubuntu with a 3.2TB hdd mapped.
The Docker image is configured with a 2.9TB limit.
I deleted all .db and shm / wal files (including revocations), practically cleaning up the storage directory (except the blob, garbage, temp and trash dirs).
If you have 200$ held amount, a few additional month wonāt cover that. And if he doesnāt do a GE now, his node might get DQed later when too many pieces are missing.
So with a GE now, he at least knows for sure if he needs to start a new node right away.
And GE on stefan-benten would probably be enough, the other satellites donāt have much held amount.
@kevink has it right. I donāt trust my disks anymore, and if I could push the data back into the system it would be great. Later, after I fix my hardware, Iāll try again.
i might be wrong here but from what i remember looking at the earning calculator, the payout for a successful graceful exit was about equal to 2 or 3 months of node operation with 100% payout
so since his node is a year he is on full payout and on graceful exit he doesnāt get paid for downloads and he has much stricter demands on his data integrity and downtime allowanceā¦ and it will most likely take months to complete anywaysā¦
so far as i can see there isnāt any current existing reasons for making a graceful exit worth even attemptingā¦ CRASH AND BURN BABY