January 10, 20242 yr Unraid was running perfect. Installed a docker app Photostructure and could not connect to the webui (using bridge mapped to a port I selected) tried some variations and no go. Did some searching looked at my network.cfg but did not change anything. rebooted and now.....nothing. Do I rebuild the flash drive? Prior to this I had just finished installing a parity drive (took two days done this AM) and new hard drives and did not yet back up my flash drive again sigh. am I hosed? Edited January 10, 20242 yr by CALMSURF typos
January 10, 20242 yr Author Here is the update. Still dead in the water after reflashing the same USB drive which seems fine from a windows PC. I copied the whole config file from the drive before flashing and added a few files back on to it after: the shares folder, pools folder, basic.key, disk.cfg, ident.cfg and super.dat. I have a black screen with a flashing white cursor int he left hand corner. Picture attached. UNRAIDSTUCKATFLASHING CURSURmp4.mp4
January 10, 20242 yr Community Expert Difficult to say what the problem could be with the information provided, is that flashing white curser before or after the Unraid boot menu? You can post a longer video showing the complete post.
January 10, 20242 yr Author Solution and I am back and running. Sometimes it is the little things that we miss. I wanted to explore pools with a cache drive and configured one using a USB attached SSD which it would seem is a good idea until you reboot? I disconnected it and unraid booted fine and shares and the data is all there so whew. I still have some docker specific issues but that is for a different post. This one can be closed and hopefully someone learns from my dumb mistake.
January 10, 20242 yr Community Expert 1 minute ago, CALMSURF said: and I am back and running. Sometimes it is the little things that we miss. I wanted to explore pools with a cache drive and configured one using a USB attached SSD which it would seem is a good idea until you reboot? I disconnected it and unraid booted fine and shares and the data is all there so whew. I still have some docker specific issues but that is for a different post. This one can be closed and hopefully someone learns from my dumb mistake. I suspect that the BIOS on your motherboard was trying to be 'helpful' and trying to boot from the USB SSD !
January 10, 20242 yr Author Now I get to figure out my original issue that caused the reboot - why I cannot connect to PhotoStrucure docker (webgui, console, logs) at all. Says started but doesnt seem to work at all.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.