Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-18 Thread Deian Popov
No strange IDE settings, it has been that way for years.

Regards,

Deian

On Feb 18, 2008 12:12 AM, Brian A. Seklecki (Mobile) <
[EMAIL PROTECTED]> wrote:

>
> On Sun, 2008-02-17 at 23:45 +0200, Deian Popov wrote:
> > I will most definitely do, but this would happen after few days (don't
> > have time to fix the system before that). The output of 6.3 and 7 is
> > the same, so I will provide one from 6.3. Should I use
> > http://www.freebsd.org/send-pr.html to file the report ?
> >
>
> Be sure to include the output of:
>
> $ sudo pciconf -lv
>
> You checked your BIOS for strange IDE settings, rights?
>
> ~BAS
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-17 Thread Brian A. Seklecki (Mobile)

On Sun, 2008-02-17 at 23:45 +0200, Deian Popov wrote:
> I will most definitely do, but this would happen after few days (don't
> have time to fix the system before that). The output of 6.3 and 7 is
> the same, so I will provide one from 6.3. Should I use
> http://www.freebsd.org/send-pr.html to file the report ?
> 

Be sure to include the output of:

$ sudo pciconf -lv

You checked your BIOS for strange IDE settings, rights?

~BAS

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-17 Thread Deian Popov
I will most definitely do, but this would happen after few days (don't have
time to fix the system before that). The output of 6.3 and 7 is the same, so
I will provide one from 6.3. Should I use
http://www.freebsd.org/send-pr.html to file the report ?

On Feb 17, 2008 11:09 PM, Brian A. Seklecki (Mobile) <
[EMAIL PROTECTED]> wrote:

>
> On Sun, 2008-02-17 at 22:53 +0200, Deian Popov wrote:
> > I have tested numerous times both 6.3 and
> > 7 and the ata driver would not detect my hdd. Here is output of dmesg
> > on 6.2system:
>
> File a bug for sure!
>
> Here are the relevant lines from the working 6.2 system:
>
>  atapci0:  port
>  0x1f0-0x1f7,0x3f6,0x170-0x177,0x37
>  6,0xf000-0xf00f irq 18 at device 31.2 on pci0*
>  ata0:  on atapci0
>  ata1:  on atapci0*
>
> *ad1: 76319MB  at ata0-slave SATA150*
> Trying to mount root from ufs:/dev/ad1s1a
>
> Can you boot a 6.3/7.x kernel and either FTP the /var/run/dmesg
> somewhere or boot w/ serial console?  Either that or screenshot using
> camera-phone, works too.
>
> ~BAS
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-17 Thread Brian A. Seklecki (Mobile)

On Sun, 2008-02-17 at 22:53 +0200, Deian Popov wrote:
> I have tested numerous times both 6.3 and
> 7 and the ata driver would not detect my hdd. Here is output of dmesg
> on 6.2system:

File a bug for sure!

Here are the relevant lines from the working 6.2 system:

 atapci0:  port
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x37
 6,0xf000-0xf00f irq 18 at device 31.2 on pci0*
 ata0:  on atapci0
 ata1:  on atapci0*

*ad1: 76319MB  at ata0-slave SATA150*
Trying to mount root from ufs:/dev/ad1s1a

Can you boot a 6.3/7.x kernel and either FTP the /var/run/dmesg
somewhere or boot w/ serial console?  Either that or screenshot using
camera-phone, works too.

~BAS

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-17 Thread Deian Popov
During my struggle to get my machine up and running without loosing
files/settings I made the stupid mistake to rebuild kernel twice without
rebooting, which completely made my system unbootable, and couldn't go to
loader prompt to boot kernel.old. I have tested numerous times both 6.3 and
7 and the ata driver would not detect my hdd. Here is output of dmesg
on 6.2system:

FreeBSDGW# dmesg
Copyright (c) 1992-2007 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 6.2-RELEASE-p11 #0: Sun Feb 17 01:02:10 EET 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (2996.81-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9

Features=0xbfebfbff
  Features2=0x4400>
  Logical CPUs per core: 2
