srfnmnk

yeah I already restored and it worked fine. This is more just about my curiosity at this point. I learned what I didn't know, hence the questions.

Yeah when the server crashed some of the files got corrupted / deleted. I didn't know super.dat had it, I think disk.cfg used to have it. I looked and looked for it. Is there any way to open super.dat?

We had a major power spike X2 during a storm the other day and both times it was powerful enough to blow out a UPS resulting in server restart. The second failure I assume happened during boot...either way, the configs got borked and I had to restore /boot/config to get things working again. One of the major issues was that my disk configs were all missing and none of the 24 disks were assigned anywhere. Throughout this process I noticed that the disk.cfg was basically empty even in historical backups. By empty I mean, all the values seem empty, attached for reference. Even now, when it's all restored and working fine, the disk.cfg is still relatively empty...where is the drive to disk mapping stored? I'm on 6.12.4. Additionally, where are the docker config xmls stored? Thanks disk.cfg

Easy question -- I am wanting to clean up my main page as I have > 10 years of dead drives in the historical devices section. If a drive is dead (and as such is showing up as historical) and the drive will never be added back to the array (since it's already been recycled) is there any issue with deleting these historical devices to clean up? Thanks

Understood -- I'm just saying that this is a bug and the community would love to see this resolved.

I did read through this forum post -- it looks like leaving the browser open can result in this issue. I did leave a browser with it open. Please help us escalate this issue, leaving a browser on a web page overnight should not result in a complete crash of the nginx server. restarting nginx seems to have resolved the issue. Thank you.

I am having the same issue. Please fix this.

Ok so today -- I logged in and received this little present. The ui was blank-ish. Looking at the nginx logs I see the following. I attached the full log. Why is nchan_max_reserved_memory running out? How to fix it? gth=1 HTTP/1.1", host: "localhost" 2023/11/09 09:26:26 [error] 19497#19497: MEMSTORE:00: can't create shared message for channel /disks 2023/11/09 09:26:27 [crit] 19497#19497: ngx_slab_alloc() failed: no memory 2023/11/09 09:26:27 [error] 19497#19497: shpool alloc failed 2023/11/09 09:26:27 [error] 19497#19497: nchan: Out of shared memory while allocating message of size 21383. Increase nchan_max_reserved_memory. 2023/11/09 09:26:27 [error] 19497#19497: *550567 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_len gth=1 HTTP/1.1", host: "localhost" 2023/11/09 09:26:27 [error] 19497#19497: MEMSTORE:00: can't create shared message for channel /disks 2023/11/09 09:26:28 [crit] 19497#19497: ngx_slab_alloc() failed: no memory 2023/11/09 09:26:28 [error] 19497#19497: shpool alloc failed 2023/11/09 09:26:28 [error] 19497#19497: nchan: Out of shared memory while allocating message of size 22385. Increase nchan_max_reserved_memory. 2023/11/09 09:26:28 [error] 19497#19497: *550573 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/update2?buffer_l ength=1 HTTP/1.1", host: "localhost" error.log

ok will try this next time if it happens again. thanks

as far as I know, there was only one browser window open from one PC.

Hi, I woke up this morning to my web ui being down. I restarted nginx and still I had the issue. I've attached the diagnostics for review. I also looked in the nginx logs to see what I could find and found the following. My server had 32G+ of mem available as per free -h command. I rebooted the server and the UI is working again, but I'd like to understand what happened and how to avoid this in the future. Thank you. pumbaa-diagnostics-20231108-1007.zip

Right, I had it as /mnt/user/appdata and it was doing this same thing so I went ahead and checked each box explicitly hoping it would change something, it did not.

Hi @KluthR -- I'm still having some issues with the new appdata backup. Sorry if I'm missing something but below I've added a screenshot of the output of my old backups using CA_Backup plugin and another with the output of the new appdata backup. Am I doing something wrong? Notice how many /appdata/config folders don't seem to be getting backed up. I've also attached the config for you. Thank you. config.json

Thank you so much for all your help @ghost82. I went ahead and upgraded the kernel now that I have internet and virtio is still not working for vdisk or network. I also reinstalled qemu agent but still nada. Any ideas why virtio still won't work? Should it? sudo apt full-upgrade sudo apt install -y --reinstall qemu-guest-agent

It appears I'm back up and running but I have no idea why. I migrated my config dir to the new usb drive (also on 6.12.4) and started back, replaced my key, and now no matter how many times I reboot, the network-rules.cfg file remains in /boot/config. On the old drive, I could place the network-rules.cfg file in /boot/config and reboot and everything would work perfectly...except, after reboot the file was gone. When the file is present, the eth devices get assigned properly, when it's missing, things go wonky. Ghost in the machine I guess... I ran a scan on the old usb drive and it came back with no issues -- so I have absolutely no idea what could have happened...but looks like we're back online now. Thank you for your help.

I'm trying to do a benchmark on an ssd but all the ssds are grayed out. Any idea why?

HOLY SMOKES!! ChatGPT for the WIN. So now I have internet and everything is working. So what is the root cause? Why did upgrade to unraid 6.12.4 break my VM? Should I leave the hard disk on sata mode or switch it back to virtio? How can I get virtio working again on the vm? The other guy said he updated the kernel, is that what I should do here to get virtio back? Question: in a ubuntu command line interface how do I configure the network In Ubuntu, network configuration can be managed using different tools depending on the version of Ubuntu you are using, the type of network interface, and whether you want to set up a static or dynamic IP address. Here are some of the common methods used for network configuration on Ubuntu: ### 1. `ifconfig` and `/etc/network/interfaces` (deprecated) Older versions of Ubuntu used `ifconfig` and the `/etc/network/interfaces` file for network configuration. This method is deprecated and replaced by `ip` and `netplan` in newer versions of Ubuntu. ### 2. `netplan` (Ubuntu 17.10 and later) Ubuntu now uses `netplan` as the standard for network configuration. Here’s how to configure the network using `netplan`: 1. Locate your netplan configuration files. They are typically in the `/etc/netplan/` directory. You will find a `.yaml` file inside this directory. ```sh ls /etc/netplan/ ``` 2. Edit the `.yaml` configuration file with a text editor like `nano` or `vim`. ```sh sudo nano /etc/netplan/00-netcfg.yaml ``` 3. Here’s an example of a static IP configuration with `netplan`: ```yaml network: version: 2 renderer: networkd ethernets: enp3s0: dhcp4: no addresses: - 192.168.1.100/24 gateway4: 192.168.1.1 nameservers: search: [mydomain, otherdomain] addresses: [192.168.1.1, 8.8.8.8] ``` Make sure to replace `enp3s0` with the actual interface name, and configure the IP addresses, gateway, and DNS as per your network requirements. 4. Apply the configuration with the following command: ```sh sudo netplan apply ``` Or, you can use `sudo netplan try` to automatically revert changes if you lose connectivity. ### 3. `nmcli` (NetworkManager command-line tool) For desktops or servers where NetworkManager is used, `nmcli` is a command-line tool to manage the network: - To see all connections: ```sh nmcli con show ``` - To edit or add a connection (for example, for setting a static IP): ```sh nmcli con edit type ethernet con-name "Wired connection 1" ``` You can set various properties with `nmcli` in interactive mode or directly from the command line. - To apply the changes to a connection: ```sh nmcli con up id "Wired connection 1" ``` ### 4. `/etc/dhcp/dhclient.conf` (for DHCP Client Configuration) If you need to make changes to how your DHCP client obtains an IP address, you can edit the dhclient configuration. ```sh sudo nano /etc/dhcp/dhclient.conf ``` Here, you can set options like the default lease time, renew time, etc. ### Additional Tips - Always back up configuration files before editing them. - Changes made with `nmcli` typically take effect immediately, but in some cases, you might need to restart the NetworkManager service: ```sh sudo systemctl restart NetworkManager ``` - Use `ip a` or `ifconfig` (if still available) to display your current network interface settings. - Be careful when configuring network settings remotely, as incorrect settings may disconnect you from the server. Remember that networking configuration can significantly impact your system's connectivity, so it should be done carefully, and preferably not on a remote system unless you have alternative access methods like a console or out-of-band management.

I was able to get it to start with 82540em (with a 0) <model type='e1000-82540em'/> but the same issue is present. No eth0 only lo: and no interenet

Apologies @ghost82 -- I gave you a diagnostics from a bit earlier. I only have the e1000 as an option from the drop down. I can start it with the following but no network: <interface type='bridge'> <mac address='52:54:00:9e:3b:8c'/> <source bridge='br0'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/> </interface> but with the following it fails to start showing the error in the screenshot below. <interface type='bridge'> <mac address='52:54:00:9e:3b:8c'/> <source bridge='br0'/> <model type='e1000-8254em'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/> </interface> I started it with it set to e1000 and posted the lspci you requested -- the screenshot is below. Thanks again for your review. pumbaa-diagnostics-20231103-1151.zip

In the new version of Appdata Backup, there is no option to "create separate archives". That's why i assumed the feature was disabled.

So if I'm reading some of the posts here correctly, this feature is now disabled, correct? Create Separate Archives? I really liked this feature because if I ever needed to look back at the backup and grab something specific (docker config / etc) I could unzip untar that single folder really quickly, whereas now I have to unzip/untar the entire backup. If this is accurate, would you consider adding it back @KluthR? Thanks for all your hard work on keeping this up-to-date. Saved my a** several times.

also, what do I do with this file on the fresh install? Do I just need to ensure it's in the new drive's /boot/config folder?

pumbaa-diagnostics-20231101-1636.zip

seems like no matter which option I use, this is all i get back. It doesn't have any visible eth interfaces. And sorry for the spam.

these are the options I have