nate-wilkins
Dabbler
- Joined
- Nov 8, 2022
- Messages
- 13
Hi fellow NAS users. I'm having the best of luck with my NAS and well why not start the New Year off strong...with a kernel panic! Yay!
I don't know how to debug stuff at this level and even had to ask for help last time this happened but at the FreeNAS OS level - quite likely not the same issue but still thought it was funny.
So my setup is:
- TrueNAS@13.0-U3.1
- Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz
- RancherOS in a Virtual Machine
When booting up the VM (after changing some `ros` configuration at runtime) I get the following kernel panic:
This is frustrating and I'm not sure how to go about fixing it. I've tried restarting the VM numerous times but it panics every time.
Maybe I'm not meant to tinker with operating systems or virtual machines in general.
But to be optimistic I guess what I'm looking for is:
- Can I fix this without making a new VM?
- If I create a new VM, how do I get the data that I had on this VM?
- Is there a way to possibly fix this by modifying the VM disk data? (I know very little about VMs)
My guess is that
I don't know how to debug stuff at this level and even had to ask for help last time this happened but at the FreeNAS OS level - quite likely not the same issue but still thought it was funny.
So my setup is:
- TrueNAS@13.0-U3.1
- Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz
- RancherOS in a Virtual Machine
When booting up the VM (after changing some `ros` configuration at runtime) I get the following kernel panic:
[ ] init:info: [18/21] Starting set proxy env
[ ] init:info: [19/21] Starting init SELinux
SELinux: Could not load policy file /etc/selinux/ros/policy/policy.29: Read-only file system
[ ] init:info: [20/21] Starting setupSharedRoot
[ ] init:info: [21/21] Starting sysinit
[ ] init:info: Launching System Docker
[ 31.895559] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 31.895559]
[ 31.897206] CPU: 5 PID: 998 Comm: system-dockerd Not tainted 4.14.73-rancher#1
[ 31.898365] Hardware name: FreeBSD BHYVE/BHYVE, BIOS 13.0 11/10/2020
[ 31.899355] Call Trace:
[ 31.899752] dump_stack+0x5a/0x6f
[ 31.900391] panic+0xd8/0x238
[ 31.900989] ? css_set_move_task+0xc3/0x128
[ 31.901809] do_exit+0x50a/0x923
[ 31.902365] do_group_exit+0x9f/0x9f
[ 31.903050] get_signal+0x42d/0x45a
[ 31.903666] ? do_futex+0xdb/0x892
[ 31.904246] do_signal+0x23/0x569
[ 31.904763] ? ktime_get_ts64+0x37/0x76
[ 31.905316] ? _copy_to_user+0x22/0x28
[ 31.905864] ? poll_select_copy_remaining+0xf3/0x109
[ 31.906615] ? SyS_futex+0x12c/0x13c
[ 31.907163] prepare_exit_to_usermode+0x91/0xf5
[ 31.907910] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 31.908718] RIP: 0033:0x45d3f3
[ 31.909165] RSP: 002b:00007f19ca36dbf8 EFLAGS: 00000286 ORIG_RAX: 00000000000000ca
[ 31.910361] RAX: fffffffffffffe00 RBX: 0000000000000000 RCX: 000000000045d3f3
[ 31.911427] RDX: 00000000
This is frustrating and I'm not sure how to go about fixing it. I've tried restarting the VM numerous times but it panics every time.
Maybe I'm not meant to tinker with operating systems or virtual machines in general.
But to be optimistic I guess what I'm looking for is:
- Can I fix this without making a new VM?
- If I create a new VM, how do I get the data that I had on this VM?
- Is there a way to possibly fix this by modifying the VM disk data? (I know very little about VMs)
My guess is that
Could not load policy file /etc/selinux/ros/policy/policy.29: Read-only file system
is the culprit since I was modifying ros configuration and might have messed up the permissions but I'm just not sure because I can't look at the VM disk data or change it to the correct configuration.