Ned

Members
  • Posts

    296
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ned's Achievements

Contributor

Contributor (5/14)

2

Reputation

  1. Thank you, I freed up some space and re-balanced the pool and after a reboot all is good. Much appreciated!
  2. Woke up this morning and all of my VMs were paused. I forced stopped them and tried to restart them but it said there was no space available. They run off my cache which is a BTRFS pool of two SSDs. The pool has free space, only 391GB used out of 500. I tried running a balance on the pool but it said it wasn't required. Rebooted the server and now my VMs don't even show up in the list nor do my dockers which also ran off the cache. I can still connect to the cache via SMB share and all of the files are there and there does not seem to be any issue accessing or opening them. It does not look like there is any corruption of the data. Any idea what is going on? Diagnostics attached. tower-diagnostics-20230822-0813.zip
  3. So I added in a Broadcomm BCM5751 Gigabit PCIe x1 card. Seems like everything is working fine but this morning I see hundreds of the following entries in the system log... does anyone know what is going on here?? Dec 1 03:53:54 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Dec 1 03:53:54 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000040/00002000 Dec 1 03:53:54 Tower kernel: pcieport 0000:00:02.0: [ 6] BadTLP Dec 1 03:54:02 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Dec 1 03:54:02 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Dec 1 03:54:02 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000040/00002000 Dec 1 03:54:02 Tower kernel: pcieport 0000:00:02.0: [ 6] BadTLP Dec 1 03:54:04 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Dec 1 03:54:04 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Dec 1 03:54:04 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000040/00002000 Dec 1 03:54:04 Tower kernel: pcieport 0000:00:02.0: [ 6] BadTLP Dec 1 03:54:08 Tower kernel: pcieport 0000:00:02.0: AER: Multiple Corrected error received: 0000:00:02.0 Dec 1 03:54:08 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Dec 1 03:54:08 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000040/00002000
  4. My server recently started "pausing" every so often for a few seconds. I first started noticing it when streaming media to my Nvidia shield TV. The media would just freeze (since the data flow from unraid stops during this time) and then a few seconds later it would resume. This can happen several times per hour. Investigating this further, I noticed that if I'm in the web GUI when this happens, the whole GUI locks up. The CPU load bars stop moving, I can't click on anything. I wait about 10 seconds and everything comes back to life. Then I looked in the server log and noticed what looks to be the NIC periodically having "hardware unit hangs". This is the onboard NIC for my Gigabyte X99-UD3P-CF motherboard. I have not tried putting in another standalone NIC yet as I wanted to see if anyone could have a look at the logs first and tell me if the NIC looks to be bad, or if something else could be causing this? I've attached a snippet of the log file for reference. Thank you in advance for any advice! Unraid Log Nov 28.txt
  5. Anyone have an answer to this question?
  6. I just upgraded from 6.3.5 to 6.4.1. Everything looks good except that if I click on any of my running Win10 VMs and try to web-VNC to them via the unRAID GUI, it doesn't work anymore. All I get is a black window pop up with a small multi-coloured garbled strip of pixels at the top. Is this a known issue in 6.4.x? If not, is there anything I can check? I can RDP into the VMs just fine but this sucks because it was easier and faster to connect via the unRAID GUI.
  7. Makes sense but it depends on how important the data is that you are backing up as well, vs the cost of backing up. Backing up PCs that don't store any user data locally as an example is not worth keeping three copies - if your PC failed and you lost your backup you can still re-install the OS and any other applications. And user data is often also stored in the cloud on Dropbox or something like that as well. But overall it's a good rule of thumb.
  8. I think I figured it out. I needed to allocate more memory to the crashplan app.
  9. The new CrashplanPRO docker was working fine however halfway through the de-dupe process it is constantly crashing on one particular file/folder it seems. Crashplan keeps restarting. Eventually it says it cannot connect to the backup service. I verified my account and connectivity are ok. Any idea what could be wrong?
  10. Personally I back up all of the computers in the house to unraid and then that is backed up to the crashplan cloud. That solves the problem and you only need to pay for one crashplan device license if you do it that way.. so I never personally used crashplan home's computer to computer backup feature. Also consider that if you back up your PCs to unraid, is it even necessary to then back up those backups to the cloud? After all, they are backups already and the original files are on the PCs which are still running... with that in mind I actually exclude pushing those PC backups sitting on unraid to the crashplan cloud and only backup the content on the unraid box that does not live anywhere else... I know everyone will have their own unique situations but that strategy works for me.
  11. Thought I'd post an update for those in a similar situation... Just migrated my account to Crashplan for small business, installed the new crashplan pro docker and did the adoption process since I was using the gfjardim docker previously. Adoption was virtually instant, it recognized all of my files and folders that I was backing up previously. Left the new docker 100% full default settings. It also creates it's own appdata folder so just needed to shut down the old docker and can go delete the files/folder from it later on. It is now synchronizing block information, been running for 20 minutes and already 10% complete on a total backup size of 3.4TB so in roughly 3 hours it looks like it should be back to normal! For a 75% discount for 12 months plus retain the existing subscription term and can cancel at any time, I think this move was a no-brainer - at the very least I will have until early 2019 to decide if I want to continue and pay the $10/month or go somewhere else...
  12. Thanks for the info! Yes, I am using the gfjardim docker... so I will look through the link you provided. Appreciate the help!
  13. I was about to post this same question. Does anyone know if the existing unraid crashplan docker will work if we were to migrate to a crashplan for small business account? The discount they are offering for the first year is very compelling and would give lots of time to consider alternatives and in my case, not have to re-upload 3.4TB of data somewhere else. So again, does anyone know if the existing unraid crashplan docker will work with a crashplan for small business account? Thanks!