Jump to content

olschool

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

1 Neutral

About olschool

  • Rank
    Newbie
  1. I love his topics as they have all proved to be very helpful. With the different ways he has illustrated the methods to remotely access unRaid GUI and VMs, I have been waiting for him to help with a solution to get around Carrier Grade NAT. With all of my own domain, DuckDNS domian/ subdomains, as well as some from afraid dns I still can not push through the CNAT. All following his guides over the past few years of course. I have tried OpenVPN docker, NGINX proxy Manager, Zerotier, and a few others. When I had a static IP it was no issue, but sadly I can no longer get a static IP address from my ISP. I know this is right up his alley and he would most likely be the one with the solution.
  2. I tend to think it may be an individual drive firmware version that needs to be updated. My problem is trying to get my windows 10 machine to format the XFS unraid disk, I am using the drive with almost no data on it (25 mb), I have to get the drives into NTFS to get run the firmware update tool from WD. I know it is sort of off topic, but does anyone know how to get windows to recognize a USB XFS so it can be formatted? It sees the drive as a generic drive, but says there is no data on it, and won't allow me to clear and format it. I even used CMD to try and use diskpart and it sees it but also says there is 0 data on it, and therefore it won't "clean" it to format it. I think I am on the right track once I get the drive firmware updated I can add it to the array and allow it to preclear format and rebuild. Unless someone else can think of a better way to do this. I am trying to do it one disk at a time the one without data first, so I do not loose the data from the array or parity. Disk 0 is the laptop SSD and the USB is the WD red pro 10tb from my unRaid server.
  3. Thank you and Squid. I apologize as I understood what you both were saying differently. I understand now that this is a new feature with the new release. My frustration is not being able to enable it, so is that a flaw in the drive itself or the way the drive is communicating with the unraid software? I would like to find a way to fix or repair it if possible. The unraid parity write speeds suck as it is, but to disable the disc cache just compounds the issue and frustration
  4. Both. Prior to updating those discs worked flawlessly with zero errors in FCP. I run regular scans in FCP over the past 6 months, same discs and hardware the entire time, and no issues. I update to 6.7 reboot and boom the cache write errors on only 3 of the 8 identical discs, 2 are parity disc. It is very odd that this write cache function has worked without issue all of this time with the only change being the update. As far as troubleshooting the hardware they are on an Adaptec 16 port pie controller that also has been in place the entire time. The discs that are showing this error are on the same breakouts from the controller as discs without these errors. I eveneed swapped the drives to the cables of the discs not showing the errors and the issues are following these three discs. Thank you for your time
  5. Please see the results in my post that you replied to. I already tried this under all of the conditions I stated. Is there an alternative means or a way to force it to enable? Thank you
  6. I posted my results from doing this in my previous comments on all three discs and the indication that it is not enableing. I even tried disabling, even though it is already disabled, and the enabling it, but it is not enabling. Can you provide a means to fix the hdparm commands not working properly? Thank you.
  7. Thank you for your input. Can you please refer me to the disc setting that I need to change for this to return to normal function?
  8. Can you please explain how to correct it? Again I have not edited anything added or removed anything, and had the exact same setup for 6 months. Something changed, but it wasn't across all discs. Theses discs are actually on seperate controllers from one another, and switching them does not help. I have tried HD parm with array active, the array stopped, rebooted several times, but still will not enable the write cache. The discs themselves return no errors in SMART or overall parity scans. They are all identical discs and added at the same time, one has less then 100 megs of data on it and stays spun down most of the time because it isn't needed in the array because storage hasn't reached the need for it. I run FCP on a schedule every few days and on reboots. Any assistance with correcting it is greatly appreciated.
  9. I too experienced this after 6.7, I have been using the EXACT same config and hardware for 6 months and went through all r versions of the 6.7 build without issue. Mine is showing on disc 1,3, and 4 of the array. Something in the update disabled it just on these discs not all of them, they are ALL identical WD red Pro 10tb drives. here are my results. I can not get it to enable. root@MediaServer:~# hdparm -W 1 /dev/sdf /dev/sdf: setting drive write-caching to 1 (on) write-caching = 0 (off) root@MediaServer:~# hdparm -W 1 /dev/sdg /dev/sdg: setting drive write-caching to 1 (on) write-caching = 0 (off) root@MediaServer:~# hdparm -W 1 /dev/sdd /dev/sdd: setting drive write-caching to 1 (on) write-caching = 0 (off) root@MediaServer:~#