On Wed, May 4, 2011 at 2:27 AM, <cac...@quantum-sci.com> wrote: > > Having a failure that may be because grub2 doesn't BTRFS. /boot is ext3 and > / is BTRFS.
Does Debian (or whatever distro you use) support BTRFS "/"? If yes, you should ask them. If no, then you should've already known that there's a risk when using unsupported filesystem. > > # dpkg -r linux-image-2.6.32-5-amd64 > (Reading database ... 136673 files and directories currently installed.) > Removing linux-image-2.6.32-5-amd64 ... > Examining /etc/kernel/postrm.d . > run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.32-5-amd64 > /boot/vmlinuz-2.6.32-5-amd64 > run-parts: executing /etc/kernel/postrm.d/zz-update-grub 2.6.32-5-amd64 > /boot/vmlinuz-2.6.32-5-amd64 > /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). > run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 > Failed to process /etc/kernel/postrm.d at > /var/lib/dpkg/info/linux-image-2.6.32-5-amd64.postrm line 234. > dpkg: error processing linux-image-2.6.32-5-amd64 (--remove): > subprocess installed post-removal script returned error exit status 1 > Errors were encountered while processing: > linux-image-2.6.32-5-amd64 Looks like grub problem. I know that Ubuntu Natty's grub-pc (grub2) work just fine, so you might be able to fix it by upgrading to newer grub/grub-pc (perhaps from Debian-unstable). -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
