Search results

  1. M

    Audit messages being spammed to root login

    how to turn off or send to another output?
  2. M

    Boot goes directly into initramfs on zfs

    Hi Proxmox Support, recently I upgraded my installation and my grub boot parameters still was not able to boot directly to login, it drops to initramfs where I have to 'zpool import -a' then 'exit' to get to login. I'm unsure how to properly configure the linux command in the grub.cfg file to...
  3. M

    Bad RIP Value, RIP: 0033:0x7f767e8f732b

    are the results from the first zgrep the second zgrep displayed nothing.
  4. M

    Bad RIP Value, RIP: 0033:0x7f767e8f732b

    Not to date myself but they're 6gb/s SAS constellation drives, I don't know how long the error has been occurring but did show up after a apt upgrade command. I recently had an I/O bug that wasn't entering/displaying characters properly inside a VM. I'll open a new thread for that issue also.
  5. M

    Bad RIP Value, RIP: 0033:0x7f767e8f732b

    Oh, ran dmesg and got this stack trace after a google search indicating that's what to do?
  6. M

    Bad RIP Value, RIP: 0033:0x7f767e8f732b

    Under root login it is printing stack traces to the shell. It's been happening for a while but I haven't been able to address this issue until now. How do I get the stack trace?
  7. M

    Bad RIP Value, RIP: 0033:0x7f767e8f732b

    Latest updates as of 04-05-2021 and intel-microcode installed.