1 |
I encountered this a few times in the past 2 3 years i'm using catalyst. I |
2 |
never could fix it. |
3 |
Instead i switched to zisofs. |
4 |
That is if you don't mind having some 20-30Mb extra space on the iso. |
5 |
|
6 |
Also i have to note that this happened always after some time since the last |
7 |
stage2 building. So for me it was just the portage tree that changed. Then |
8 |
switching back to squashfs after 2 3 months was sometimes ok but not all the |
9 |
time. In my experience, i don't think this has to do with catalyst |
10 |
versioning. |
11 |
I tried numerous times to rebuild but this led me no where. |
12 |
|
13 |
Zisofs did the trick although i'm still wondering why. |
14 |
|
15 |
Sorry i can't be of more help. |
16 |
|
17 |
Erick |
18 |
|
19 |
sent from Android |
20 |
|
21 |
Le 3 août 2009, 2:44 PM, "lurker" <lurker@×××××××.com> a écrit : |
22 |
|
23 |
A few days ago I made a few small changes (just to the root overlay) to |
24 |
a catalyst project of mine and re-ran from livecd2 stage. For some |
25 |
reason boot now fails during init: |
26 |
|
27 |
[...] |
28 |
>> Mounting squashfs filesystem |
29 |
mount: mounting /dev/loop0 on /newroot/mnt/livecd failed: Invalid argument |
30 |
!! Failed to $1: failing back to the shell... |
31 |
BusyBox v1.7.4 [...] |
32 |
|
33 |
If I then, from the ash shell that you're thrown into, run "mount -o |
34 |
loop -t squashfs /newroot/mnt/cdrom/image.squashfs /newroot/mnt/livecd" |
35 |
I get the same error as above (invalid argument). Nothing appears in dmesg. |
36 |
|
37 |
I've tried upgrading catalyst from 2.0.6 to 2.0.6.905, and genkernel |
38 |
(the one used "inside" the catalyst project) from 3.4.10-r2 to |
39 |
3.4.10.905, but nothing helps. Not that I expected it to do anything |
40 |
since the changes I made since my last successful build cannot possibly |
41 |
have anything to do with any of the bugs fixed in the newer versions. |
42 |
|
43 |
How can I troubleshoot this further? |