PhilDG

Members
  • Posts

    58
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

PhilDG's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Thank you for the advice - I'm rebuilding parity and will probably swap the drive connections sooner rather than later
  2. Hi, I just logged to my server to see a message that my parity disk is in error and has been disabled - it shows a red cross against the drive and a '1' in the errors column Can someone take a look at my diagnostics please? Not sure if I need to get ordering a replacement or if it's just one of those things that happen and a restart would work Thanks so much in advance tower-diagnostics-20230719-2125.zip
  3. Thanks for your quick reply - there was an update available to me which I have installed - will keep an eye when my next parity check starts Thanks again for your help
  4. Hi, like some others here, my log file is getting filled with the following every 6 minutes during a scheduled parity check - I couldn't see if there is an answer to this as yet
  5. Not sure if it's a problem my end but I had Overseer working great. This morning there was an update for the docker which I applied and I can no longer connect - I'm getting 'This site cannot be reached xx.xx.xx.xx refused to connect. I'm using the default settings for the docker - not sure what other information to give
  6. Hi, How do I update the server version. My client is saying server version 1.3.0.0 or higher required. When I load the page on my PC, it says that the new version (1.13.4.5251) is available - how do I update this? I have tried restarting the docker.
  7. It's fair to say my cache is running on a sh*tty old drive - looks like it might be a good time to put in an SSD?
  8. root@tower:/# fdisk -l /dev/sdb Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 63 488397167 488397105 232.9G 83 Linux root@tower:/#
  9. Thanks Squid I have just run FCP in extended mode and got some SMB file permission issues but it doesn't report anything about the cache. Here is the diagnostics tower-diagnostics-20180324-2124.zip
  10. Hi, I've run the upgrade assistant to upgrade from 6.41 to 6.5 and it gives me this message: Issue Found: Cache drive partition doesn't start on sector 64. You will have problems. See here https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?tab=comments#comment-511923 for how to fix this. This link tells me how to change some of my share settings but I don't really understand what I'm trying to do as it doesn't move everything off the cache drive so I don't want to proceed removing the cache drive and re-formatting it. Is this a new issue or has it just been introduced with 6.5? The instructions look as if they have been around a while.
  11. Thanks Squid - that looks to have done the trick. Strange that the setting was automatic but with those ip addresses in the fields. It now looks good to me - thanks for your help
  12. Thanks for the suggestions - the help around here appears so quickly!! I found that my router did not have static DNS addresses so I set those to 8.8.8.8 and 8.8.4.4 I'm getting the error that it's unable to communicate with github and still don't appear to have any access from either unraid or any dockers with the exception of crashplan which seems to connect without any issues which seems odd although I guess it must open up some sort of secure access. I've enclosed the diagnostics tower-diagnostics-20180308-1924.zip
  13. Thanks for the reply - unraid comes up with the GUI just fine so I can presumably use putty or the command line button. When I get the chance next, I will post the diagnostics.