I have to add: I'm not sure my problem was due to that "superblock
time". I wouldn't have been in panic if I realized it simply was a date
problem, ...but maybe it was as I read quite quickly.
I had no problem *at all* when chainloading from grub1.
fsck on partitions solved it *for good*, even if I had to reboot twice
so that it tells me about other partitions which had a problem too.
It was a really fresh Debian install, and I can't remember of any tool I
may have used during my session which would have altered my partitions
(except grub-upgrade -> I knew I was going to make that upgrade during
this session so I wasn't going to screw up everything) ; the major thing
I did, and which I mention is first post, being that gnome reinstall
which I found weird to happen (this was because meta package "gnome"
wasn't selected).
However due to the unmethodic of how I proceeded I can't affirm that
problem was due to grub-upgrade for sure.
If there was a list of typical error messages which can trigger that
CTRL-D thing and ask for fsck after being unable to mount root
partition, then I'd gladly have an eye on it and see if one could be the
one I saw ... ahum.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
