Bug 141060

Summary: [install] Can't install 8.0-RELEASE on the server where 7.2 works fine [regression]
Product: Base System Reporter: Konstantin Belov <kostya>
Component: amd64Assignee: freebsd-amd64 (Nobody) <amd64>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Konstantin Belov 2009-12-01 17:30:01 UTC
Can not install 8.0-RELEASE on the server where 7.2 were installed successfully. After creating fdisk slices and FSs the installator tries to do newfs and says "Can not find device node /dev/aacd0s1a" (but it just was created). Tried to install not on the ARRAY, but on SATA HDD attached directrly to motherboard controller, but had the same message.
Configuration: M/B Supermicro X7DBE-X, Intel X5410, Adaptec 2820SA (PCI-X).

Next:
Tried to upgrade successfully installed 7.2 to 8.0. After rebooting with new kernel it can not find root FS and I can not find it too in the list of possible mount devices (i.e. no aacd0s1a, just aacd0a). But entering to the loader prompt and making lsdev shows all FSs and SWAP on the disk where it was created (disk D).

Fix: 

Could not do anything. Finally leave 7.2 version on the server. Hope I'm not alone with such a trouble and you will find the problem and make a fix.
How-To-Repeat: Try to install on the specefied configuration.
Comment 1 Mike Duchene 2010-01-08 05:32:47 UTC
If 7.2 was installed on a "dangerously dedicated" drive, then the 8.0
sysinstall bsdlabel does not automatically recreate a standard MBR on the
disk.  You can try to fix this by starting a fixit shell from sysinstall and
issuing the command:
  dd if=/dev/zero of=/dev/ad1 bs=512 count=1025
where ad1 is the dangerously dedicated device.

This corrected the issue for me.  Also, you can read more about this from
the mailing list archives:
http://lists.freebsd.org/pipermail/freebsd-questions/2009-December/208759.ht
ml

Thank You,
Mike Duchene
Comment 2 Andriy Gapon freebsd_committer freebsd_triage 2010-12-05 13:08:57 UTC
Is this still a problem?
Have you tried to follow the suggestion?

-- 
Andriy Gapon
Comment 3 Jaakko Heinonen freebsd_committer freebsd_triage 2011-09-24 08:44:43 UTC
State Changed
From-To: open->feedback

Note that submitter has been asked for feedback.
Comment 4 Jaakko Heinonen freebsd_committer freebsd_triage 2011-11-11 19:14:07 UTC
State Changed
From-To: feedback->closed

Feedback timeout.