shaunmccloud

Last night I went to start a VM I accidentally stopped. I got a "read_folders error. looks like migration is running wild. Please report this on the forums." Rebooted and it is back again today. diagnostics are attached as is a screen shot of the error. bb-8-diagnostics-20210714-1245.zip

Will do. Just waiting on the drives to come back from being NAID certified wiped. I mean, I'd really prefer the 1.92TB SAS SSDs, but they are worth a lot of money.....

I know what I won't to do won't be easy at best. Right now I have a cache array of 4 600GB 15000 RPM SAS drives. I would like to migrate to an array of 8 480GB SSDs (power usage, speed & sound). Can I just set every share to be cache yes, move my docker & VM images to the array, run the mover to get everything off the cache array, rebuild my config to not have a cache array then create the new one?

Just reinstalled everything and its working fine still. Could it have been the Nvidia plugin not set to update drivers on boot?

I reduced my plugin list to the essentials for me and RC2 now boots. Not sure which one it was, but given that I'm booting I don't care to much.

Here are the plugins I have installed right now. CA Auto Turbo Write Mode CA Backup / Restore Appdata CA Config Editor CA Dynamix Unlimited Width Community Applications disklocation Dynamix Active Streams Dynamic Cache Directories Dynamix Date Time Dynamix File Integrity Dynamix Local Master Dynamix Schedules Dynamix Stop Shell Dynamix System Buttons Dynamix System Information Dynamix System Statistics Enhanced Log Viewer File Activity Fix Common Problems IPMI Support Libvirt Hotplug USB Nerd Tools Nvidia Driver Open Files Preclear Disks rclone Spin Down SAS Drives ssh Plugin Statistics Tips and Tweaks Unassigned Devices Unassigned Devices Plus User Scripts

I'm currently rolling back to RC1 so I can get a list of plugins. I know I have the nVidia driver plugin, could that be it?

Yes, It does boot fine in safe mode. Do I just make a list of my plugins and install them one at a time until I find the one that causes the issue?

Let me try again, but based on memory it still crashes when the array starts (I know for sure it boots fine in normal mode if I do not auto start the array).

Ok, will do. Might not be until January 2nd due to having to move other plans up now

Will a recording of my server's IPMI KVM console help figure out the cause of my RC2 kernel panics on boot?

Anyone have an idea how to get logs from my kernel panics after boot? Nothing written to the flash drive

It is possible I was getting it after it booted, but over IPMI remote console it changed so fast I couldn't to much. 6.9 RC1 is back up and running at least.

Is anyone else getting a kernel panic on boot of RC2? I'm currently rolling back to RC1 due to this.

Got my install sorted out, but if I try to login with my Apple ID I get "Could not communicate with the server." and I did follow the steps to verify it should work.

Here you go.

Got into the macOS recovery utility, but I cannot boot into Big Sur after running it. Keeps rebooting into the recovery utility. I did set FIRSTINSTALL to no.

Follow this File -> Add Connection Check "Connect to remote host over SSH Leave Username as root Set the hostname to the IP of your unRAID box Check "Autoconnect" If you get a prompt for the SSH key, type yes and then click OK Enter your root password and click OK Be confused as the Macinabox VM doesn't yet exist

Can't wait for the video on how to use the new version. Right now I cannot get it added and fumbling through isn't the easiest.

And switching from onboard to my H310 in IT mode made it worse. I’m wondering if it’s the backplane or the SAS cables.

And it just happened on another drive Updated diagnostics attached. bb-8-diagnostics-20201204-0959.zip

If they are set to never spin down, it doesn't happen. Plus for some reason the drives never spin down even when configured to. Although that is all my drives and I just haven't had time to look at it.

Here are the diagnostics with the array running. But the issue has not occurred since the last reboot as I'm running my monthly parity check. bb-8-diagnostics-20201202-1234.zip

I have two HGST Deskstar NAS 4TB drives that are acting weird. When they spin down, the appear in the unassigned drives list and no longer work correctly for data. Rebooting ends up causing a parity check the next boot because the reboot stops when attempting to unmount the drives. The drives are hooked up to a Broadcom SAS2208 SAS RAID controller is cross-flashed to a SAS2308-IT mode SAS HBA. HBA is dual linked to a Supermicro backplane in an SC836TQ case and the drives are plugged into it. Prior to the Supermicro case I had all my drives hooked up using breakout cables to both the onboard SAS HBA and a Dell H310 cross-flashed to IT mode. In this configuration these drives spun down as expected. I'm guessing you will need diagnostic logs after the issue has happened. Is that correct?