GeneM

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

GeneM's Achievements

Noob

Noob (1/14)

2

Reputation

  1. +1 for Linkwarden, pls. https://github.com/linkwarden/linkwarden
  2. I also just install (/unifi:7.5.187-unraid) per directions. All was fine, but I needed to adjust Port: 1900 as it was being used to my Plex docker. It took a `sudo netstat -pna | grep 900` for me to realize 1901 was already snagged by mosquitto, so 1902 it was! Opened the WebUI, restored the backup, and after a docker-page-refresh, it already showed as stopped, so, restarted it, opened the WebUI and followed the prompts to re-add it to my ui.com site. Not sure how I went to the ui.com site - maybe it was a typo/mis-click on my end - but upon re-visiting my local url site, I logged in as before and everything was there (no adoption needed). Great Job, thank you.
  3. After upgrading to 6.9.0, and remaining with 6.9.1, I noticed that unRAID is trying to spin it down every hour. unassigned devices don't seem to have the option to over-ride the global spin-down delay. Just an annoyance given the hourly entry in the syslog. ar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] 125313283 512-byte logical blocks: (64.2 GB/59.8 GiB) Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00 Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 15 13:33:51 ED800 kernel: sdb: sdb1 Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk Mar 15 13:34:16 ED800 emhttpd: Samsung_Flash_Drive_FIT_0315220050002503-0:0 (sdb) 512 125313283 Mar 15 13:34:16 ED800 emhttpd: read SMART /dev/sdb Mar 15 13:34:22 ED800 unassigned.devices: Adding disk '/dev/sdb1'... Mar 15 13:34:22 ED800 unassigned.devices: Mount drive command: /sbin/mount -t exfat -o rw,auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdb1' '/mnt/disks/unRAID_TD' Mar 15 13:34:22 ED800 unassigned.devices: Successfully mounted '/dev/sdb1' on '/mnt/disks/unRAID_TD'. Mar 15 14:34:25 ED800 emhttpd: spinning down /dev/sdb Mar 15 15:34:26 ED800 emhttpd: spinning down /dev/sdb Mar 15 16:34:27 ED800 emhttpd: spinning down /dev/sdb . . . Apr 3 11:20:26 ED800 emhttpd: spinning down /dev/sdb
  4. I keep an unassigned device USB thumbdrive mounted as a nightly backup destination. After upgrading to 6.9.0, and remaining with 6.9.1, I noticed that unRAID is trying to spin it down every hour. Any cause for concern, or any adjustment I could make to have that ignored? Tnx Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] 125313283 512-byte logical blocks: (64.2 GB/59.8 GiB) Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00 Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 15 13:33:51 ED800 kernel: sdb: sdb1 Mar 15 13:33:51 ED800 kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk Mar 15 13:34:16 ED800 emhttpd: Samsung_Flash_Drive_FIT_0315220050002503-0:0 (sdb) 512 125313283 Mar 15 13:34:16 ED800 emhttpd: read SMART /dev/sdb Mar 15 13:34:22 ED800 unassigned.devices: Adding disk '/dev/sdb1'... Mar 15 13:34:22 ED800 unassigned.devices: Mount drive command: /sbin/mount -t exfat -o rw,auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdb1' '/mnt/disks/unRAID_TD' Mar 15 13:34:22 ED800 unassigned.devices: Successfully mounted '/dev/sdb1' on '/mnt/disks/unRAID_TD'. Mar 15 14:34:25 ED800 emhttpd: spinning down /dev/sdb Mar 15 15:34:26 ED800 emhttpd: spinning down /dev/sdb Mar 15 16:34:27 ED800 emhttpd: spinning down /dev/sdb Mar 15 17:34:28 ED800 emhttpd: spinning down /dev/sdb Mar 15 18:34:29 ED800 emhttpd: spinning down /dev/sdb Mar 15 19:34:30 ED800 emhttpd: spinning down /dev/sdb Mar 15 20:34:31 ED800 emhttpd: spinning down /dev/sdb Mar 15 21:34:32 ED800 emhttpd: spinning down /dev/sdb . . . Apr 3 08:20:23 ED800 emhttpd: spinning down /dev/sdb Apr 3 09:20:24 ED800 emhttpd: spinning down /dev/sdb Apr 3 10:20:25 ED800 emhttpd: spinning down /dev/sdb Apr 3 11:20:26 ED800 emhttpd: spinning down /dev/sdb
  5. 😆Oh, man. Sorry for spinning this up. If I missed a release-note or documentation(?) change, please advise. But, thank you.
  6. Also trying to rearrange the folders and dockers to manage start-up. unRAID: 6.9.0 2021-02-27 Docker Folder Plugin: 2021.03.03 Not seeing anything in the Chrome browser console. Same symptom w/Firefox Thank you...
  7. For whomever winds up here with this symptom: While I also configured -i br0, I can reproduce this at-will by starting up an old Win 8.1 tablet. Every time. Stop/Start the array to resolve it. Also 6.8.3.
  8. Folks: I appreciate the guidance on this. I think I'm mission accomplished at this point. Array: 95.1 MB used of 61.5 GB (0.2 %) DEVICE STATUS TEMP SMART UTILIZATION Disk 1 active * healthy 0% Cache 113 GB used of 1 TB (11.3 %) DEVICE STATUS TEMP SMART UTILIZATION Cache active 23 C healthy 11% Funny: My boot thumb drive is a SanDisk 16GB Ultra Fit USB 3.1 Flash Drive - SDCZ430-016G-G46 which unRAID shows as a simple identification: Flash Ultra_Fit - 15.4 GB (sda) For the Array thumb drive, I went with a SanDisk 64GB Ultra Fit USB 3.1 Flash Drive - SDCZ430-064G-G46 unRAID is using an identification string of: Ultra_Fit_04014b853bd7df80063efbb2fb89413c10b9246f0603543e8c9763be945ae394f941000000000000000000002c181ad0ff836e18835581078ea75baf (SanDisk_Ultra_64G) Just found that strange. Thanks again.
  9. Oh, never considered that. Thank you....
  10. Hello, all. Question: Would I have a supportable configuration if I had a single SSD as an array? I've done a lot of reading here on using SSDs in arrays, but don’t seem to be finding anything for just a single drive array. I have a minimal requirement and selected unRAID on a small form factor (SFF) fanless i5, to replace my Media server PC and Home Assistant Pi. The backstory: I currently have a 250G M.2 SSD (Cache) for a 1T laptop HDD. In this SFF configuration, the M.2 is tucked in under the HDD. Even after attaching a heatsinked, the M.2 runs at 60C, and that warms the HDD from 41C to 65C when the room goes over 72F. It’s getting kind of close. I was hoping to rip them both out in exchange for a single 1T SSD. No more cache, No Parity (like now), No redundancy (like now). In case of failure, I’d just re-install, leveraging the appdata backups I mirror off to another network drive after the nightly backup. I’m fully installed and running, and am still under 100G of storage usage on my unRAID server. Any media server content I want to keep, is copied off to a separate NAS, so I'm not seeing my storage requirements changing. Maybe someday I can more the NAS into the unRAID, but for now, that’s not a priority. So, amy I missing anything in regards to the 1T SSD? I've read no TRIM on an array, so I’d probably want to periodically shut the array and do that manualy? Any other gotchas? Tnx!