You are not logged in.
Hi,
been away for five weeks and lost my desktop via ssh after a kernel update a few weeks back.
Now I'm home it tells me that it wants to mount /tmp3. Naturally it fails 'cos it doesn't exist in /etc/fstab.
Have I missed something while I was away? Some important piece of news that fstab is deprecated or somefink?
Tearing my hair out...
Last edited by toad (2010-08-23 20:52:02)
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
Update:
blkid gave me a tmp3 readout on sdb11 which had existed previously but which I had mapped to tmp as I frequently ran out of space on my 10GB /.
So I adjusted my fstab to have sdb11 (well, the UUID) as tmp3 again and still the system threw up over it. Seems like I have to read up on man blkid as I don't understand what is happening.
EDIT:
I adjusted /etc/blkid.tab to reflect the new situation but still no joy. I then checked udev rules but there is no mention of sdb11 in connection with tmp3.
So the question remains:
Against which wall have I not banged my stupid head against to find the (obvious) answer???
Last edited by toad (2010-08-23 19:57:36)
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
Bah,
all I had to do was an fsck.ext4 /dev/sdb11 and it booted just fine.
I am still not quite sure why it kept on referring to that partition as tmp3 as I could not find any reference to it but I will still mark it as solved.
Any enlightening comments are most welcome
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline