From owner-freebsd-current Thu Mar 23 10: 2:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg-20425418-10.ricochet.net [204.254.18.10]) by hub.freebsd.org (Postfix) with ESMTP id 29BD137B60C; Thu, 23 Mar 2000 10:02:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01112; Thu, 23 Mar 2000 10:04:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003231804.KAA01112@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Eric Sabban Cc: Matthew Dillon , Mike Smith , Forrest Aldrich , freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: 4.0 sysinstall fails to recognize disks In-reply-to: Your message of "Thu, 23 Mar 2000 09:56:46 PST." <38DA5ADE.27FD7481@clickrebates.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 10:04:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I say again, DO NOT low-level format the drive. The _only_ situation where it's worth taking this risk is when you're seeing errors from the drive itself specifically referring to formatting issues; eg. 'address mark not found'. There are no other circumstances which justify this action, and a great deal of harm can come from it. > I normally wouldn't recommend it. But the same situation with a different (not to be mentioned) OS happened to me. > After hours of being frustrated, I decided the scsi controller went south. A cow-orker told me to LL the drive, > and voila, magic. These were IBM LVD 10kRPM drives, brand spankin new. I'd recommend updating sysinstall first, if > that doesn't work, LL the drives. Wrong solution. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message