Results 1 to 2 of 2
Hy everybody:
I've got a Debian with a 2.6 kernel installed on an embedded PC, and this embedded is accessible only by LAN (i.e. i login via ssh if i ...
- 07-16-2007 #1Just Joined!
- Join Date
- Jul 2007
- Posts
- 2
skipping boot warnings / errors
Hy everybody:
I've got a Debian with a 2.6 kernel installed on an embedded PC, and this embedded is accessible only by LAN (i.e. i login via ssh if i want to change something).
Last week something wrong happened inside the embedded, and now i can only ping the embedded correctly, but the ssh and ftp services are not up (better, i suppose... the shell says "connection refused" even if i write "ftp 192.168.151.102").
I fear that the boot stops at a certain step (quite surely after the initialization of the eth0, otherwise the ping wouldn't work), prompting for some user intervention...
I will unmount the diskOnModule that is inside the embedded and recopy the image of the distro, but i want to change the behavior of the booting in order to have some other possibilities the next time this problem will appear.
For doing so, i've looked for some parameters to give or to the grub or to whoever needs, just to let the boot process decide the options when some errors occur, instead of an user (that physically here cannot be present). Note this may lead to 2 behaviors:
a) kernel panic (=> embedded unusable, but i can understand it just because the ping should fail after the panic)
b) some problems, but ssh service up (=> embedded usable and fixable (hopefully)
)
c) some problems, and ssh service down (=> no changing)
Unfortunatly i've found anything in the grub man pages, in google and in the forums...
If somebody will have some tips the possibilities of being fired will be reduced
Anyway thanks everybody
- 07-19-2007 #2Just Joined!
- Join Date
- Jul 2007
- Posts
- 2
I found maybe a piece of solution; for now i made the system bypassing the questions about filesystem errors.
In the "/etc/init.d/checkroot.sh" script there's a call to the "fsck"; the position of the call is in the #if-fi block which condition is:
"if [ "$rootcheck" = yes ]"
the previous command line calling "fsck" was:
"fsck $spinner $force $fix -t $roottype $rootdev"
then I added the "-p" flag, that forces the "fsck" to correct automatically the filesystem errors without prompting; now the command line is:
"fsck $spinner -p $force $fix -t $roottype $rootdev".
I hope it will be useful for somebody


Reply With Quote
