From owner-freebsd-questions Thu Mar 23 10: 7:10 2000 Delivered-To: freebsd-questions@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7B04637C52A; Thu, 23 Mar 2000 10:06:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA02333; Thu, 23 Mar 2000 10:06:57 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 10:06:57 -0800 (PST) From: Matthew Dillon Message-Id: <200003231806.KAA02333@apollo.backplane.com> To: Eric Sabban Cc: Mike Smith , Forrest Aldrich , freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: 4.0 sysinstall fails to recognize disks References: <200003231554.HAA01743@mass.cdrom.com> <200003231750.JAA02133@apollo.backplane.com> <38DA5ADE.27FD7481@clickrebates.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :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. : :-eric I really doubt that LLing the drive fixed your problem. You probably did something else while messing around that wound up fixing it. The simple answer when someone approaches you on the street and suggests that you can fix the world by LLing your hard drive, is "NO" :-). The worst I've ever had to do to a drive to make the system recognize it is zero-out the first few sectors with dd. That way the system believes that the drive does not have a valid label and lets you install a new one trivially. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message