Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 571612 - sys-kernel/gentoo-sources-4.4.0 crashes on boot with mdraid 10 and reisferfs
Summary: sys-kernel/gentoo-sources-4.4.0 crashes on boot with mdraid 10 and reisferfs
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-12 03:26 UTC by Harris Landgarten
Modified: 2017-10-04 19:11 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
config file (config-4.4.0-gentoo,111.07 KB, text/plain)
2016-01-12 03:26 UTC, Harris Landgarten
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harris Landgarten 2016-01-12 03:26:04 UTC
Created attachment 422614 [details]
config file

kernel-4.4.0 starts up. Starts reassembling raid volumes. Says it cannot get exclusive access to map file.

Then it assembles my root raid, says my lvm raid is unclean, but right after it logs that it is good.

It then pauses for a few minutes and logs it is looking at the log file for the root reiserfs

After another long wait the kernel crashes.

No problems booting 4.3.3

I am attaching the kernel.config
Comment 1 Dan Moulding 2016-02-03 00:06:11 UTC
Harris, it might be helpful to also provide the config you are using to (successfully) boot the 4.3.3 kernel.

Also, any chance you could post the panic?
Comment 2 Harris Landgarten 2016-02-03 04:49:24 UTC
Because of issues with reiserfs I changed the root filesystem to btrfs and now have no issues booting the 4.4 kernel with mdraid 10 arrays as I had before.

The issue is that the 4.4 kernels with the same initramfs as I was using with 4.3 for some reason were unable to assemble the md10 root when it was reiserfs based.

Unfortunately I can no longer reproduce the issue. There were some mdraid changes made to 4.4 so I assume the issue was related.