Help! Sia-UI lost my Storage Foldrs



  • I just restarted my computer after one of Windows' updates and under "Hosting" when I scroll down to the "Add Storage Folder" section, where I had 6+ TB of storage I now have none :-(. I went to add a storage folder back by remapping it to the same location but it says 1699 GB Free of 1699 GB. I had my other shared folder on a WD MyCloud drive and now that won't map anymore at all. Host -v in terminal shows only the folder I've remapped to and 0B used. I can still see my 250 risked SC and 16KS Locked as collateral. Is there anything I can do here to recover from this mess?

    https://siahub.info/host/5355



  • So I remapped them both, and I imagine by remapping them I just overwrote the whole siahostdata.dat file crushing all the data I had. So that's pretty unfortunate...



  • No change today. Still acting like I don't have any data. :-(


  • Global Moderator

    @RatchetA10 if you lost your cache of files then you cannot recover them. The next version allegedly will have a recovery option. maybe someone like @reinisp can help.

    Make sure you tag me @bryan if you need to me respond.
    Forum Mod. I cannot fix transactions. I can't help with Mac or Linux.
    alt text
    Unofficial Web Based Siacoin Wallet. No more syncing.

    0


  • @RatchetA10 @bryan
    Unfortunately I am not a magician able to recover remote files...
    Honestly I have no clue what went wrong with Sia during that Windows update.
    I can only guess the possible reasons why Sia lost its hosts metadata.
    For example, windows restarted at the unfortunate point of time and the host metadata did not get saved to disk correctly (some file in %AppData%\Sia-UI\sia\host).
    Or, the shared folder was not accessible (was not mapped) when siad was started.
    If it was the first guess, you were doomed already. Let me quote Taeks post on the Hosting Handbook:
    It's a good idea to keep the actual wallet folders themselves (the host, wallet, consensus, etc. directories) running on raid10, or maybe even triple mirroring. If you lose those, you lose the whole host.
    If windows had damaged these files even tripple mirroring wouldn't help.

    If the files were not damaged but only the shared folders were unavailable, you have "fixed" the problem from the wrong side and damaged (overwritten) the host files with a fresh empty host configuration.
    That is normal, I have "fixed" (made irrecoverable) some problems too when panicking and trying to fix without investigating the problem cause.

    You could look into the host contract manager log file for what happened. For example, I see in my log:

    2017/05/23 20:43:26.969049 persist.go:83: ERROR: unable to open the /storage1/siashared1 sector metadata file: open /storage1/siashared1/siahostmetadata.dat: no such file or directory
    2017/05/23 20:43:26.969160 persist.go:89: ERROR: unable to open the /storage1/siashared1 sector file: open /storage1/siashared1/siahostdata.dat: no such file or directory
    

    This was when the shared folder was not mounted...

    In any case I doubt there is a possibility to recover now and the only thing you can do is take the lesson to not panic, look for problem causes, ask for help if unsure before the applied fix.
    A day offline at Sia is less bad than a wrong fix (lost metadata).



  • Definitely panicked. One of my 4 raid 1+0 drives just failed and I was taking out the clicking one when I restarted and sia came back up with no host folders. Sad. Anyway, I assume I'll lose the "risked" collateral but the "locked" collateral should come back to me eventually right? Can you think of any reason why 0.04 SC are being withdrawn from my account still every day?



  • @RatchetA10 said in Help! Sia-UI lost my Storage Foldrs:

    Can you think of any reason why 0.04 SC are being withdrawn from my account still every day?

    Are you a renter on the network, i.e. uploaded files, or at least enabled the renter module? You should disable that if you have no files uploaded that you'd like to keep. Command is something like

    renter allowance cancel

    if memory serves me right - I don't rent, and never did.



  • @maol not a renter, never had



  • any idea how to re create the connection to a lost set of folders. I did not re map anything yet, but I have similar issue, where I've hosted a lot of files but a corrupted json file made teh files dissappear. I have the files intact in my drives but the SIA client does not know it. Any idea when there will be a self-repair funtion for the hosted files, when they are in fact not lost, but SIA itself messes up??



  • Just an idea.
    Could there be a possible "backup"? Maybe you can look for "shadow copies" or something similar?
    I've seen sometimes that "shadow copies" or "previous versions" are available for some files...
    I am pretty sure Windows makes some sort of backup during updates, but I have no clue if Sia metadata is backed up.



  • @reinisp: I've been down the route, with no success :-( ... I think this is a classic case of basic functinality being broken by design - the json files in the roaming directory seem to be the central nerve system hostclient, and being at risk of degenretating the whole system is weak (at least on windows).. A quick browse in this forum reveals a lot of issues on that front, and I've had it before on other roaming json files and the frequency of the error did go down (which was why I stopped backing those files up !) a lot with recent versions. Previously I was always able to repair it with out any loss of collatteral and files. This time the devil caought up on me and I'm facing a loss of 335 contracts and a lot of collatteral. Sia is still a bit from being really stable. Being a host it is obviously that your data is at stake and that is your main responsibility, but that the client it self corrupts this often isn't good enough - I have to conclude this even I'm a big big fan of the project.



  • @reinisp @larsfloe
    I don't have anything intelligent left to say. Hosting Sia was a pretty big failure on my machine. Granted I made a mistake, but only after Sia-UI made a HUGE mistake as the result of a forced restart. These are the kind of things that will hold this project back. Nobody has the time to read every post by taek before setting up their host. Don't mistake me for a complete idiot, I've done some good work with Raid 1+0 and symbolic links to get this all running, though I do understand I'm probably below average for someone running a host. But, for now I'll probably just try to move all my sia out of this wallet, so I don't keep losing this .04 SC multiple times per day, but keep watching the wallet hoping the locked (but not risked, that's gone) collateral returns.

    If I had one input from this, the Sia-UI absolutely needs a close or exit option so it closes happily and doesn't lose it's mind on a restart.

    Still a big fan of the project, but unfortunately I'll be sitting on the sidelines from here on in.

    Will



  • @reinisp @RatchetA10; I've been following this project for a year and so.. And that the very heart of the system, the hosting software, is stil THIS vulnerable should make the core team re think and re priotize what to focus on. They must provide a stable platform! The bad state of the client is contradicting the whole idea; to make free disk space available to the public. For the most hosts (average Joes) that would imply fire and forget with out to have to worry about updateing, repairing and backing up odd json files deep deep inside a folder structure you don't even know. Comparisons might be unfair but I've had Storj on the same windows machine exposed to the same windows crashes and updates. Not a single hick up, not any loss of data and actually I was able to make a small profit on that system, which I haven't had the chance with SIA due to the lack of storage demand and my recently loss of funds. SIA core team is remakably invisible in thsi forum and when reaching out to them on discord I get no feed back either.. When reaching out to Storj support, I always got an answer. I don't hope SIA is about to stop the project - Meanwhile they are also now a HW-provider, but for what reason when the basic functionality is far from operational!??



  • I totally agree with you @larsfloe @RatchetA10 .
    This is a huge weakness of Sia. I have impression the Sia team is still too small. Or we expect too much from the current state of the project.
    I think this year was suboptimal (not to say bad) for the Sia as the devs were first distracted by the sudden increase in users/usage/price (wallet scaleability issues) and the ASIC project later. All the issues are to be solved sooner or later, but the current concentration on the renters side is not enough.

    For storage users (renters) it is irrelevant that hosts have their problems and lose data as the data is protected by redundancy. And it is important for hosters Sia attracts more users/renters. So I understand the devs decision to improve the renters side. And that is good for the whole project.
    The problem is, if they completely forget about the hosts they will end up lacking storage space for all the happy renters...
    I have no clue what exactly causes the json persistence problem and/or how could that be fixed. I just suspect that a quick and dirty solution would either degrade the performance significantly or push some inconvenient tasks to the hosters. For example, the metadata persistence could be realized through putting it into a DB (maria, postgre or whatever) but would not be acceptable by most of the "hobby scale" hosters.



  • Just happened again. There's nothing in my host.log that indicates an error. Trying a couple restarts and we'll see.



  • So after the restart, Sia says I have no shared folders. Both of my shared folders still have their data. Here's the errors in my contractmanager.log:

    2017/12/13 12:33:14.034288 writeaheadlog.go:285: WARN: WAL file detected, performing recovery after unclean shutdown.
    2017/12/15 23:16:47.959503 writeaheadlogsync.go:50: SEVERE: ERROR: unable to atomically copy the contract manager settings: rename C:\Users\Will\AppData\Roaming\Sia-UI\sia\host\contractmanager\contractmanager.json_temp C:\Users\Will\AppData\Roaming\Sia-UI\sia\host\contractmanager\contractmanager.json: Access is denied.
    2017/12/16 21:35:57.964665 writeaheadlogsync.go:50: SEVERE: ERROR: unable to atomically copy the contract manager settings: rename C:\Users\Will\AppData\Roaming\Sia-UI\sia\host\contractmanager\contractmanager.json_temp C:\Users\Will\AppData\Roaming\Sia-UI\sia\host\contractmanager\contractmanager.json: Access is denied.
    2017/12/17 22:59:04.304914 dependencies.go:200: STARTUP: Logging has started.
    2017/12/17 22:59:04.316416 writeaheadlog.go:285: WARN: WAL file detected, performing recovery after unclean shutdown.
    2017/12/17 23:17:58.178448 dependencies.go:200: STARTUP: Logging has started.
    2017/12/17 23:17:58.185450 writeaheadlog.go:285: WARN: WAL file detected, performing recovery after unclean shutdown.

    Not really sure why access is denied to anything. Sia-UI is set to open up as administrator. Any thoughts?


Log in to reply