Jump to content

vizi0n

Members
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

2 Neutral

About vizi0n

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I am using the drives as JBOD. You need to tell the controller that the disks are JBOD using the controller's software at boot time, or through arcconf. It works very well still. Currently upsizing a drive as we speak I keep the drives always spinning, less stop and start means less possible failure. The chassis is well cooled so heat is no issue
  2. How can I change that specific disk’s treshold? I haven’t found the option in the menus
  3. Hi! Is there any way to disable the low disk space notifications/warning for a specific disk? One of them is running using Unassigned Devices and is used as a Time Machine backup system which deletes data as needed to free up space. I always receive warnings about this disk because it is between 90 and 99% Thank you
  4. The settings were done in the GUI, and have stayed over the updates. It's just that when the docker is restarted they are not applied until I login to the GUI. I can I assign channels to my torrents in the config? This seems like a strange way to set this
  5. I think my post slipped and was not read, but again this morning I woke up to a non-functionnal internet connectivity because my torrents were completely filling up my upload. As soon as I opened rtorrent evereything went back to normal as the upload slowly slowed down to the channel's limit. Is there some kind of workaround for this?
  6. Hi, Is it possible that the channels (manual speed limits) are applied only after a GUI login? My auto updates are set to daily at 4am and every morning that there was an update, the current upload speed on my seeds is not respecting the channel's limit and is actually filling up my entire internet connection upload. After logging into the GUI, the upload speed slowly drops to the maximum that is set for the channel.
  7. I guess I'll just live with it for now then. Thanks!
  8. I'm getting lots of PHP Warning in my syslog Do you know what could be causing this? Jul 22 13:17:07 Tower rc.diskinfo[31979]: SIGHUP received, forcing refresh of disks info. Jul 22 13:17:07 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 13:17:07 Tower rc.diskinfo[31979]: SIGHUP ignored - already refreshing disk info. Jul 22 14:17:12 Tower kernel: mdcmd (906): spindown 1 Jul 22 14:17:14 Tower kernel: sd 1:1:0:0: [sdb] Spinning up disk... Jul 22 14:17:18 Tower kernel: . Jul 22 14:17:18 Tower kernel: ready Jul 22 14:17:18 Tower kernel: sd 1:1:0:0: [sdb] 975155200 512-byte logical blocks: (499 GB/465 GiB) Jul 22 14:17:18 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 14:17:18 Tower rc.diskinfo[31979]: SIGHUP received, forcing refresh of disks info. Jul 22 14:17:18 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 14:17:18 Tower rc.diskinfo[31979]: SIGHUP ignored - already refreshing disk info. Jul 22 15:16:24 Tower kernel: mdcmd (907): spindown 1 Jul 22 15:16:26 Tower kernel: sd 1:1:0:0: [sdb] Spinning up disk... Jul 22 15:16:30 Tower kernel: . Jul 22 15:16:30 Tower kernel: ready Jul 22 15:16:30 Tower kernel: sd 1:1:0:0: [sdb] 975155200 512-byte logical blocks: (499 GB/465 GiB) Jul 22 15:16:30 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 15:16:30 Tower rc.diskinfo[31979]: SIGHUP received, forcing refresh of disks info. Jul 22 15:16:30 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 15:16:30 Tower rc.diskinfo[31979]: SIGHUP ignored - already refreshing disk info. Jul 22 15:16:32 Tower kernel: mdcmd (908): spindown 5 Jul 22 15:16:34 Tower kernel: sd 1:1:4:0: [sdf] Spinning up disk... Jul 22 15:16:39 Tower kernel: . Jul 22 15:16:39 Tower kernel: ready Jul 22 15:16:39 Tower kernel: sd 1:1:4:0: [sdf] 3900682240 512-byte logical blocks: (2.00 TB/1.82 TiB) Jul 22 15:16:40 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 15:16:40 Tower rc.diskinfo[31979]: SIGHUP received, forcing refresh of disks info. Jul 22 15:16:40 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 15:16:40 Tower rc.diskinfo[31979]: SIGHUP ignored - already refreshing disk info. Jul 22 15:17:27 Tower kernel: mdcmd (909): spindown 6 Jul 22 15:17:29 Tower kernel: sd 1:1:5:0: [sdg] Spinning up disk... Jul 22 15:17:34 Tower kernel: . Jul 22 15:17:34 Tower kernel: ready Jul 22 15:17:34 Tower kernel: sd 1:1:5:0: [sdg] 3900682240 512-byte logical blocks: (2.00 TB/1.82 TiB) Jul 22 15:17:35 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 15:17:35 Tower rc.diskinfo[31979]: SIGHUP received, forcing refresh of disks info. Jul 22 15:17:35 Tower rc.diskinfo[31979]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 684 Jul 22 15:17:35 Tower rc.diskinfo[31979]: SIGHUP received, forcing refresh of disks info.
  9. Oooh i had missed the first sentence. "method attempts to step fill each disk so at the end of each step there is an equal free space left on each disk."
  10. oh ok... I've always thought high water was 50% of all drives, then 75% and so on. So its 50% of the bigger , than until it is up to filling half the size of the 500gb it will move to this one?
  11. Hi everyone, I find this very strange that unRAID skipped one drive and even though all are at 50% and its going through the 75% full cycle, it never writes to one of my drives. This drive is not explicitely excluded from any share. Did this ever happen to anyone?
  12. All is well, still. I guess I can say problem solved! Thanks to you two
  13. Well, no lockups since I have disabled mover logging and automatic backups by CA Backup / Restore. I guess one of these 2 was probably the culprit