denishay

Members
  • Content Count

    62
  • Joined

  • Last visited

Community Reputation

6 Neutral

About denishay

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. oh, and yes, I'm using an LSI controller with flashed IT mode bios
  2. Hi John_M, Thanks for the tip. I think I'll abstain flashing the card, as I'd like to keep the option to have a BIOS with it, just in case. An upgrade of my ancient hardware is stll more than overdue. I'm just waiting for a better moment, as right now hardware prices are inflated out of proportion. It's still working... it's just that this old BIOS limitation forces me to remove 2 drives after shutdown and connect them again during boot, once Unraid starts loading. If I had to reboot my server often, I would consider the flashing operation you mention, but right now, it
  3. Hi all, FYI, I made an important discovery today when updating my Unraid from 6.8.3 to 6.9.1. Right after the update, I couldn't boot on USB anymore. The USB drive wouldn't even show in the list of choices in my boot menu. I thought "OK, bad luck, the last batch of writes did it and this older USB drive is dead"... I take my backup (yes, I do backup everything, including the boot flashdrive), create a new drive... and same thing. The brand new out-of-package USB key (kept a few spares just for cases such as this one) wouldn't boot either. I will spare y
  4. A PCIe gen 4 SSD as cache is a real waste if all you have as network behind that is gigabit Ethernet. You'll be limited to receiving/sending at approx. 100 MB/s. even a SATA SSD will consistently deliver way more than that.
  5. FYI, still works fine with unraid 6.8.3 and sysstat-11.2.1.1-x86_64-1.txz
  6. OK... I have found a solution, and writing it here as it may help others troubleshoot passwordless SSH connections. I knew I had done everything right and couldn't find why it was working with passwords entered bu not without. The whole key is in the "-v" (verbose) option of the SSH command which allowed be to see all the steps and find out what was wrong. As a reminder, host is unraid and the remote guest is a raspberry pi under debian 10 lite (without desktop). As you can see, all it took was to rename the public certificate and upload it to the host.
  7. I'm at a loss after 3 days of research and many reboots on this. I am trying to create a "safe" connection between my unraid and a raspberry pi which will ultimately be remote. I am using raspbian lite 10 on the raspberry. I have already installed wireguard on it and it connects to unraid successfully at each reboot. So that's for the "safe" tunnel in between the two. Unraid (10.253.0.1) can ping and ssh into the raspberry pi (10.253.0.3) using the IP address between brackets, and the other way around. So SSH works wonderfully... but only by entering the password.
  8. Hi turl, The shares on the array was a temporary thing as I wanted to try and sort out the current issues before setting them back to use the cache. I had tried to delete the docker image and install dockers again, but it dien't work at first. So I went a bit brutal and stopped the array completely, removed the two cache drives and let them in unassigned devices where I removed their respective partitions. Then I added them back as cache, let unraid format them again and clicked on the Balance > Convert to raid 0 once more. This time everythin
  9. Some more info. I saw there was a BTRFS check feature whent he array is in maintenance mode, so I tried that, but it can't find any errors: [1/7] checking root items [2/7] checking extents [3/7] checking free space cache [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdl1 UUID: ***removed*** found 206969012224 bytes used, no error found total csum bytes: 149267328 total t
  10. Hi all, I could really use some help to get back the possibility to run my dockers. Here is the situation: My unraid 6.8.3 had a fully happily functionning array of various disks and a 250 GB SSD as cache drive (xfs). My VMs and dockers image are by default on the cache drive too for performance reasons. I happen to have gotten another 250 GB SSD drive and thought I would use that second SSD and use that new 6.8.3 support for BTRFS pools to set the two as raid0. So here I go, stopping my array, extending the cache to two slots and add
  11. Hi, You are right. It is not possible anymore. The "for business" line of Crashplan never allowed that. And Crashplan discontinued their older solution for consumers. So you cannot do that anymore. A pity as I see lots of added value there, but I also understand, knowing that their cloud backup service isn't limited in size (or you could potentially backup many workstations to one, then have a subscription only for that last one).
  12. What I like the most about Unraid is the ease of use of dockers. It's so easy to add new functionality to my home lab with that. And what I would like to see the most in 2020 is an easy to use back up system (not just sync) from unraid to remote unraid. It is doable now but requires quite a lot of setup.
  13. Lost completely all connection to the server twice already since 6.8rc3 upgrade yesterday. Can't even connect via SSH, I am forced to hard shutdown/restart Unraid. I wish I could help debug that by providing diagnostics, but can't as my server is headless. I had it running 6.7 stable previous to that for several months in a row without any problem. Going back to 6.7 Not sure what went wrong with 6.8 really. The loss of connection was complete, not only a web UI issue, but even at the router level, neither Unraid nor any of the dockers with their own IP showed up. Running on an old but rel
  14. What I do is that I have indeed Nextcloud have its own files on /data and I create an extra mapping pointing to my unraid data that I add as external storage on Nextcloud.
  15. You're welcome. Yes, sorry, my nextcloud is using an older PHP (I downgraded it manually for an older version update which wasn't supported with PHP7). Had even forgotten about it since.