Date: Sun, 26 Feb 2012 23:53:59 +0100 From: Damien Fleuriot <ml@my.gd> To: Erich Dollansky <erichfreebsdlist@ovitrap.com> Cc: Scott Bennett <bennett@cs.niu.edu>, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: random problem with 8.3 from yesterday Message-ID: <B934538A-767C-40E8-9319-579A79F17097@my.gd> In-Reply-To: <201202261106.19487.erichfreebsdlist@ovitrap.com> References: <201202251717.q1PHHeXD024464@mp.cs.niu.edu> <CAN6yY1u-nctGz0pq7fkw9qQiF2myh_aVT3GkKDCESEDSNsB4XQ@mail.gmail.com> <201202261106.19487.erichfreebsdlist@ovitrap.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 Feb 2012, at 05:06, Erich Dollansky <erichfreebsdlist@ovitrap.com> wrote: > Hi, > > On Sunday 26 February 2012 00:55:46 Kevin Oberman wrote: > >> I thought he was creating a "monolithic" device...what was called >> "dangerously dedicated". No slices at all. Not only are DD volumes > > yes, I remember this term. And Windows machines get confused but they do not damage the media. > >> mountable, they are bootable. It's been years since I created a DD >> disk as the slight space savings are irrelevant on modern hundreds of >> gigabyte disks, so I may have forgotten how it works. It might still >> make sense on a small thumb drive, bootable or not. > > Never break a winning team. The script doing the job works since a long time. This is the simple reason behind. > Ok so since nobody mentioned it, does the problem happen for ALL your media handled in the same fashion, or just the one drive ? What I'm saying is don't blame the software so readily when it might be hardware. Get a SMART report on your disk. Also try with another media.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B934538A-767C-40E8-9319-579A79F17097>