Today I learnt this: Do NOT use ext4 for the /boot partition, where your kernel resides.
I did this on my EEEPC to speed up boot, and today I got at boot the error message: initrd.img corrupt. My EEEPC has got an ssd inside and /usr, /home and /var are encrypted partitions. It took me hours and hours to fix this. First I tried ext2fs, with no success. I could run Trinity Rescue Kit from a sd card, and I created a chroot, but not all was possible to do in the chroot. After lots of tries I got the solution: 1. I backuped all the content of /boot to another drive. 2. Booted with a livefile and formatted /boot to ext2. 3. Restored /boot 4. Edited /etc/fstab, removed the UUID of /boot and removed disacard,noatime 5. Now I could boot again. 6. From the running system started "update-initramfs -u" 7. Did "dpkg-reconfigure linux-base", so I got the UUID in all necessary config files again. 8. For making all sure. did "update-grub" 9. Finally test, rebooted again, everything was ok. So NEVER, NEVER, NEVER use ext4 for /boot! Don't do it! (If I would have read the manual, I should have known, ext4 and grub is still in experimental state) Best regards Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201304231752.54550.hans.ullr...@loop.de
