realies

Will try to recover the data to another disk from the array. It says that data from the failed disk is emulated but I'm not seeing the shares, is that to be expected?

Jul 24 15:06:30 helion unassigned.devices: Adding disk '/dev/sdd1'... Jul 24 15:06:30 helion unassigned.devices: Mount drive command: /sbin/mount -t btrfs -o auto,async,noatime,nodiratime '/dev/sdd1' '/mnt/disks/WDC_WD1001FALS-XXX_WD-XXX' Jul 24 15:06:30 helion kernel: BTRFS info (device sdd1): disk space caching is enabled Jul 24 15:06:30 helion kernel: BTRFS info (device sdd1): has skinny extents Jul 24 15:06:33 helion kernel: BTRFS error (device sdd1): bad tree block start, want 1312205111296 have 1312204832768 Jul 24 15:06:33 helion kernel: BTRFS warning (device sdd1): failed to read log tree Jul 24 15:06:33 helion kernel: BTRFS error (device sdd1): open_ctree failed Jul 24 15:06:33 helion unassigned.devices: Mount of '/dev/sdd1' failed. Error message: mount: /mnt/disks/WDC_WD1001FALS-XXX_WD-XXX: can't read superblock on /dev/sdd1. Jul 24 15:06:33 helion unassigned.devices: Partition 'WDC_WD1001FALS-XXX_WD-XXX' could not be mounted...

Reconnecting the drive does not help. Attaching diagnostics. helion-diagnostics-20190724-1141.zip

Disk 2 went to "Device is disabled, contents emulated" and although it lists the btrfs filesystem, it says 'Unmountable: No file system'. Checking the filesystem status results in 'checksum verify failed on 1312205111296 found 7723BE85 wanted 5C832EA0' and 'bad tree block 1312205111296, bytenr mismatch, want=1312205111296, have=15350558693598887749'. It's a very old drive and it might be failing. The error occurred when trying to run a VM which failed, the system locked and libvirt is located on the same drive. What would be the best steps forward for recovering the drive or the data on it?

@sameranio, you need to satisfy all dependencies, maybe compile in a Linux VM that already has compiling tools installed? Otherwise, DevTools is an option.

@sameranio, wrong repository address, I've updated my post.

Hey @sameranio, could you please test if this branch has an expected output based on your device id? You might have to compile in a glibc/gcc environment to satisfy all headers. git clone -b feature-ax860i https://github.com/realies/corsairmi cd corsairmi make ./corsairmi

@jtmsrl, does it have a USB interface?

Credits to github/notaz for taking the time to reverse engineer the USB messages. Feel free to publish it on CA. Not sure what you mean by "make it compatible with the watercooling AIO's"...

I am working on a low-latency/max performance host/guest configuration for a Windows 10 VM on the Zen platform and some of the material regarding virtualisation that I have read so far indicates that using Huge Pages and disabling Transparent Huge Pages improves latency to memory. Is it possible to enable this with 6.7.0-rc5, if not, possible to add optional access to `/proc/sys/vm/nr_hugepages` for a future release?

Just seeing this now. I am still using the plugin without any issues, can someone report if there's anything wrong? RE: Adding ChatID/Token text fields, am not aware this is currently possible with the way NotificationAgents.xml is parsed, perhaps @bonienl can shed some light on this?

@ridge, there's an issue regarding this in the source repository with a discussion on a potential fix, but I have not found time yet to work on it... it will eventually get fixed.

@Ashe , did some bug fixes that can be seen here. Did retest in a clean environment and can't replicate the issue you were having. Feel free to test it yourself (note you also have to remove /boot/config/plugins/dynamix/notifications/agents/Telegram.sh if you do change NotificationAgents.xml). Pretty sure @limetech will merge the changes for the next release.

@limetech, following this up from: @Ashe, as you can see from here, the script checks if the `chatid` file does not exist and if it doesn't it asks the Telegram API for the latest bot updates, expecting to find a message from the user in there that would get the chat id to the `chatid` file. I have recently noticed that the timestamp on the files generated by this script updates everytime an update has come through, which is something I would not expect. Will do a revision in the following days.

Might get to it at some point when I get to that version, feel free to do a PR if you want it sooner.

@rix, what does it take?

You're welcome - https://docs.docker.com/storage/bind-mounts/.

@zandrsn, maybe you should read more about the high-level abstract of how Docker and Docker volumes work or at least try it the brute-force way before asking questions of this type.

With a few extra steps, it is possible without hosting a bot middleware: https://github.com/limetech/webgui/pull/425

Happy to do a Telegram bot integration if @limetech is happy with the idea. Microservice hosting such as now.sh could do for hosting the bot router, but might need a subdomain CNAME that would go in the webGui source.

My understanding is that different outputs are different rails coming out of the power supply. You can use Corsair Link to figure this out better. As mentioned above, type "corsairmi" in the terminal of Unraid to see all output options and more.

How do you get edac-util running on Unraid?

The "GPU Load" label is hardcoded to say that and it outputs the "output0 watts" value that the "corsairmi" command responds with (type "corsairmi" in the terminal for more). The name is hardcoded to say that only because this was my use-case at the time I wrote the plugin and configuration with other systems might differ. If there is demand, future versions might allow for custom labels. "PSU Load" is the "total watts" value from the same "corsairmi" command.

@steve1977, sorry for the lack of communication, I did not receive any notification for posts in this thread. I'll make sure I'm subscribed to it. It seems that your Corsair PSU shows up as 1b1c:1c0d. Interestingly, while I was able to source the device IDs for the rest of the Corsair smart PSU lineup by decompiling the Windows client, I did not have any confirmation about the device ID of the RM1000i until now (only an assumption). With this information, I have updated the plugin, which now supports RM1000i and displays meaningful errors on any potential failure (instead of "null").

@MrPotter, https://github.com/realies/soulseek-docker/issues/1