ROSA Linux Bugzilla – Bug 4161
Update ROSA Fresh LXDE from R2 to R3 failed
Last modified: 2015-01-22 18:10:49 MSK
Created attachment 2996 [details]
System not booting after update ROSA Fresh LXDE from R2 to R3 with latest kernel 3.10.42 installed on SSD drive.
As I can understand, during update ROSA changed UUID of partitions created on drive.
Screenshot attached. sosreport.txt can't copy from damaged system.
Please attach your initrd and tell what dracut version you have currently.
Created attachment 3005 [details]
Dracut version dracut-027-19 I think.
And one detail: not working all kernels after reboot. Old 3.10.19 and new 3.10.42. And next one: on same machine, but with HDD all upgraded fine.
Attached initrd looks ok.
Can you please tell what disks are seen in /dev/disk/by-uuid in dracut resque console
and provide please dmesg |grep "not found" output from the same resque console
(In reply to comment #5)
> Attached initrd looks ok.
> Can you please tell what disks are seen in /dev/disk/by-uuid in dracut
> resque console
> and provide please dmesg |grep "not found" output from the same resque
ls of /dev/disk/by-id shows:
This is really my SSD drive. But, path /dev/disk/by-uuid/ not exists.
There are no grep command in rescue console. But I sed for this. See attached photo :)
Created attachment 3012 [details]
So problem in incorrect initrd image.
After regenerating initrd image manually by dracut -f command, problem was gone and system boot correctly.
Problem repeated again when updating to latest stable kernel 3.10.46. Update log attached.
Created attachment 3066 [details]
(In reply to comment #10)
> Created attachment 3066 [details]
> update log
Regenerate initrd again. Working file. But I found an important thing. If I make reboot after regenerating initrd — initrd will be corrupted again. After regenerating and making poweroff — system boot fine.
Больше никто не жаловался, а миграцию на 2014 будем тестировать отдельно.