

I would be really grateful if somebody could help with that.Ĭode: Select all mount /dev/md0 chroot /mntĬhroot: failed to run command `/bin/bash': Exec format chroot /mntĬhroot: failed to run command `/bin/bash': Exec format grub-install -root-directory=/mnt /dev/md0Ĭp: writing `/mnt/boot/grub/915resolution.mod': No space left on dfįilesystem 1K-blocks Used Available Use% Mounted on I am not new to linux (have a good overview), but I definitely need a lot of learning in this field. Like I said I tried all documented solutions - but none really worked for me, or were related to other distributions or invoked by different actions (kernel upgrades). The only problem is that USB stick is only 8GB. I used latest Ubuntu live on USB stick where I was able to install my debian raid - so disk manager sees all raid partitions (including root) that can easily be mounted.


GRUB shows two kernels: 2.6.26-2 and 2.6.26-2 (single user) but they both show the same error on boot. My system is Debian Lenny AMD 64 2.6.26-2 with software RAID 1 with traditional (old school) 5 partitions with recommended sizes. Or: did some automatic upgrades via synaptic apt. The system was working smoothly until IĮither: temporarily moved a file from boot menu (I ran out of space on root partition and tried to do "magic" - my mistake) and then put in the exactly same place but it did not work since then. I checked everything that was written on this topic, but things mostly happened when people were putting new kernels on - so described solutions didn't work for me. I got obviously very famous "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
