Ruben de Groot
2012-Jun-15 17:10 UTC
kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
Hi,
After over 3 years of uptime, I decided to upgrade one of my SUN boxes to
9-stable. However the new kernel didn't boot because of geom integrity check
issues. This I understand as I remember I had to use some weird tricks in the
past to get the entire disks used in the first place.
Anyway, I felt lucky this was a known and documented problem, with a workaround:
http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#AEN1277
However, the workaround doesn't seem to work :-(
Type '?' for a list of commands, 'help' for more detailed help.
OK set kern.geom.part.check_integrity="0"
OK boot
jumping to kernel entry at 0xc0070000.
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012
root@morninglightmountain.hacktor.net:/usr/obj/usr/src/sys/MORNINGLIGHTMOUNTAIN
sparc64
real memory = 536870912 (512 MB)
avail memory = 503963648 (480 MB)
cpu0: Sun Microsystems UltraSparc-IIe Processor (400.00 MHz CPU)
ctl: CAM Target Layer loaded
nexus0: <Open Firmware Nexus device>
pcib0: <U2P UPA-PCI bridge> mem
0x1fe00000000-0x1fe0000ffff,0x1fe01000000-0x1fe010000ff irq 2032,2030,2031,2021
on nexus0
pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 66MHz
pcib0: DVMA map: 0x60000000 to 0x63ffffff 8192 entries
pcib0: [GIANT-LOCKED]
pci0: <OFW PCI bus> on pcib0
pci0: <bridge, PCI-ISA> at device 7.0 (no driver attached)
pci0: <old, non-VGA display device> at device 3.0 (no driver attached)
dc0: <Davicom DM9102A 10/100BaseTX> port 0x10000-0x100ff mem 0-0xff at
device 12.0 on pci0
miibus0: <MII bus> on dc0
amphy0: <DM9102 10/100 media interface> PHY 1 on miibus0
amphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: Ethernet address: 00:03:ba:05:fa:5c
dc1: <Davicom DM9102A 10/100BaseTX> port 0x10100-0x101ff mem 0x2000-0x20ff
at device 5.0 on pci0
miibus1: <MII bus> on dc1
amphy1: <DM9102 10/100 media interface> PHY 1 on miibus1
amphy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc1: Ethernet address: 00:03:ba:05:fa:5c
pci0: <serial bus, USB> at device 10.0 (no driver attached)
atapci0: <AcerLabs M5229 UDMA66 controller> port
0x10200-0x10207,0x10218-0x1021b,0x10210-0x10217,0x10208-0x1020b,0x10220-0x1022f
at device 13.0 on pci0
atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug,
expect reduced performance
ata2: <ATA channel> at channel 0 on atapci0
ata3: <ATA channel> at channel 1 on atapci0
nexus0: <syscons> type unknown (no driver attached)
Timecounter "tick" frequency 400000000 Hz quality 1000
Event timer "tick" frequency 400000000 Hz quality 1000
Timecounters tick every 1.000 msec
ada0 at ata2 bus 0 scbus0 target 0 lun 0
ada0: <MAXTOR STM3160215A 3.AAD> ATA-7 device
ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes)
ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad0
ada1 at ata3 bus 0 scbus1 target 0 lun 0
ada1: <MAXTOR STM3160215A 3.AAD> ATA-7 device
ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes)
ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad1
GEOM: ada0: adding VTOC8 information.
GEOM_PART: integrity check failed (ada0, VTOC8)
this is where it hangs, just like without setting
kern.geom.part.check_integrity.
Is this a regression?
--
cheers,
Ruben de Groot
Ruben de Groot
2012-Jun-20 15:15 UTC
kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
I'm resending this email as I got no response the first time.
After over 3 years of uptime, I decided to upgrade one of my SUN boxes to
9-stable. However the new kernel didn't boot because of geom integrity check
issues. This I understand as I remember I had to use some weird tricks in the
past to get the entire disks used in the first place.
Anyway, I felt lucky this was a known and documented problem, with a workaround:
http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#AEN1277
However, the workaround doesn't seem to work :-(
Type '?' for a list of commands, 'help' for more detailed help.
OK set kern.geom.part.check_integrity="0"
OK boot
jumping to kernel entry at 0xc0070000.
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012
<SNIP>
Timecounters tick every 1.000 msec
ada0 at ata2 bus 0 scbus0 target 0 lun 0
ada0: <MAXTOR STM3160215A 3.AAD> ATA-7 device
ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes)
ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad0
ada1 at ata3 bus 0 scbus1 target 0 lun 0
ada1: <MAXTOR STM3160215A 3.AAD> ATA-7 device
ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes)
ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad1
GEOM: ada0: adding VTOC8 information.
GEOM_PART: integrity check failed (ada0, VTOC8)
this is where it hangs, just like without setting
kern.geom.part.check_integrity.
Is this a regression?
--
cheers,
Ruben de Groot
_______________________________________________
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"
Andrey V. Elsukov
2012-Jun-20 16:35 UTC
kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
On 20.06.2012 19:14, Ruben de Groot wrote:> Timecounters tick every 1.000 msec > ada0 at ata2 bus 0 scbus0 target 0 lun 0 > ada0: <MAXTOR STM3160215A 3.AAD> ATA-7 device > ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) > ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad0 > ada1 at ata3 bus 0 scbus1 target 0 lun 0 > ada1: <MAXTOR STM3160215A 3.AAD> ATA-7 device > ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) > ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) > ada1: Previously was known as ad1 > GEOM: ada0: adding VTOC8 information. > GEOM_PART: integrity check failed (ada0, VTOC8) > > this is where it hangs, just like without setting kern.geom.part.check_integrity. > > Is this a regression?Can you enable verbose boot mode and show what you will get? -- WBR, Andrey V. Elsukov -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20120620/21e4eadb/signature.pgp