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 looks like this:
```
pool: bpool
state: ONLINE
scan: scrub repaired 0B in 0 days 00:00:04 with 0 errors on Sun Jan 10
00:24:05 2021
config:
NAME STATE READ WRITE CKSUM
bpool ONLINE 0 0 0
sdc1 ONLINE 0 0 0
errors: No known data errors
pool: rpool
state: ONLINE
scan: scrub repaired 0B in 0 days 00:18:34 with 0 errors on Sun Jan 10
00:42:35 2021
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sdc2 ONLINE 0 0 0
```
sdc is just a standard sata drive, so it should just work out of the box
with any fairly recent kernel, I haven't needed any non standard changes
for that drive in many many kernels.
Can I easily modify the initrd that's built into this initrd and add
some debug info to stdout somehow?
** Attachment added: ""screenshot""
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5458267/+files/20210130_122038.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913639
Title:
linux-crashdump is not capable of mounting zfs root pools
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