real memory  = 1073676288 (1023 MB)
avail memory = 1041674240 (993 MB)
ioapic0: Changing APIC ID to 2
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
acpi_button0:  on acpi0
acpi_button1:  on acpi0
pcib0:  port 0xcf8-0xcff,0x1000-0x10bf on acpi0
pci0:  on pcib0
agp0:  mem 0xe000-0xe7ff at device
0.0o
n pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
uhci0:  port 0xbc00-0xbc1f irq 16
at
device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xb000-0xb01f irq 19
at
device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xb400-0xb41f irq 18
at
device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3:  port 0xb800-0xb81f irq 16
at
device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3:  on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0:  mem 0xf410-0xf41003ff
irq
23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4:  on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib2:  at device 30.0 on pci0
pci2:  on pcib2
rl0:  port 0xa000-0xa0ff mem
0xf310-0xf31000ff
ir
q 22 at device 2.0 on pci2
miibus0:  on rl0
rlphy0:  on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:02:44:6b:53:39
fxp0:  port 0xa400-0xa41f mem
0xf400-0xf4000ff
f,0xf300-0xf30f irq 16 at device 3.0 on pci2
miibus1:  on fxp0
inphy0:  on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:08:c7:b3:4e:00
pci2:  at device 4.0 (no driver attached)
fxp1:  port 0xa800-0xa83f mem
0xf31020
00-0xf3102fff irq 20 at device 8.0 on pci2
miibus2:  on fxp1
inphy1:  on miibus2
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:0d:61:1a:f0:2e
isab0:  at device 31.0 on pci0
isa0:  on isab0
*atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x37
6,0xf000-0xf00f irq 18 at device 31.2 on pci0*
*ata0:  on atapci0
ata1:  on atapci0*
pci0:  at device 31.3 (no driver attached)
pci0:  at device 31.5 (no driver attached)
fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0:  port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
pmtimer0 on isa0
orm0:  at iomem 0xd-0xd07ff on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 2996811260 Hz quality 800
Timecounters tick every 1.000 msec
*ad1: 76319MB  at ata0-slave SATA150*
Trying to mount root from ufs:/dev/ad1s1a


On Feb 16, 2008 3:21 AM, Brian A. Seklecki <
[EMAIL PROTECTED]> wrote:

>
> On Fri, 2008-02-15 at 16:03 -0600, Derek Ragona wrote:
> > >the prompt has "?" command which shows available boot devices. The
> > only
> > >device present t

Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-15 Thread Brian A. Seklecki

On Fri, 2008-02-15 at 16:03 -0600, Derek Ragona wrote:
> >the prompt has "?" command which shows available boot devices. The
> only
> >device present there is my floppy (fd0)

Your new kernel is hosed.  Its not probing the mass storage device of
your root disk.  

Show us your original dmesg(8), your new dmesg(8), and original
fstab(5).


-- 
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.




IMPORTANT: This message contains confidential information and is intended only 
for the individual named. If the reader of this message is not an intended 
recipient (or the individual responsible for the delivery of this message to an 
intended recipient), please be advised that any re-use, dissemination, 
distribution or copying of this message is prohibited. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-15 Thread Derek Ragona

At 03:02 PM 2/15/2008, Deian Popov wrote:

Hello,

I'm pretty stuck with the death of my bsd machine after attempt on upgrade
from 6.2 to 6.3. Some time ago, I successfully upgraded from 6.1 to
6.2following the steps in the manual

1) cvsup source to specific release
2) buildworld
3) buildkernel
4) installkernel
5) boot
6) mergemaster -p
7) installworld
8) mergemaster
9) boot

Now, after completing steps 1 to 5 the system won't boot and stucks at the
following prompt

bsd: Trying to mount root from ufs:/dev/ad1s1a
bsd: mountroot>

the prompt has "?" command which shows available boot devices. The only
device present there is my floppy (fd0)

I can choose to boot to loader prompt but have no idea how to recorver, and
more interesting, to figure out why that failure occurred?

Any help is appreciated.


In some 6.x versions the upgrade can go south.  I had this happen on one 
server, and this is how I fixed it:


I downloaded and burned the release iso.  I booted the system from CD, then 
in sysinstall, I used the emergency shell.  In the emergency shell I 
mounted my drives and had a peek.  In my case I saw there was no 
kernel.  So I copied the kernel from the cd to my root / drive.  After that 
I could reboot from the hard drive, and finished my upgrade.


Hope this helps.

-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: freebsd dead after attempt on upgrade from 6.2 to 6.3

2008-02-15 Thread Kris Kennaway

Deian Popov wrote:

Hello,

I'm pretty stuck with the death of my bsd machine after attempt on upgrade
from 6.2 to 6.3. Some time ago, I successfully upgraded from 6.1 to
6.2following the steps in the manual

1) cvsup source to specific release
2) buildworld
3) buildkernel
4) installkernel
5) boot
6) mergemaster -p
7) installworld
8) mergemaster
9) boot

Now, after completing steps 1 to 5 the system won't boot and stucks at the
following prompt

bsd: Trying to mount root from ufs:/dev/ad1s1a
bsd: mountroot>

the prompt has "?" command which shows available boot devices. The only
device present there is my floppy (fd0)

I can choose to boot to loader prompt but have no idea how to recorver, and
more interesting, to figure out why that failure occurred?


Check the kernel boot messages to see why your ad1 did not get probed. 
Did the ata driver report an error?  Did it attach the drive under a 
different device number?


Kris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"