Oh, I am sorry to hear that. I wish you luck in fixing the HW problem, and when
that happens, let us know and we can continue this debug if possible.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi
Sorry about the lack of reply on this, I had some hardware issues with
this setup and I've been waiting for the time to have a proper go at
fixing it. Unfortunately I failed at that yesterday. This machine no
longer boots, so it's hard for me to get the output..
--
You received this bug
Yeah..I need the full output. A suggestion: you seems to have 2 devices
(sda and sdb) at the kdump failure point, right? So, you could try to
mount one of them, and save the dmesg, like "dmesg > /mnt/dmesg.kdump" .
That'd be perfect!
Thanks again
--
You received this bug notification because
I did a dmesg picture attachment in the previous update. Do you need
more of that output?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1913639
Title:
linux-crashdump is not capable of
Hi Anders, I really appreciate your debug data, thanks a bunch for
buying the PS2 adapter, very useful. So, seems you are observing an
issue with the SATA controller. Could you collect a dmesg from the kdump
environment, in this minimal "(initramfs)" shell?
Also, thanks for the previous data - I
So I got the ps2 adapter and... it looks like this has nothing to do
with ZFS.
I have 4 SATA drives in this machine.
sda - ST2000DM001-1ER1 - zpool storage
sdb - ST2000DM008-2FR1 - zpool storage
sdc - Samsung SSD 860 - my main drive. zpool rpool and bpool.
sdd - Samsung SSD 850 - windows - used
** Attachment added: "kdump_initrd.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460763/+files/kdump_initrd.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "initramfs.debug"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460762/+files/initramfs.debug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "20210206_125923.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460761/+files/20210206_125923.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I also just spend 5$ to order a usb to ps2 adapter, that should make it
a bit easier to figure out what's going on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1913639
Title:
** Attachment added: "regular_initrd.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460764/+files/regular_initrd.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
A : I can confirm that debug was there, and the output on the console is
different. However, plugging in the keyboard again didn't work,
regardless of usb port on the machine, and I can't get a response on ssh
either (or pinging the machine for that matter). Any ideas? I've
attached a photo of
In fact Anders, I just thought of a potential alternative issue, so do
you mind to run a 3rd test?
(c) After running tests (a) and (b) from the last comment, please boot
the machine and edit the file "/etc/default/grub.d/kdump-tools.cfg",
changing the crashkernel parameter there to be exactly
Hi Anders, thanks for your testing. You can show all the initrd scripts
debug output to console, for that you'd need to add the kernel parameter
"debug=vc" for example. But I don't suggest to do that here, since you
seem not able to capture the full console log in plain/text form.
That made my kdump initrd grow from 46mb to 86mb. However, it still
fails.
An additional complication here is that kdump does something with my usb
keyboard so I can't actually write anything when I get to the initramfs
prompt... So it's a bit hard to debug what's going on.
my zpool/rpool setup
Hi Anders, thanks for your report! It seems the issue could lie in the
initramfs-tools package not being able to recognize the need of ZFS if
MODULES=dep is used - in the kdump initrd, we restrict the modules
included to the needed subset, in order to make it smaller and consume
less memory from
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1913639
Title:
linux-crashdump is not capable of mounting zfs root pools
Status in linux
17 matches
Mail list logo
