Cull2ArcaHeresy

Members
  • Content Count

    77
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Cull2ArcaHeresy

  • Rank
    Newbie
  1. Either that was a fast update (thanks) or i've never looked at the "TOTAL" line (oops hidden in plain sight).
  2. With the new pool options, i'm trying to have different shares for different things. Currently trying to have downloads be in a share that is on a pool (pool only), and done/seeding to be on main array (mover pool->array). Initially tried having p2p share (for incoming and everything else) mount as /data and also shares mounting as /data/downloading and /data/DONE but that caused conflicts where some stuff went to proper share and some went to p2p/[downloading or DONE]. Now do not have a base /data mount, but mounting everything needed...which seems to work ok but save to cannot
  3. Unless there is a longer log elsewhere, the one in the ui doesn't go back far enough. But those were the last 3 lines to be transferred to disk 7, who currently has 49.2 kb free. Source disk still has 36.8 gb on it, belonging to those 3 lines. So i'm assuming that was the issue. Mover was disabled, but guess something else was writing to that disk during transfers. All lines before were green (disk 7), and after those 3 lines (disk 12) were also green checks. One feedback (been meaning to give for a while). A select/deselect all checkbox would be great. Currently working on clearin
  4. do the colors of the icons indicate a problem or just ui bug?
  5. Spaceinvaderone's video was all usb3 (or at least top 3 were), but i know that was just extreme case stress testing with temperature readings. I just had the one issue that was easy to fix (will check boot flag first if happens again instead of reimaging), but if the issue is reoccurring then ill move my license to a new usb2 drive. Was hoping by now that the anecdotal-ness of it was historical and not current, but guess we're not there yet due to the amount of old hardware still in use and/or tech in the usb3 drives.
  6. after taking care of failed drive, clearing off 4 more of the 4tb drives that are to be in 8 drive archive_two pool, and dealing with a boot usb issue, i updated to 6.9.2 with no problems. After upgrade, i assigned the 8 drives to new pool archive_two, started array, and then used the gui to set to raid 6 and it did. Since it worked i forgot to copy the command from syslog, so just did balances from raid6 -> raid0 -> raid6. If someone else has issues maybe this could be of help. Apr 19 23:35:10 Raza ool www[29765]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_balance 'start' '/mnt
  7. Safe mode + GUI, local browser, same results. Did it that way so there is no chance it would be any kind of plugin/extension in browser or unraid plugin. When i boot into GUI or safemode+GUI, if i have a monitor plugged in and am using idrac console, after boot select menu and then part of the boot text, both are just a black screen. Not sure if that is an unraid thing or a hardware thing. Web access still works, but local does not. I did not try non-gui mode. Integrated graphics...was using the front vga on 720xd, not the rear one if that makes any difference. Dont think i ever ha
  8. command/cli output root@Raza:~# btrfs balance start -dconvert=raid6 -mconvert=raid1c3 /mnt/archive_one Done, had to relocate 3 out of 3 chunks log Apr 7 03:45:46 Raza kernel: BTRFS info (device sdak1): balance: start -dconvert=raid6 -mconvert=raid1c3 -sconvert=raid1c3 Apr 7 03:45:46 Raza kernel: BTRFS info (device sdak1): setting incompat feature flag for RAID1C34 (0x800) Apr 7 03:45:46 Raza kernel: BTRFS info (device sdak1): relocating block group 14223933440 flags metadata|raid1 Apr 7 03:45:47 Raza kernel: BTRFS info (device sdak1): found 3 extents, stage: move data extents Apr 7
  9. I upgraded from 6.8.3 to 6.9.1 and while at it finally upgrade my flash drive from a OLD 2gig that was from sometime before 2010. VMs and dockers seem to be working fine now and main array and cache normal. I created a new pool "archive_one" with 6 * 4tb sas drives. Now trying to rebalance it to raid6 instead of default raid 1. I started it last night and it ran for over 8 hours displaying this Data, RAID1: total=1.00GiB, used=0.00B System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=2.00GiB, used=128.00KiB GlobalReserve, single: total=3.25MiB, used=16.00KiB
  10. I upgraded from 6.8.3 to 6.9.1 and while at it finally upgrade my flash drive from a OLD 2gig that was from sometime before 2010. VMs and dockers seem to be working fine now and main array and cache normal. I created a new pool "archive_one" with 6 * 4tb sas drives. Now trying to rebalance it to raid6 instead of default raid 1. I started it last night and it ran for over 8 hours displaying this Data, RAID1: total=1.00GiB, used=0.00B System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=2.00GiB, used=128.00KiB GlobalReserve, single: total=3.25MiB, used=16.00KiB
  11. that seems to have been the issue (or at least fixed it), thanks
  12. I thought it was part of the core functionality. [25.03.2021 19:02:07] WebUI started. [25.03.2021 19:02:30] _cloudflare: Plugin will not work. rTorrent user can't access external program (python). [25.03.2021 19:02:30] _task: Plugin will not work. rTorrent user can't access external program (php). [25.03.2021 19:02:30] autotools: Plugin will not work. rTorrent user can't access external program (php). [25.03.2021 19:02:30] create: Plugin will not work. rTorrent user can't access external program (php). [25.03.2021 19:02:30] datadir: Plugin will not work. rTorrent user can't access external
  13. Any indication of an issue before starting the array? I was thinking of putting a clean trial copy of unraid on another usb to boot to check before upgrading. Could this be a valid way to check hardware/drive compatibility before upgrading?
  14. Does the coloring function work relative to disks in array instead of to 100%? Your description here made me think of conditional formatting in excel like so, round up applied to all % to avoid the middle yellow color for the purposes of this point.