Em Wed, 15 Feb 2012 21:29:56 -0300, Nilton Jose Rizzo escreveu > Em Wed, 15 Feb 2012 17:25:56 -0200, Marcelo Gondim escreveu > > Em 15/02/2012 16:56, Enio Marconcini escreveu: > > > 2012/2/15 Enio Marconcini<[email protected]> > > > > > >> salve galera. > > >> o servidor com freebsd 9.0Stable, estava rodando normalmente, em testes, > > >> hoje fui reiniciar ele, e durante o boot ficou parado com essa mensagem: > > >> > > >> Starting file system checks: > > >> /dev/ada0p2: NO WRITE ACCESS > > >> /dev/ada0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY > > >> Automatic file system check failed; help! > > >> ERROR: ABORTING BOOT (sending SIGTERM to parent)! > > >> Feb 15 14:32:44 init /bin/sh on /etc/rc terminated abnormally, going to > > >> single user mod > > >> Enter full pathname of shell or RETURN for /bin/sh: > > >> > > >> o dispositivo /dev/ada0p2 é o root filesys / > > >> pressionei enter e entrei com o /bin/sh mesmo, consegui montar as > > >> partições com mount -a (não retornou erro) > > >> se eu digitar exit ele sobe para o modo multiuser normalmente e inicia os > > >> serviços > > >> > > >> dei uma busca no google mas não consegui achar nada especificamente para > > >> este caso... alguém já passou por isso ou sabe o motivo aparente deste > > >> acontecimento? > > >> > > >> -- > > >> *ENIO RODRIGO MARCONCINI* > > >> @eniomarconcini<http://twitter.com/eniomarconcini> > > >> *[ $[ $RANDOM % 6 ] == 0 ]&& rm -rf / || echo "You live"** > > >> * > > >> * > > >> * > > >> *"H**ave a trouble with windows: reboot!* > > >> *Have a trouble with unix: be root!"* > > >> > > >> > > > mais um detalhe eu notei que isso acontece depois que eu ajustei o > > > securelevel=2 no /etc/sysctl.conf > > > dei boot com securelevel desativado e funcionou normalmente. > > > > > > > > Oi Enio, > > > > Mas tipo toda vez que você inicia com securelevel=2 acontece isso ou > > só aconteceu uma vez? > > ------------------------- > > Histórico: http://www.fug.com.br/historico/html/freebsd/ > > Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd > > Olhando no man: > The kernel runs with five different security levels. Any super-user > process can raise the level, but no process can lower it. The security > levels are: > > -1 Permanently insecure mode - always run the system in > insecure mode. This is the default initial value. --More- > -(byte 21068) 0 Insecure mode - immutable and append-only > flags may be turned off. All devices may be read or > written subject to their permissions. > > 1 Secure mode - the system immutable and system append-only > flags may not be turned off; disks for mounted file > systems, /dev/mem and /dev/kmem may not be opened for > writing; /dev/io (if your platform has it) may not be > opened at all; kernel modules (see kld(4)) may not be > loaded or unloaded. > > 2 Highly secure mode - same as secure mode, plus disks may > not be opened for writing (except by mount(2)) whether > mounted or not. This level precludes tampering with file > systems by unmounting them, but also inhibits running > newfs(8) while the system is multi- user. > > In addition, kernel time changes are restricted to less > than or equal to one second. Attempts to change the time > by more than this will log the message ``Time adjustment > clamped to +1 second''. > > 3 Network secure mode - same as highly secure mode, plus IP > packet filter rules (see ipfw(8), ipfirewall(4) and > pfctl(8)) cannot be changed and dummynet(4) or pf(4) > configuration cannot be adjusted. > > The security level can be configured with variables documented > in rc.conf(8). >
Provavelmente o fdisk precisou escrever algo no disc e não pode por isso a inconsistencia .... vai ver ele não conseguir finalizar todos os processos no sync anterior .... -- Nilton José Rizzo 805 Informatica Disseminando tecnologias 021 2413 9786 --- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ------------------------- Histórico: http://www.fug.com.br/historico/html/freebsd/ Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd
