Public bug reported:
Binary package hint: casper
$ grep such /var/log/casper.log
/init: line 1: can't open /dev/sda: no such file
/init: line 1: can't open /dev/sda: no such file
/init: line 1: can't open /dev/sda1: no such file
/init: line 1: can't open /dev/sda2: no such file
/init: line 1: can't open /dev/sda3: no such file
/init: line 1: can't open /dev/sda4: no such file
/init: line 1: can't open /dev/sda5: no such file
/init: line 1: can't open /dev/sda6: no such file
/init: line 1: can't open /dev/sda7: no such file
/init: line 1: can't open /dev/sda8: no such file
Harmless in most cases, but they will also show up on the screen. They come
from get_fstype when
eval $(fstype < $1)
is called with a non-existing device node.
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~tormodvolden/casper/guard-dev-nodes
--
"no such device" errors when booting
https://bugs.launchpad.net/bugs/425159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
