Re: SU+J hard recovery failure

看板FB_stable作者時間12年前 (2013/04/27 13:33), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串3/3 (看更多)
Le jeudi 28 mars 2013 11:05:58 Daniel O'Connor a =E9crit : > 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=3D"YES". > = > In my experience 'fsck -y' almost invariably recovers the disk to a point > where it can boot and then I can login remotely. > = When the problem appeared, I could not use fsck -y because it will asks "Us= e = journal?" and if journal is used the error above reappears and you can not = clean the file system.. I needed to do a full fsck without any journal at all. > -- > 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 Regards, -- = David Demelier _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
文章代碼(AID): #1HUsCQ8j (FB_stable)
文章代碼(AID): #1HUsCQ8j (FB_stable)