Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Miss_Sissy

Members
  • Joined

  • Last visited

  1. If you want examples of failed consumer flash drives, the Unraid forums have plenty of them. Personal anecdotes about individual drives and warm feelings about case materials are no way to choose flash drives for applications where high reliability is important. I will stick with SLC NAND industrial drives like the ATP NANODURA, but you do you.
  2. I didn't dispute that in my reply.
  3. There is more to Unraid flash reliability than cell P/E cycles. As one goes from SLC to TLC to MLC to QLC, the error rate goes up, the data retention time goes down, and the operating temperature window shrinks -- in addition to P/E cycles going from ~100,000 in SLC to just ~100 – 1,000 in QLC. See: https://storedbits.com/slc-mlc-tlc-qlc-and-plc/#Detailed_Comparison_of_SLC_MLC_TLC_QLC_and_PLC_NAND_Flash_Cells
  4. @landS Samsung literature calls the BAR Plus drives "Temperature-proof" and then, apparently without recognizing the irony, specifies "Operating temperatures of 0℃ to 60℃ (32°F to 140°F)." * My ATP NANODURA 4GB B800pi flash drive is rated for an operating temperature range of -40°C to 85°C (-40°F to 185°F). * Samsung previously rated the BAR Plus line for an operating temperature range of -25°C to 85°C but later revised that down to the more limited 0℃ to 60℃ range we see now. That suggests that Samsung might have downgraded the drive's NAND flash or other internal components. Or they might have discovered that the drives were not reliable at the previously specified -25°C to 85°C temperature range.
  5. Using a USB 2.0 port, whether internal or external, reportedly helps reliability. But your industrial USB stick helps a lot more. Cheers!
  6. While I'm happy for your good fortune, we can't extrapolate much from it. If your model of drive had a 25% failure rate over three years, 56% of the people who bought a pair of them three years ago would have experienced no failures by now.
  7. Your rapid deployment of updates fixed that System tab problem for me. Thank you very much. Sorry for the delay in gettin back to you (I was installing a new ham radio antenna cable today).
  8. root@Unraid-NAS:~# ls -la /boot/config/plugins/disklocation/backup/ total 24 drwx------ 5 root root 4096 Feb 14 12:29 ./ drwx------ 4 root root 4096 Feb 14 13:25 ../ -rw------- 1 root root 4096 Oct 10 19:03 ._20240328-204958 drwx------ 2 root root 4096 Jan 23 13:50 20250123-135020/ drwx------ 2 root root 4096 Jan 23 14:28 20250123-142806/ drwx------ 2 root root 4096 Feb 14 12:29 20250214-122912/ root@Unraid-NAS:~# I did not muck about at the command line to move anything before or after installation or update of Disk Location. The NAS is connected to an Eaton 3000VA UPS and I don't yank the power cord or flip the power switch. It's generally rock-solid and runs for weeks or even months at a time. Thanks for your help.
  9. What I immediately found in the PHP log may give you what you need: text error warn system array login [14-Feb-2025 13:45:37 America/New_York] PHP Warning: scandir(/boot/config/plugins/disklocation/backup/._20240328-204958): Failed to open directory: Not a directory in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 13:45:37 America/New_York] PHP Warning: scandir(): (errno 20): Not a directory in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 13:45:37 America/New_York] PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:211 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(211): array_diff(false, Array) #1 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(385): disklocation_system('backup', 'list') #2 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 13:46:55 America/New_York] PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:211 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(211): array_diff(false, Array) #1 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(423): disklocation_system('backup', 'list') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778) : eval()'d code(5): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 13:53:34 America/New_York] PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:211 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(211): array_diff(false, Array) #1 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(423): disklocation_system('backup', 'list') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778) : eval()'d code(5): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 13:59:11 America/New_York] PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:211 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(211): array_diff(false, Array) #1 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(423): disklocation_system('backup', 'list') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778) : eval()'d code(5): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 13:59:19 America/New_York] PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:211 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(211): array_diff(false, Array) #1 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(423): disklocation_system('backup', 'list') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778) : eval()'d code(5): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 [14-Feb-2025 18:51:43 America/New_York] PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, false given in /usr/local/emhttp/plugins/disklocation/pages/page_system.php:211 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(211): array_diff(false, Array) #1 /usr/local/emhttp/plugins/disklocation/pages/page_system.php(423): disklocation_system('backup', 'list') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778) : eval()'d code(5): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 211 Does that explain what's happening? Let me know what else you need.
  10. @FlamongOle I updated Disk Location on two Unraid installs. One seems normal, but the other has an empty System tab. I've stopped and started the array. I've rebooted the NAS twice. I've tried with two different browsers. The result is always the same -- an empty System tab in Disk Location.
  11. I've got a massive box full of cables, most of which are CAT6A or better. Things are a tad more complex than the diagram. The switch that services the NAS has a 10GBase-SR Fiber Transceiver SFP+ module that goes to a matching module in another switch in my computer room. In that switch is a a 10GB Ethernet SFP+ module, to which the workstation shown in the diagram is connected. I may end up just making my own cables to length to go between the NAS and the switch.
  12. Thanks! That's what I thought, but I didn't want to purchase an LACP-capable switch without some reassurance.
  13. I've not been able to find a clear answer on this. If I have an Ethernet switch with four 2.5Gbps connections to my Unraid server, configured in LACP 802.3ad bonded mode, and a 10Gbps 'uplink'connection to a single workstation, what is the theoretical maximum bandwidth? Again, theoretical. (see footnote 1) Thanks in advance. Footnotes: (1) Please know in your heart that readers would swoon in admiration if you explained that the switch has to support LACP link aggregation, that networking protocols have overhead, that disks are not infinitely fast, that defective cables can slow things down, etc. And then don't explain any of those things. Thank you.
  14. Thanks. I probably won't even look at the display more than once every few weeks, and then just in passing because I happen to be in the laundry room where my primary 3D printer lives. The ICP A125 does work with the ICP A106 driver and that's the one I used when I set up LCD Manager. My issue wasn't the panel driver, which worked fine. It was displays that didn't fit on the tiny 16x2 format. Most of the preconfigured displays seem to be formatted for LCD panels at least 20 characters wide, so I was ending up with things like time displays with missing seconds and screen titles and host names that continually scrolled. This is not a criticism of @SimonF's LCD Manager plugin. It's not his fault that QNAP put a 16x2, 1200 baud display in my NAS; I would not expect him to tailor his displays for something that pitiful. With a list of available system status variables, I could printf my own displays. Let me pass in two strings of 16 characters formatted however I want. But, really, I'm fine with what I have put together now.
  15. Hi @wabamad, Thanks for the generous offer. That's a good looking LCD display you have. Unfortunately, my LCD panel is an ICP A125 with just two lines of 16 5x7 pixel characters, which is stock on the QNAP TS-853A. On top of that, it communicates at a liesurely 1200baud, leading to ugly things like time displays with colons that blink out of sync with second changes. In the end, I took a simpler route that lets me know if the system is booting, the array has been started, or the array has been stopped. I just manually write to the display using a couple of scripts called from the User Scripts plugin: LCD_Array_Start: #!/bin/bash # Define command to clear LCD LCD_Clear="\x4D\x0D" # Define commands to send 16 character lines. LCD_Line0="\x4D\x0C\x00\x10" LCD_Line1="\x4D\x0C\x01\x10" # Define 16 character strings Stringx="1234567890123456" StringA=" Unraid-QNAP " StringB=" Ready " # Set the baud rate to 1200 stty -F /dev/ttyS1 1200 printf $LCD_Clear > /dev/ttyS1 printf "$LCD_Line0%s", "$StringA" > /dev/ttyS1 printf "$LCD_Line1%s", "$StringB" > /dev/ttyS1 LCD_Array_Stop: #!/bin/bash # Define command to clear LCD LCD_Clear="\x4D\x0D" # Define commands to send 16 character lines. LCD_Line0="\x4D\x0C\x00\x10" LCD_Line1="\x4D\x0C\x01\x10" # Define 16 character strings Stringx="1234567890123456" StringA=" Unraid-QNAP " StringB=" Array Stopped " # Set the baud rate to 1200 stty -F /dev/ttyS1 1200 printf $LCD_Clear > /dev/ttyS1 printf "$LCD_Line0%s", "$StringA" > /dev/ttyS1 printf "$LCD_Line1%s", "$StringB" > /dev/ttyS1 That's really all of the info I need when I happen to walk by the NAS in the laundry room. Thanks again for the offer of help and for sharing the nice display you've got going. -- Miss_Sissy

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.