Date: Sat, 8 Dec 2012 08:33:55 +0100 From: CeDeROM <cederom@tlen.pl> To: Chuck Burns <break19@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: 9.1-RC3 LiveCD missing features Message-ID: <CAFYkXjnPd5StvogL%2BOmSQOtYejJVQwVdG2pF5G3tygO7peFu4A@mail.gmail.com> In-Reply-To: <CAFYkXjkf2Hyv%2BgXP92sqQf8_sWiy0A%2BC9WMiLuWOVy6FertGkQ@mail.gmail.com> References: <CAFYkXj=R=V=3pUH9FbKq3pdqtga-EuJuTB1avZxi2bkLhUs5WA@mail.gmail.com> <50C26999.6090802@gmail.com> <CAFYkXjk8bgaJRkjEyMsfgwRD45K=DX%2BEJJOPLEa_WGBv7CS6pg@mail.gmail.com> <CAFYkXjkf2Hyv%2BgXP92sqQf8_sWiy0A%2BC9WMiLuWOVy6FertGkQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Running fsck -t ufs -fy solved the issue!! http://i47.tinypic.com/35m1qxk.jpg How reliable is new UFS2-SU+J? Are there any journal verification routines (I heard about some chcecks in the background). Will automatic fsck on boot force full filesystem checks in any case (like filesystem related kernel panic will set full filesystem check flag)? This was the filesystem issue not the hard drive (its new 2TB WD disk preformatted before use). Having badblocks and other test solutions on the LiveCD would at least detect some hardware issues I gues, I give +1 for service/support tools in LiveCD :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjnPd5StvogL%2BOmSQOtYejJVQwVdG2pF5G3tygO7peFu4A>