Re: Wubi megathread
Originally Posted by
bcbc
The only thing I can see is that the initrd.img for your latest kernel is broken into 3 fragments. I actually haven't noticed this bootinfoscript diagnostic before... so take it for what it's worth.
What I would do is either rebuild the initrd.img or run fsck on the root.disk (or both).
Code:
sudo update-initramfs -u
How does the initrd.img get corrupted? If it needs a rebuild I would presume that to be the case. I'd be also correct in assuming after I do that a reboot is in order right? Breaking up that name I think it stands for initialization of RAM and the Fixed Disks. As far as I can see and I'm not coder by a mile, alot of commands share some logic and straight English translation.
Also check how much space you have remaining on the root.disk. On the following command look for (loop0) that represents the root.disk:
Here's the entry for that command. BTW. Thanks for it. I'm making a collection of these in a reference document. It would be nice if there was a place where I could find them all and their functions.
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 29G 9.2G 19G 34% /
none 1.9G 796K 1.9G 1% /dev
none 2.0G 7.9M 2.0G 1% /dev/shm
none 2.0G 444K 2.0G 1% /var/run
none 2.0G 0 2.0G 0% /var/lock
/dev/sde5 362G 44G 319G 12% /host
I have to wonder if Wubi really did put my install on the 3rd partition of the main drive. Thanks for the straightforward tips
When in doubt, check it out!
If all else fails, check the plug!
Bookmarks