| 1 |
On 11.03.19 20:55, J. Roeleveld wrote: |
| 2 |
> On March 10, 2019 1:24:14 PM UTC, Dan Johansson <Dan.Johansson@×××.nu> wrote: |
| 3 |
>> After updating a server from kernel-4.14.83 to 4.19.27-r1 (same problem |
| 4 |
>> |
| 5 |
>> with 4.19.23) the server will not boot. |
| 6 |
>> |
| 7 |
>> Grub starts fine and I can select the new kernel. |
| 8 |
>> The kernel starts booting and after mounting "/" and "/usr" (this is a |
| 9 |
>> server with a separate /usr") the boot-process hangs. |
| 10 |
>> |
| 11 |
>> Here are the last few lines displayed before it hangs: |
| 12 |
>> |
| 13 |
>>>> Initializing root device... |
| 14 |
>>>> Detected root: /dev/md127 |
| 15 |
>>>> Mounting /dev/md127 as root... |
| 16 |
>>>> Detected fstype: ext4 |
| 17 |
>>>> Using mount fstype: ext4 |
| 18 |
>>>> Using mount opts: -o ro |
| 19 |
>> 7.6104971 EXT4-fs (md127): mounted filesystem with ordered data |
| 20 |
>> mode. Opts (null) |
| 21 |
>> 7.6572671 init (5708) used greatest stack depth: 13280 bytes left |
| 22 |
>>>> Mounting /dev/dm-O as /usr: mount -t ext4 -o noatime,user_xattr,ro |
| 23 |
>> /deu/dm-O /newroot/usr |
| 24 |
>> 7.6909561 EXT4-fs (dm-0): INFO: recouery required on readonly |
| 25 |
>> filesystem |
| 26 |
>> 7.6925551 EXT4-fs (dm-0): write access will be enabled diming |
| 27 |
>> recouery |
| 28 |
>> 7.9169781 EXT4-fs (dm-0): recovery complete |
| 29 |
>> 7.9223701 EXT4-fs (dm-0): mounted filesystem with ordered data |
| 30 |
>> mode. Opts: user_xattr |
| 31 |
>> 7.9233051 mount (5722) used greatest stack depth, 13000 bytes left |
| 32 |
>>>> /usr already mounted, skipping... |
| 33 |
>>>> Booting (initramfs) |
| 34 |
>> sep-usr init: running user requested applet |
| 35 |
>> |
| 36 |
>> |
| 37 |
>> As I said, the 4.14.83 kernel boots without problem with the same |
| 38 |
>> configuration. |
| 39 |
>> |
| 40 |
>> Any suggestions? |
| 41 |
>> -- |
| 42 |
>> Dan Johansson, |
| 43 |
>> *************************************************** |
| 44 |
>> This message is printed on 100% recycled electrons! |
| 45 |
>> *************************************************** |
| 46 |
> |
| 47 |
> I updated my servers last weekend and all moved to 4.19.27, 2 use ZFS for the filesystem, several are VMs on top of Xen. None had any issues. |
| 48 |
> |
| 49 |
> The messages you show make me think they are from an initrd, not the actual kernel. I would investigate that first and make sure your initrd is actually updated as well. |
| 50 |
> Did you copy the text? Or did you manage to grab the output somehow? |
| 51 |
> |
| 52 |
> Also, which init system and initrd are you using? |
| 53 |
> |
| 54 |
> -- |
| 55 |
> Joost |
| 56 |
> |
| 57 |
|
| 58 |
The text was copied from a screenshot (IPMI-KVM). |
| 59 |
I am using sys-apps/openrc with sys-fs/eudev and I use genkernel to |
| 60 |
build the kernel and the initramfs. |
| 61 |
|
| 62 |
Yes, for me it also looks like it has to do with /ginit (busybox) or |
| 63 |
/sbin/init (sys-apps/sysvinit) and not the kernel. |
| 64 |
|
| 65 |
I also have a bunch of other servers which all updated fine to 4.19.?? |
| 66 |
|
| 67 |
I tried the suggestion from Hasan to run "make synconfig" but that did |
| 68 |
not change any option in .config. |
| 69 |
|
| 70 |
I'll try to rebuild kernel/init/busybox/intel-microcode again next weekend. |
| 71 |
|
| 72 |
|
| 73 |
-- |
| 74 |
Dan Johansson |
| 75 |
*************************************************** |
| 76 |
This message is printed on 100% recycled electrons! |
| 77 |
*************************************************** |
Archives