findfs: unable to resolve uuid on boot

Forum rules
We don't support installations in VirtualBox, VMWare, qemu or others. We ignore posts about WINE, PlayOnLinux, Steam and Skype. We don't support btrfs, lvm, UEFI, side-by-side installations with GPT or dualboot with anything newer than Windows XP.
Google your problem first. Check the Wiki. Read the existing threads. It's okay to "hijack" an existing thread, yes! If your problem is not yet covered, open a new thread. To get the quickest possible help, mention the exact release codename in your post (uname -a is a good idea, too). Due to the lack of crystal balls, attach the output of lspci -nnk if you encounter hardware problems.
User avatar
PBMax
Saltimbocca-Roller
Posts: 15
Joined: Wed Aug 07, 2013 9:30 am

findfs: unable to resolve uuid on boot

Unread post by PBMax » Wed Apr 23, 2014 9:39 am

Hello all,

First things first...
cbp@mobbin-one:~$ uname -a
Linux mobbin-one 3.12-8.towo-siduction-amd64 #1 SMP PREEMPT Thu Jan 16 09:11:45 UTC 2014 x86_64 GNU/Linux
I've seen this error message on bootup but I can't find it in the logs. (Don't ask how many times I had to reboot to read the message!). Googling led me to some posts about fstab not being right (incorrect UUIDs) but that doesn't apply to me. (I did check it, though.) I've done a dist-upgrade since the install and the error message remains. It doesn't seem to affect anything and I'm wondering if this is a common issue most folks simply ignore. (I'm assuming here since there isn't many complaints I could find.)

Anyhoo, is there away to correct this or should I ignore it?

PBMax

User avatar
ivanovnegro
Minister of Truth
Posts: 5449
Joined: Wed Oct 17, 2012 11:12 pm

Re: findfs: unable to resolve uuid on boot

Unread post by ivanovnegro » Wed Apr 23, 2014 7:34 pm

I am not a pro when it comes to such things but if it does not bite I would just ignore it. Maybe try another kernel, a newer one. This one you use is already older.

I have also an error message on boot (happens every once in a while) but it has nothing to do with your issue though it seems not to happen with towo kernels.

If you are bothered you can wait that someone else pops in or try to google it.

Post Reply