Summary: | LiveDVD 11.2 persistence is not working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry Zamaruev <dmitry.zamaruev> |
Component: | [OLD] Unspecified | Assignee: | Team Anniversary <ten> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 378027 | ||
Attachments: | Boot error |
Description
Dmitry Zamaruev
2011-08-15 13:37:25 UTC
This will be fixed on next release, odd this stopped working since it was fine before. I will made the adjustments for it to work now. likewhoa there is a new image located at http://77.110.8.68/gentoo11 which implements the fix to this. Feel free to test. Created attachment 283621 [details]
Boot error
Cannot even boot latest amd64-multilib-r2 ISO image, see attach. Previous amd64-multilib-11.2 booted successfully on same virtual machine with same conditions. please try -r2 just a note, i only tested the livedvd-x86-amd64-32ul-11.2.iso image. Checked latest available -r4 images (both 32ul and amd64). - 32bit boots successfully, persistence mode working as expected, default image size is big enough - 64bit fails to boot (in both images amd64-multilib and amd64-32ul) with same error described above PS. It would be nice if persistence_mb parameter will be checked to be > defaul_value. Because if one will setup it lower than default size - it will be out of space and unusable. (In reply to comment #7) > Checked latest available -r4 images (both 32ul and amd64). > - 32bit boots successfully, persistence mode working as expected, default image > size is big enough > - 64bit fails to boot (in both images amd64-multilib and amd64-32ul) with same > error described above > > PS. It would be nice if persistence_mb parameter will be checked to be > > defaul_value. Because if one will setup it lower than default size - it will be > out of space and unusable. -r4 didn't have the aufs3 update cleanly applied so sources needed to be restored. -r5 should just work. Thanks for reporting and I have included a check on persistence_mb value so it does not fall below require space. likewhoa (In reply to comment #8) > -r4 didn't have the aufs3 update cleanly applied so sources needed to be > restored. -r5 should just work. Thanks for reporting and I have included a > check on persistence_mb value so it does not fall below require space. Checked -r5 image - all works as expected. Thanks! Great job. |