soong

Members
  • Posts

    20
  • Joined

  • Last visited

soong's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Looks like i'm having the same/similar issue... the USB network controller worked fine in 6.9.2 but it's not showing up under 6.10.3 even though it shows up in the system devices: Bus 004 Device 002 Port 4-1 ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN
  2. The current version of ExifTool is 12.41 but I'm only seeing 11.93. Is there something I need to do to update that?
  3. So SMB shares were working fine (although kind of slow but that's another issue) and I wanted to get Time Machine backups working. I enabled the "Enhanced macOS Interoperability" SMB settings and configured the Time Machine shares and that worked no problem. Now when I mount a normal SMB share on my Mac, every time I copy even a single file, it hangs/timeouts and completely hangs the Finder. If I turn off "Enhanced macOS Interoperability" everything works fine (without the Time Machine shares). I have UnRaid 6.9.2
  4. So I currently have a shell script that lives on another computer and I'm trying to figure out how to move it to UnRaid... besides moving some files around it calls mkvmerge (from MKVToolNix) and HandBrakeCLI. I have both MKVToolNix and HandBrake installed as Dockers, but I don't quite understand how I'd would get a shell script to be able to access both (or either for that matter). Do I need to combine them into one Docker somehow? But even then where would I run the script from? I guess I could setup the whole thing as a VM but that seems overkill. Is there a better way?
  5. This is a follow up from my other thread... My setup is as follows: I have a SAS controller and a SAS expander. I have 4 of the drives in a trayless rack that I hot swap in and out for backups. I have 1 parity drive and 5 data drives. So if all 4 backup drives are in that's a total of 10 (spinning) drives (and 1 SSD cache drive) Most of the time the following situation happens... 1) Insert Drive A, shows up in Unassigned Devices as expected 2) Insert Drive B 3) Drive A disappears 4) Drive B shows up 5) Drive A comes back, usually by itself within a few seconds, if not I have to pull it out and reinsert it. I've tried the following: 1) I turned off all the other drives so this happens with only 2 drives in the system 2) Bypassed the trayless rack and same thing happens, so that doesn't seem to be the issue 3) Tried a different modular SATA power cable, same issue 4) If both drives are powered up and I plug and unplug the SATA data connectors everything works as expected, so it doesn't seem like it's a controller issue. 5) If Drive A is powered up and data is connected it shows up as expected. If I plug in only the power to drive B, Drive A disappears for a few seconds just like above. 6) Also have intermittent issue with booting up with all the drives on - which again points to the power supply So test 5 leads me to think the issue is with the power supply? I have a Corsair CX Series 750 Watt 80+ Bronze from 2016. I would think they would be more then sufficient for my setup? Any thoughts?
  6. I'm looking over this page: The parity swap procedure It sounds like something I might want to do in the future, upgrade my 10TB parity drive to 12TB and then replace the the 10TB drive with a (working) 3TB drive. What's the advantage of using the swap method vs just doing it in two steps. 1) Upgrading the parity drive and then 2) Replace the 3TB drive?
  7. I'm using this removable drive bay: StarTech.com 4 Bay 3.5" SATA SAS Backplane anything else I need to consider?
  8. Yea, I think the hot-swapping is what's causing the issue. Although I'm surprised I haven't had more trouble with this. My main array drives are connected via a SAS controller. My backup drives (which I hot swap) and the cache drive are connected to the motherboard SATA ports. It looks like my motherboard (from a ThinkServer TS140) doesn't support hot swapping so I guess that is causing issues... I've been meaning to order a SAS expender card. If all the drives are connected via a SAS controller it should be safe to hot swap them?
  9. Ok, it just happened again... this time I had only attached the 2 drives, I hadn't even mounted them yet. I had to shutdown (reboot didn't work) and restart before the cache drive showed up again... weird soong-diagnostics-20201012-1407.zip
  10. I was trying to preclear a couple of disks and when I mounted the 2nd one (I think I had a total of 4 unassigned drives mounted at that point) my cache disk disappeared (I didn't notice at that point). The next morning when I noticed, I rebooted and it didn't come back I feared it was dead... I then rebooted again but removed all the unassigned drives and it showed back up... and it works fine. Any ideas? 10/09 - 19:54 - Mounted Drive 10/09 - 19:55 - Started getting BTRFS errors - Around the same time I got a notification about my Cache drive missing but I didn't see the notification 10/09 - 19:56 - Started Preclear (already had one running) 10/10 - 08:55 - Noticed Cache drive is missing - Stoped Array 10/10 - 08:55 - Rebooted - Cache drive is not listed 10/10 - 08:57 - Rebooted - Cache drive is still not listed 10/10 - 08:58 - Rebooted - Cache drive is still not listed 10/10 - 09:10 - Shutdown - Remove all non-array drives from system - Power On - Cache Drive shows up (Samsung_SSD_860_QVO_1TB) 10/10 - 09:14 - Rebooted - Cache drive still shows up log.txt
  11. FYI, I figured it out: Docker -> Add Container -> Select a template -> Click red "X"
  12. I installed the VNCWebBrowser and it worked fine it just required a password to login it, I tried to remove the password by removing the password option under "Update Container" now I can't login at all. I tried removing the container and re-installing but it keeps remembering my previous settings... I also don't see anything saved in appdata for this container.
  13. Hoping the logs might show what keeps causing this crash... I'm coping files from an Unassigned Devices drive (HFS+) to a share using binhex-krusader. Most of the time things work just fine but the last two times Krusader crashed and wouldn't start back up. I then couldn't stop or start any dockers. When I tried to stop Docker altogether under setting it hangs. The first time I was able to stop the array but the 2nd time I wasn't. I tried rebooting and shutting down but it seemed like something was hanging the processes. I tried hitting the power button once to force a clean shutdown but that didn't seem to work either (it's possible I wasn't waiting long enough). I had to do an unclear shutdown. Everything was fine when I rebooted but it needed to do a parity check (the first time was fine, the 2nd time just started). I'm mounting the drive using a dock if that makes a difference. Any thoughts? soong-diagnostics-20200328-1016.zip soong-diagnostics-20200326-1128.zip
  14. Ok, thanks... it worked no problem... I was like 90% sure that would be the case
  15. I accidentally booted up w/o by cache drive connected... I didn't start the array but for some reason it showed up as "unassigned" vs "missing". I rebooted and it looks normal (I can see it in unassigned devices as a "btrfs" file system)... When I assign it to the cache slot it comes up as "New Device". It is safe to start up the array like that? Will it recognized it or will lose the files that are on it?