Do you mean I shall boot with the 'single' option and shoot a digital photo? 
I spent the last hour rebooting my system and writing down. So at first some 
manually written logs:

udevd [$A]: unable to open 'etc/udev/rules.d': No such file or directory
 * Reading files to boot [OK]
 * Preparing restricted drivers [OK]
 * Setting system clock
 * starting basic networking... [OK]
 * starting kernel event manager
udevd[$B]: specified group 'nut' unknown
[OK]

 *Loading hardware drivers ...
udevd_event[$C]: mknod(/dev/pktcdvd/control, 020660, (10,62) failed: Not a 
directory

It took me 25 hardresets to boot up. The main difference was the change
of numbers ($A,$B,$C) as followed. Only two times the screen wrote lots
of spaces after the 'unable to open "/etc/udev/rules.d"' (lines with
$A,x,x).

reboot num| ($A, $B, $C):
---------------------------------------
01| (785,1441,1692)-hardreset  
02| (784,X,X)-hardreset  
03| (784,1442,1695)-hardreset  
04|BEEPER (785,1442,1701)-hardreset  
05|BEEPER (784,1441,1690)-hardreset  
06| (785,1440,1688)-hardreset  
07| (785,1442,1694)-hardreset  
08| (785,1441,1690)-hardreset  
09| (784,1425,1676)-hardreset  
10| (785,1444,1693)-hardreset  
11| (784,1425,1673)-hardreset  
12| (784,1432,1689)-hardreset  
13| (785,1424,1672)-hardreset  
14|BEEPER (785,1442,1690)-hardreset  
15| (785,X,X)-hardreset  
16| (785,1442,1690)-hardreset  
17| (785,1441,1697)-READ UNDERNEATH  
18| (784,1440,1688)-hardreset  
19| (785,1443,1688)-hardreset  
19| (785,1441,1692)-hardreset  
20| (785,1424,1672)-hardreset  
21| (785,1444,1689)-hardreset  
22| (785,1442,1700)-hardreset  
23| (785,1442,1694)-hardreset  
24| (784,1431,1688)-fsck, finally booting up

Interrestingly lots of different variations occured, but the system never 
booted up when it was beeping.
17: was booting like described on top until:
 * starting basic networking ...  [OK]
[28.9...] EXT3_fs error (device sda5): ext3_dx_find_entry: bad entry in 
directory #5267490: rec_len is smaller than minimal - offset=53248, inode 
4914001, rec_len=0, name_len=0
.
.
.
setting kernel variables (/etc/sysctl.conf) ...
error: "kernel.maps_protect" is an unknown key [FAIL]
.
.
.
checking root file system ...
fsck (was scanning whole drive because of errors) followed by a reboot 


If you still need a digital photograph, let me know. I dont reboot my machine 
very often because of this.

-- 
kernel doesnt boot system, udev not working, missing group nut
https://bugs.launchpad.net/bugs/316725
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to