Date: Thu, 28 Mar 2013 11:05:58 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: David Demelier <demelier.david@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: SU+J hard recovery failure Message-ID: <FA931FE9-D64B-4A32-9E76-4F4146DD21E3@gsoft.com.au> In-Reply-To: <CAO%2BPfDdH%2BfZvzYqYqZW-_7FRH=gBhW0G4Bj4Ho%2BFTqeEneO41Q@mail.gmail.com> References: <CAO%2BPfDdH%2BfZvzYqYqZW-_7FRH=gBhW0G4Bj4Ho%2BFTqeEneO41Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 27/03/2013, at 18:43, David Demelier <demelier.david@gmail.com> wrote: > Yesterday I had a panic on my laptop. Unfortunately the SU+J was not > able to recovery the file system, the error was something like : > > Unknown error: Help! > Could not find directory 9854215 > > And it went to the single user mode, I needed to fsck_ufs manually to > recover the disk. What afraid me is what if happens on a headless > machine? It will be hard to recover. For headless remote systems I use fsck_y_enable="YES". In my experience 'fsck -y' almost invariably recovers the disk to a point where it can boot and then I can login remotely. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C [-- Attachment #2 --] 0 *H 01 0 + 0 *H Y040 0 *H 0}1 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o -we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U 00U 0 U Sr풜\|~5NԸQ0 U #0N @[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[U T0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u +70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^ #wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0& ;@#13qۑ& ̢o 6r_;GO>*I( 74XS1r3)!LJy6Kotˆ# _wSr ;B ADp(fs 䰷6%.W0J3:bC<8t X1<Cn=t==wST~\wkBf|15zUP)(IjVB!OfI=bb\4-*em/нSJm7N[]'@ڽ D9Kr>R7/|o^I@ټ'Pa $ z9a'L)( I}vcH]۸D*W} m>Q|C.(,lQ0 0y0 *H 01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 120705022129Z 130706155449Z0a10U mumuFi49xwpdkQhw1 0 U doconnor@gsoft.com.au1$0" *H doconnor@gsoft.com.au0"0 *H 0 #AV* 4g'Ja<F?LюT0>S6>+y0iu3ڄ\SպX3<UwSGSRE5\ a2U7A^ʥʼN ͫt8U=Nc,ДS%̷$CULF< h #Kvpvf)9嗶OlƾJa[]J]?6mA֦ aH N7^ו8|p}j* 00 U 0 0 U 0 U %0++0 U .>npy2Uؚ0 U #0Sr풜\|~5NԸQ0 U 0doconnor@gsoft.com.au0!U 00 +700.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.0+00' StartCom Certification Authority0dLiability and warranties are limited! See section "Legal and Limitations" of the StartCom CA policy.06U /0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U 0http://www.startssl.com/0 *H >t=đY aKXw܉.K9Qj*ه'B\A]z% rn2KK6!uG=y.miUB*6Fv%P: 4g㗋M6EE^vo6ذD 6,8wyK.S }#;H|9rO>^bAcIBނ' Щ<ALe#F%P/[4&(<+az4Ajلy{p1o0k001 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CAy0 + 0 *H 1 *H 0 *H 1 130328003559Z0# *H 1TDh G8Hm0 +71001 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CAy0 *H 101 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CAy0 *H Y(o3!v-{EPXmȾOf}@B 80@$_Yi.M^(7A&yx|al7w [<&+qydT'=YA c6+3Lɺ *ص+5+alEC+ GbZN 6~ bh؊y+a @NP?Oi J R{q!=|v v[XY0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FA931FE9-D64B-4A32-9E76-4F4146DD21E3>