uk100

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

uk100's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks, but I don't understand. Access what directly, and from what IP address?
  2. Hi. After a power down, got the "Bzimage checksum error/failure reading flash drive" or similar message on remote management console. NB approx 1 year then passed for various reasons... I've now followed instructions at: https://wiki.unraid.net/Manual/Troubleshooting#Bzimage_checksum_error.2Ffailure_reading_flash_drive: Repaired USB key Restored bz* files from a new 6.9.2. image (same as installed) UNRAID appears to start when viewing remote management console. But no GUI, and I can't see the expected local IP address on my network. Have also tried safe mode. I've attached diagnostics (although oddly, I get a message when doing so, saying ZIP files aren't supported...) I'm not clear what to do next - please advise. Thanks. storage-diagnostics-20230520-1908.zip
  3. Hi, I've just tried to restore some files to /storage and have found, by reading the Github docs, that /storage is read-only by default and I need to make it read-write. But how do I actually do this in unRAID? The 'storage' path config item does not seem to have an Edit button, although Flash and Host PAth 3 do. Am I missing something?
  4. Interesting. In fact that SSD is an Unassigned Device that I'd physically installed and pre-cleared OK, in preparation for using as cache, but had pretty much decided to instead use that last remaining slot for another storage HD for now. I don't have any cache drive. I will fiddle with cables and retest, and also retest with the SSD removed. Now I think about it, I had noticed odd delays sometimes showing the content of the Unassigned Devices pane. Many thanks for your advice.
  5. I meant using command line 'powerdown'. It definitely hung. When all works well, with the couple of Dockers I have running, it takes a only a minute or so, and there's a series of messages at the bottom of the screen which update to tell you what's happening.
  6. Thanks but this occurs when stopping the array, not on attempting to power it down., so I don't think it's relevant?
  7. Hi, bit disappointed by the lack of response. Is there another way I can get support?
  8. Yes, I did that myself for a while when I used SyncBack. Got fiddly as I was moving/renaming files a lot. Had to purge deleted files every so often by doing a 'mirror and delete files no longer on source'. Although I think it is possible to set up Syncback to do incremental backups which makes it a bit easier to manage.
  9. Remember that a simple sync/mirror-type backup won't protect you if you delete files by mistake from your primary storage.
  10. Hi, sorry to bump but can anyone advise? Thanks.
  11. Hi I've been stopping and starting my new array a lot as I start playing with it. I'm finding that most of the time, when I attempt to stop the array, the GUI becomes unresponsive. As expected on stopping array, the array shares become unavailable, flash drive and unassigned devices are still mounted. CLI can still be accessed. No parity or other issues evident with array on restarting via CLI. Any advice? Latest log attached. Thanks. storage-diagnostics-20161016-1810.zip