Bug 4161 - Update ROSA Fresh LXDE from R2 to R3 failed
: Update ROSA Fresh LXDE from R2 to R3 failed
Status: RESOLVED WONTFIX
Product: Desktop Bugs
Classification: ROSA Desktop
Component: LXDE Edition
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: Aleksandr Kazantcev
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-25 13:14 MSD by Eugene Budanov
Modified: 2015-01-22 18:10 MSK (History)
2 users (show)

See Also:
RPM Package:
ISO-related:
Bad POT generating:
Upstream:


Attachments
screenshot (80.06 KB, image/jpeg)
2014-06-25 13:14 MSD, Eugene Budanov
Details
initrd image (4.36 MB, application/octet-stream)
2014-06-25 22:59 MSD, Eugene Budanov
Details
sed search (79.89 KB, image/jpeg)
2014-06-26 22:02 MSD, Eugene Budanov
Details
update log (3.98 KB, application/octet-stream)
2014-07-19 15:07 MSD, Eugene Budanov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Budanov 2014-06-25 13:14:13 MSD
Created attachment 2996 [details]
screenshot

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.
Comment 1 Alexander Burmashev 2014-06-25 13:19:33 MSD
Please attach your initrd and tell what dracut version you have currently.
Comment 2 Eugene Budanov 2014-06-25 22:59:56 MSD
Created attachment 3005 [details]
initrd image
Comment 3 Eugene Budanov 2014-06-25 23:04:46 MSD
Dracut version dracut-027-19 I think.
Comment 4 Eugene Budanov 2014-06-25 23:09:29 MSD
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.
Comment 5 Alexander Burmashev 2014-06-26 15:15:57 MSD
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
Comment 6 Eugene Budanov 2014-06-26 22:02:20 MSD
(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
> console

ls of /dev/disk/by-id shows:
ata-TS64GSSD-M002495430450

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 :)
Comment 7 Eugene Budanov 2014-06-26 22:02:43 MSD
Created attachment 3012 [details]
sed search
Comment 8 Eugene Budanov 2014-06-30 21:54:28 MSD
So problem in incorrect initrd image. 

After regenerating initrd image manually by dracut -f command, problem was gone and system boot correctly.
Comment 9 Eugene Budanov 2014-07-19 15:06:42 MSD
Problem repeated again when updating to latest stable kernel 3.10.46. Update log attached.
Comment 10 Eugene Budanov 2014-07-19 15:07:20 MSD
Created attachment 3066 [details]
update log
Comment 11 Eugene Budanov 2014-07-22 00:12:50 MSD
(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.
Comment 12 Stanislav Fomin 2015-01-22 18:10:49 MSK
Больше никто не жаловался, а миграцию на 2014 будем тестировать отдельно.