mynodebtc / mynode

The easiest way to run Bitcoin and Lightning!
Other
648 stars 146 forks source link

"Looking for Drive. Please attach a drive to your myNode" #485

Open TheTotalConnector opened 3 years ago

TheTotalConnector commented 3 years ago

Hey, never had this issue before. I had already the latest upgrade-version on mynode (-premium). After my login into my dashboard did not work, it asked me to reboot. So, I tried that 3x. But every time, eventually it told me: "Looking for drive. Please, attach a drive to your mynode". I have a solid (Casa2-) harwarde with a Rasp4 (extra ice-tower and cooling pads etc.). Unfortunately, I wont be back home on my local network for some time. I tried remounting the drive in settings, but this did not work either. Another option would be to "reformat" the drive, but I am afraid of risks / partial destruction etc. I was told to tests another USB connection (USB 2 instead of USB 3/ black instead of blue??). What surprises me is why now...and I really hope it is not some serious hard-or software -issue... Before ordering some 3.0 hubs or whatever according to this myndodebtc-guide , http://mynodebtc.com/guide/debug_cannot_find_drive, , I would appreciate any other suggestions or guidance.

Thanks.

Describe the bug A clear and concise description of what the bug is.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

MyNode hardware (please complete the following information):

Additional context Add any other context about the problem here.

tehelsper commented 3 years ago

This is typically a hardware issue or corruption on the hard drive. Power outage, bad power supply (or going bad) can all cause this. It typically means you just need to reformat the drive (optionally connect to PC and try to recover any data you need).

If it had been working, my guess would be hardware failure or random corruption (likely due to hardware starting to go bad) or maybe just bad luck.

Jacksper13 commented 3 years ago

@TheTotalConnector were you able to resolve this?

definitivequestion commented 3 years ago

One thing you might try is changing the bootloader by running raspi-config. Sometimes I need the latest boot firmware and other times I need the default firmware. I also unplug my drive. Finally, if the drive is detected and MyNode failed to mount it try mounting it manually.

zsojma commented 2 years ago

I had the same issue after failed upgrade of MyNode software. Instead of reformatting the drive, I tried to download the newest SW from web and flash the SD card. It worked and I didn't have to restore any data! ;)

chazoidgmail commented 2 years ago

I had the same issue after failed upgrade of MyNode software. Instead of reformatting the drive, I tried to download the newest SW from web and flash the SD card. It worked and I didn't have to restore any data! ;)

Thanks for this piece of advice since I am having he same issue. I am going to try this in the next few days.

tehelsper commented 2 years ago

I had the same issue after failed upgrade of MyNode software. Instead of reformatting the drive, I tried to download the newest SW from web and flash the SD card. It worked and I didn't have to restore any data! ;)

Thanks for the info. Did you happen to check the mynode log on the status page before re-flashing? That may have pointed to the specific error.

chazoidgmail commented 2 years ago

@zsojma - I flashed the SD card last night with the latest software (on a new 32 GB SD card - previous card was 16 GB) and that seemed to work - now am re-running the software upgrade since mynode told me the previous attempt at the upgrade didn't complete properly. This upgrade has now been running for around 6 hours. I wonder if that's right. I am getting a message that says don't power off or unplug the device so going to let this run a bit longer. But I wonder if it's now caught in an endless loop of some sort.

tehelsper commented 2 years ago

It could be stuck. Can you see the upgrade log and see where it stopped?

Also, what did you flash? The RP4 image is on v0.3.0 already.

chazoidgmail commented 2 years ago

Here's the last several lines of the upgrade log. I am not very technical so this is all completely not understandable to me. In many ways I have no business trying to run a node but I am trying to be part of the BTC "hive" so to speak.

image

chazoidgmail commented 2 years ago

@tehelsper - also to try and answer your second question regarding what did I flash. Here is what I "flashed"

image

tehelsper commented 2 years ago

Check the top of the log, it's inverted (newest at the top).

chazoidgmail commented 2 years ago

Thanks @tehelsper - shows you what I know! Here's the top of the log as I send this:

I see "upgrade complete" - If that's true that would be great news! Yet it's still "updating". Maybe time to reboot the whole thing? Appreciate your insights.

image

tehelsper commented 2 years ago

Yeah, try clicking on the mynode logo.

chazoidgmail commented 2 years ago

@tehelsper: I ended up doing nothing and walking away from the computer, lol. This morning I came back and looked. Everything is updated! And the mynode is back on line and up to date! Thanks for your help!

chazoidgmail commented 2 years ago

@zsojma also want to thank you for original idea to do the SD card flash. That was got me to eventually solve the original problem which is the "looking for drive" issue. At one point @tehelsper asked why did I flash, the "RP4 image is on v3.0.0 already". But I don't think it was since on the status page (which I previously didn't mention) under "devise type" I had an error message telling me to upgrade from a 32 bit image to a 64 bit image. At first I didn't know what that meant and I believe the flash solved that since that error message is now gone. Thanks to another friend of mine, I also bought a 32 GB SD card and flashed that. The card that came with the mynode when I bought it at the end of 2021 came with a 16GB SD card. Whether the 32 GB SD made a difference I don't really know but I suppose putting in a larger capacity SD card can't hurt.

tehelsper commented 2 years ago

Good! The re-flash definitely solved the 32 bit warning and going with 32GB was a good idea. I'm switching to use them now.

zsojma commented 2 years ago

Thanks for the info. Did you happen to check the mynode log on the status page before re-flashing? That may have pointed to the specific error.

Sorry, I didn't check them. I don't think I was able to get to the status page at all... Not sure now.

want to thank you for original idea to do the SD card flash

You are welcome. Glad to help.