Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Jan 2009 09:43:09 -0700 (MST)
From:      jjr@larush.com
To:        "Mike Barnard" <mike.barnardq@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
Message-ID:  <de6f3877c282d2e08b23b16fea8fa5f9.squirrel@www.larush.com>
In-Reply-To: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com>
References:  <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Mike,

I ran into this very issue on a Mac Pro that I installed 7.1-RELEASE on
and then cvsup'd, make buildworld to 7.1-STABLE.  On my machine,
7.1-RELEASE named the drives ad8, ad9, and ad10 (I have 3 drives and
installed 7.1-RELEASE on ad9).  When I booted the STABLE keneral (GENERIC
no tweaks), this kernel named the drives ad6, ad7, and ad8 and I was
dropped into this "Manual root filesystem" prompt.  ? did not list any
drives however, I entered ufs:ad7s1a and booted the kernel when I
recognized that the drive had been re-named from ad9 to ad7.  After
booting, I changed /etc/fstab appropiately and have had no further
problems.  I've never run into this with previous upgrades, very odd.

regards
John

> Hi All,
>
> I have run into a problem that seem rather puzzling. I have upgraded an
> installation of FreeBSD from 7.0-RELEASE to 7.0-STABLE and 7.1-STABLE, but
> i
> fail to boot with either one of the STABLE upgrades. I end up at this
> point:
>
>
> Trying to mount root from ufs:/dev/ad0s1a
> Manual root filesystem specification:
> <fstype>:<device> Mount <device> using filesystem <fstype>
> eg. ufs:da0s1a
> ? List valid disk boot devices
> <empty line> Abort manual input
>
> When i type ?, i get nothing. When i try to load all possible drives, from
> ad0s1a to ad9s1a, i get nothing. When i boot kernel.old, i see this:
>
> atapci0: <Intel ICH7 SATA300 controller> port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem
> 0xfdffe000-0xfdffe3ff
> at device 31.2 on pci0
> ...
> ad0: 152627MB <WDC WD1600AAJS-60PSA0 21.12M21> at ata0-master SATA150
>
> It seems that FreeBSD recognises this drive as a SATA300 but later on
> refers
> to it as SATA150. Could this be the problem.
>
> This is what i have about this disk when i boot the RELEASE version of
> FreeBSD:
>
> #pciconf -lv
> atapci0@pci0:0:31:2:    class=0x01018a card=0x73361462 chip=0x27c08086
> rev=0x01 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage
> Controller'
>     class      = mass storage
>     subclass   = ATA
>
> #atacontrol cap ad0
>
> Protocol              Serial ATA II
> device model          WDC WD1600AAJS-60PSA0
> serial number         WD-WMAP96717073
> firmware revision     21.12M21
> cylinders             16383
> heads                 16
> sectors/track         63
> lba supported         268435455 sectors
> lba48 supported       312581808 sectors
> dma supported
> overlap not supported
>
> Feature                      Support  Enable    Value           Vendor
> write cache                    yes      yes
> read ahead                     yes      yes
> Native Command Queuing (NCQ)   yes       -      31/0x1F
> Tagged Command Queuing (TCQ)   no       no      31/0x1F
> SMART                          yes      yes
> microcode download             yes      yes
> security                       yes      no
> power management               yes      yes
> advanced power management      no       no      0/0x00
> automatic acoustic management  no       no      0/0x00  0/0x00
>
> # atacontrol mode ad0
> current mode = SATA150
>
>
> When i boot in verbose mode, i get this:
>
> atapci0: <Intel ICH7 SATA300 controller> port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem
> 0xfdffe000-0xfdffe3ff
> at device 31.2 on pci0
> atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfa00
> pci0: child atapci0 requested type 4 for rid 0x24, but the BAR says it is
> an
> memio
> ata0: <ATA channel 0> on atapci0
> atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
> atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
> ata0: reset tp1 mask=03 ostat0=50 ostat1=00
> ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00
> ata0: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
> ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54
> ata0: [MPSAFE]
> ata0: [ITHREAD]
> ata1: <ATA channel 1> on atapci0
> atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170
> atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376
> ata1: reset tp1 mask=03 ostat0=00 ostat1=00
> ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: reset tp2 stat0=00 stat1=00 devices=0xc<ATAPI_SLAVE,ATAPI_MASTER>
> ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55
> ata1: [MPSAFE]
> ata1: [ITHREAD]
> ...
> ...
> ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire
> ad0: 152627MB <WDC WD1600AAJS-60PSA0 21.12M21> at ata0-master SATA150
> ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth
> queue
> GEOM: new disk ad0
> ad0: Intel check1 failed
> ad0: Adaptec check1 failed
> ad0: LSI (v3) check1 failed
> ad0: LSI (v2) check1 failed
> ad0: FreeBSD check1 failed
> ata1: reiniting channel ..
> ata1: reset tp1 mask=03 ostat0=00 ostat1=00
> ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: reset tp2 stat0=00 stat1=00 devices=0xc<ATAPI_SLAVE,ATAPI_MASTER>
> ata1: reinit done ..
> ata1: reiniting channel ..
> ata1: reset tp1 mask=03 ostat0=00 ostat1=00
> ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: reset tp2 stat0=00 stat1=00 devices=0xc<ATAPI_SLAVE,ATAPI_MASTER>
> ata1: reinit done ..
> ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire
>
>
> Any one with any ideas?
>
>
> --
> Mike
>
> Of course, you might discount this possibility, but remember that one in
> a million chances happen 99% of the time.
> ------------------------------------------------------------
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de6f3877c282d2e08b23b16fea8fa5f9.squirrel>