| View previous topic :: View next topic |
| Author |
Message |
clostry
n00b
Joined: 26 Nov 2008
Posts: 26
|
 Posted: Wed Feb 13, 2013 5:17 pm Post subject: [SOLVED] Boot fails after upgrade |
 |
|
Hi,
after the last update i can't get my system working anymore, it stops at boot saying that /dev/tty* are not found.
I thought it could be the udev upgrade (~196-r1 -> 197), the kernel was ok (i have kernel versions 3.3.8 and 3.6.11 already configured for udev-19*), but downgrading to 171 solved nothing.
I have really no idea where to look for the problem source.
Any help would be really appreciated!
Clos.
Last edited by clostry on Wed Feb 13, 2013 6:47 pm; edited 1 time in total |
|
| Back to top |
|
 |
clostry
n00b
Joined: 26 Nov 2008
Posts: 26
|
| Posted: Wed Feb 13, 2013 5:34 pm Post subject: |
|
|
This is my rc.log
| Code: |
rc boot logging started at Wed Feb 13 18:25:52 2013
* Setting system clock using the hardware clock [UTC] ...
[ ok ]
* Autoloaded 0 module(s)
* Setting up the Logical Volume Manager ...
No volume groups found
No volume groups found
No volume groups found
[ ok ]
* Checking local filesystems ...
/dev/sda3: clean, 802330/2240224 files, 4386266/8960000 blocks
/dev/sda1: clean, 85/50400 files, 62736/204800 blocks
[ ok ]
* Remounting root filesystem read/write ...
[ ok ]
* Remounting filesystems ...
[ ok ]
* Updating /etc/mtab ...
[ ok ]
* Activating swap devices ...
[ ok ]
* Mounting local filesystems ...
[ ok ]
* Configuring kernel parameters ...
[ ok ]
* Creating user login records ...
[ ok ]
* Cleaning /var/run ...
[ ok ]
* Wiping /tmp directory ...
rm: impossibile rimuovere "./shm": Dispositivo o risorsa occupata
rm: impossibile rimuovere "./pts": Dispositivo o risorsa occupata
rm: impossibile rimuovere "./shm": Dispositivo o risorsa occupata
rm: impossibile rimuovere "./pts": Dispositivo o risorsa occupata
[ ok ]
* Setting terminal encoding [UTF-8] ...
[ ok ]
* Setting console font [default8x16] ...
Couldn't open /dev/tty1
[ !! ]
* ERROR: consolefont failed to start
* Setting hostname to archimede ...
[ ok ]
* Setting keyboard mode [UTF-8] ...
Couldn't open /dev/tty1
Couldn't open /dev/tty2
Couldn't open /dev/tty3
Couldn't open /dev/tty4
Couldn't open /dev/tty5
Couldn't open /dev/tty6
Couldn't open /dev/tty7
Couldn't open /dev/tty8
Couldn't open /dev/tty9
Couldn't open /dev/tty10
Couldn't open /dev/tty11
Couldn't open /dev/tty12
[ ok ]
* Loading key mappings [it] ...
[ ok ]
* Bringing up interface lo
* 127.0.0.1/8 ...
[ ok ]
* Adding routes
* 127.0.0.0/8 via 127.0.0.1 ...
[ ok ]
* Mounting misc binary format filesystem ...
[ ok ]
* Loading custom binary format handlers ...
[ ok ]
* Activating additional swap space ...
[ ok ]
* setting up tmpfiles.d entries ...
[ ok ]
* ERROR: urandom failed to start
rc boot logging stopped at Wed Feb 13 18:25:56 2013
|
|
|
| Back to top |
|
|
clostry
n00b
Joined: 26 Nov 2008
Posts: 26
|
| Posted: Wed Feb 13, 2013 6:55 pm Post subject: |
|
|
The problem was that i accidentally commented the shm line in fstab instead of one of my tmpfs.
I did this one month ago or so...err...i seldom reboot my laptop...  |
|
| Back to top |
|
|
clostry
n00b
Joined: 26 Nov 2008
Posts: 26
|
| Posted: Wed Apr 17, 2013 1:51 pm Post subject: |
|
|
This happened again....
I was wrong, that wasn't the shm line in fstab, in fact this is not necessary anymore.
The problem occourred because I used devtmpfs to mount my /tmp instead of tmpfs, as I found out reading another thread. |
|
| Back to top |
|
|
|
Kernel & Hardware
