Date: Sun, 19 Mar 2017 13:15:01 +0100 From: CeDeROM <cederom@tlen.pl> To: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: Second severe crash in six weeks Message-ID: <CAFYkXjn7SGgb-%2B%2B62%2BwXYZw9PsRf11oFOeQC4A8oz3sHG6vC1A@mail.gmail.com> In-Reply-To: <20170319114652.GA1287@becker.bs.l> References: <20170315222221.GA18691@becker.bs.l> <eb296c6a-a437-9b02-3e80-067eaba2cf04@FreeBSD.org> <20170317195043.GA5295@becker.bs.l> <alpine.BSF.2.20.1703171355520.23129@wonkity.com> <CAFYkXjksTd2vaab4J23UM_vy4bhuh2BnQY6xjt6=3Vgad=b07A@mail.gmail.com> <20170319114652.GA1287@becker.bs.l>
next in thread | previous in thread | raw e-mail | index | archive | help
If fsck -f on all partitions did not find any problems then it looks like either hardware failure or a bug somewhere :-) You may want to get another disk, install clean 11.0-RELEASE and see if problem exists, then install old system (10.3?) and see if problem exist.. then compare results and find the problem source :-) I rarely upgrade between major release numbers its also good time to do some cleaning.. also none of us here seems to have problem that you describe thus it seems hardware specific or hardware driver problem :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On 19 Mar. 2017 12:46, "Bertram Scharpf" <lists@bertram-scharpf.de> wrote: > On Friday, 17. Mar 2017, 22:58:32 +0100, CeDeROM wrote: > > Bertam, are you sure you are working on a clean filesystem? Did you > > run FSCK -F / from single user as suggested?? > > Didn't help. > > Bertram > > > -- > Bertram Scharpf > Stuttgart, Deutschland/Germany > http://www.bertram-scharpf.de > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjn7SGgb-%2B%2B62%2BwXYZw9PsRf11oFOeQC4A8oz3sHG6vC1A>