"db_root" continuous lines
Ste
125 Posts
October 22, 2021, 10:29 amQuote from Ste on October 22, 2021, 10:29 amHi, I have the console and dmesg output of one node full of this lines (one every few seconds), is it something I have to worry about ? Thanks.
db_root: cannot be changed: target drivers registered
Hi, I have the console and dmesg output of one node full of this lines (one every few seconds), is it something I have to worry about ? Thanks.
db_root: cannot be changed: target drivers registered
admin
2,930 Posts
October 23, 2021, 9:34 amQuote from admin on October 23, 2021, 9:34 amcan you list output of
dpkg -s petasan | grep Version
uname -r
dpkg -s targetcli-fb
can you list output of
dpkg -s petasan | grep Version
uname -r
dpkg -s targetcli-fb
Ste
125 Posts
October 24, 2021, 9:51 amQuote from Ste on October 24, 2021, 9:51 amSure, here it is:
root@petasan04:~# dpkg -s petasan | grep Version
Version: 2.8.1
root@petasan04:~#
root@petasan04:~# uname -r
4.15.0-161-generic
root@petasan04:~#
root@petasan04:~# dpkg -s targetcli-fb
Package: targetcli-fb
Status: install ok installed
Priority: optional
Section: base
Maintainer: PetaSAN
Architecture: amd64
Version: 2.1.49-1petasan
Depends: python3-rtslib-fb (= 2.1.69-1petasan), python3-configshell-fb, python3-dbus, python3-pyparsing, python3-urwid
Description: LIO management tool
root@petasan04:~#
Sure, here it is:
root@petasan04:~# dpkg -s petasan | grep Version
Version: 2.8.1
root@petasan04:~#
root@petasan04:~# uname -r
4.15.0-161-generic
root@petasan04:~#
root@petasan04:~# dpkg -s targetcli-fb
Package: targetcli-fb
Status: install ok installed
Priority: optional
Section: base
Maintainer: PetaSAN
Architecture: amd64
Version: 2.1.49-1petasan
Depends: python3-rtslib-fb (= 2.1.69-1petasan), python3-configshell-fb, python3-dbus, python3-pyparsing, python3-urwid
Description: LIO management tool
root@petasan04:~#
admin
2,930 Posts
October 24, 2021, 10:42 amQuote from admin on October 24, 2021, 10:42 amYou have an incorrect kernel 4.15. Any idea how you got this and how you are booting from it ? Your best action is to configure the grub menu to boot from the PetaSAN supplied kernel.
You have an incorrect kernel 4.15. Any idea how you got this and how you are booting from it ? Your best action is to configure the grub menu to boot from the PetaSAN supplied kernel.
Ste
125 Posts
October 25, 2021, 9:11 amQuote from Ste on October 25, 2021, 9:11 amYes, you're right, the grub default had been changed, I'm afraid during my attempts to fix the grub issue described in this thread.
Now I restored the petasan kernel as grub default boot entry and the db_root error has disappeared, but the grub bootloader hasn't been fixed during the update to Petasan 2.8.1. Now any further attempt says that everything is up to date. Is there a way to manually apply the "bug fix for grub bootloader" also to this node ?
Thanks, Dk.
Yes, you're right, the grub default had been changed, I'm afraid during my attempts to fix the grub issue described in this thread.
Now I restored the petasan kernel as grub default boot entry and the db_root error has disappeared, but the grub bootloader hasn't been fixed during the update to Petasan 2.8.1. Now any further attempt says that everything is up to date. Is there a way to manually apply the "bug fix for grub bootloader" also to this node ?
Thanks, Dk.
"db_root" continuous lines
Ste
125 Posts
Quote from Ste on October 22, 2021, 10:29 amHi, I have the console and dmesg output of one node full of this lines (one every few seconds), is it something I have to worry about ? Thanks.
db_root: cannot be changed: target drivers registered
Hi, I have the console and dmesg output of one node full of this lines (one every few seconds), is it something I have to worry about ? Thanks.
db_root: cannot be changed: target drivers registered
admin
2,930 Posts
Quote from admin on October 23, 2021, 9:34 amcan you list output of
dpkg -s petasan | grep Version
uname -r
dpkg -s targetcli-fb
can you list output of
dpkg -s petasan | grep Version
uname -r
dpkg -s targetcli-fb
Ste
125 Posts
Quote from Ste on October 24, 2021, 9:51 amSure, here it is:
root@petasan04:~# dpkg -s petasan | grep Version
Version: 2.8.1
root@petasan04:~#
root@petasan04:~# uname -r
4.15.0-161-generic
root@petasan04:~#
root@petasan04:~# dpkg -s targetcli-fb
Package: targetcli-fb
Status: install ok installed
Priority: optional
Section: base
Maintainer: PetaSAN
Architecture: amd64
Version: 2.1.49-1petasan
Depends: python3-rtslib-fb (= 2.1.69-1petasan), python3-configshell-fb, python3-dbus, python3-pyparsing, python3-urwid
Description: LIO management tool
root@petasan04:~#
Sure, here it is:
root@petasan04:~# dpkg -s petasan | grep Version
Version: 2.8.1
root@petasan04:~#
root@petasan04:~# uname -r
4.15.0-161-generic
root@petasan04:~#
root@petasan04:~# dpkg -s targetcli-fb
Package: targetcli-fb
Status: install ok installed
Priority: optional
Section: base
Maintainer: PetaSAN
Architecture: amd64
Version: 2.1.49-1petasan
Depends: python3-rtslib-fb (= 2.1.69-1petasan), python3-configshell-fb, python3-dbus, python3-pyparsing, python3-urwid
Description: LIO management tool
root@petasan04:~#
admin
2,930 Posts
Quote from admin on October 24, 2021, 10:42 amYou have an incorrect kernel 4.15. Any idea how you got this and how you are booting from it ? Your best action is to configure the grub menu to boot from the PetaSAN supplied kernel.
You have an incorrect kernel 4.15. Any idea how you got this and how you are booting from it ? Your best action is to configure the grub menu to boot from the PetaSAN supplied kernel.
Ste
125 Posts
Quote from Ste on October 25, 2021, 9:11 amYes, you're right, the grub default had been changed, I'm afraid during my attempts to fix the grub issue described in this thread.
Now I restored the petasan kernel as grub default boot entry and the db_root error has disappeared, but the grub bootloader hasn't been fixed during the update to Petasan 2.8.1. Now any further attempt says that everything is up to date. Is there a way to manually apply the "bug fix for grub bootloader" also to this node ?
Thanks, Dk.
Yes, you're right, the grub default had been changed, I'm afraid during my attempts to fix the grub issue described in this thread.
Now I restored the petasan kernel as grub default boot entry and the db_root error has disappeared, but the grub bootloader hasn't been fixed during the update to Petasan 2.8.1. Now any further attempt says that everything is up to date. Is there a way to manually apply the "bug fix for grub bootloader" also to this node ?
Thanks, Dk.