Re: 8.0 install fails to create filesystem ("unable to find device node")

2010-02-02 Thread Vitaly Magerya
Jeremy Chadwick wrote:
>> Yes, ad0s1b is the swap, but I think it fails before doing newfs.
>> "Writing partition information to ad0" is the last message I see before
>> the error occurs, no newfs popups occur.

By the way, in the fixit console /dev has ad0b but not ad0s1b.

> Can you get this disk into a system (or the same system if booting off
> CD, etc.) where you can do the following to it and then retry the
> installation?
> 
> dd if=/dev/zero of=/dev/ad0 bs=64k count=1
> 
> No, this isn't a joke.  This should also clear up the GEOM label
> error/warning you see.

Yay, that did the trick.

I installed 8.0 into a usb flash and cleaned ad0 from there. The setup
successfully created the filesystems and is copying files right now.

Thank you! I hope that sysinstall will be able to recognize this
situation in future releases.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: 8.0 install fails to create filesystem ("unable to find device node")

2010-02-02 Thread Jeremy Chadwick
On Tue, Feb 02, 2010 at 11:58:11PM +0200, Vitaly Magerya wrote:
> Kevin Oberman wrote:
> >> The setup tries to create filesystem and fails with this message:
> >>
> >> Unable to find device node for /dev/ad0s1b in /dev!
> > 
> > Are you doing a 'W'rite in the labeling tools? I'm guess that you are
> > not, but I wanted to be sure. You don't want to.
> 
> Nope, no write.
> 
> > You say that you are doing the default partitions. If so, the 'b'
> > partition should be swap. It should not get 'newfs'ed. No file system
> > needed (or wanted) there. This tells me that something was wrong in the
> > partition setup if it THINKS that there is a need to newfs partition
> > 'b'. 
> 
> Yes, ad0s1b is the swap, but I think it fails before doing newfs.
> "Writing partition information to ad0" is the last message I see before
> the error occurs, no newfs popups occur.
> 
> >> Aside from debug messages, there's this on second VT:
> >>
> >> GEOM: ad0: geometry does not match label (255h,63s != 16h,63s).
> > 
> > This is a known issue, but cosmetic in almost all cases.
> 
> OK, good.
> 
> > I suspect that you are doing something wrong, but it's hard to figure
> > out just what it might be.
> 
> Anything I can do to see what's the problem?

Can you get this disk into a system (or the same system if booting off
CD, etc.) where you can do the following to it and then retry the
installation?

dd if=/dev/zero of=/dev/ad0 bs=64k count=1

No, this isn't a joke.  This should also clear up the GEOM label
error/warning you see.

-- 
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: 8.0 install fails to create filesystem ("unable to find device node")

2010-02-02 Thread Vitaly Magerya
Kevin Oberman wrote:
>> The setup tries to create filesystem and fails with this message:
>>
>> Unable to find device node for /dev/ad0s1b in /dev!
> 
> Are you doing a 'W'rite in the labeling tools? I'm guess that you are
> not, but I wanted to be sure. You don't want to.

Nope, no write.

> You say that you are doing the default partitions. If so, the 'b'
> partition should be swap. It should not get 'newfs'ed. No file system
> needed (or wanted) there. This tells me that something was wrong in the
> partition setup if it THINKS that there is a need to newfs partition
> 'b'. 

Yes, ad0s1b is the swap, but I think it fails before doing newfs.
"Writing partition information to ad0" is the last message I see before
the error occurs, no newfs popups occur.

>> Aside from debug messages, there's this on second VT:
>>
>> GEOM: ad0: geometry does not match label (255h,63s != 16h,63s).
> 
> This is a known issue, but cosmetic in almost all cases.

OK, good.

> I suspect that you are doing something wrong, but it's hard to figure
> out just what it might be.

Anything I can do to see what's the problem?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: 8.0 install fails to create filesystem ("unable to find device node")

2010-02-02 Thread Kevin Oberman
> Date: Tue, 02 Feb 2010 21:29:26 +0200
> From: Vitaly Magerya 
> Sender: owner-freebsd-sta...@freebsd.org
> 
> Greetings everyone. I'm trying to install FreeBSD 8.0 from Disk1 on
> ThinkPad T40, so far unsuccessfully.
> 
> Here are the setup steps:
> Installer complains that "77520/16/63" may not be a good geometry for
> ad0, proposes "4864/255/63" instead (both eventually lead to failure).
> I create a single disk-wide slice (ad0s1), choose a boot manager, set up
> standard labeling for ad0s1, choose distributions.
> 
> The setup tries to create filesystem and fails with this message:
> 
> Unable to find device node for /dev/ad0s1b in /dev!

Are you doing a 'W'rite in the labeling tools? I'm guess that you are
not, but I wanted to be sure. You don't want to.

You say that you are doing the default partitions. If so, the 'b'
partition should be swap. It should not get 'newfs'ed. No file system
needed (or wanted) there. This tells me that something was wrong in the
partition setup if it THINKS that there is a need to newfs partition
'b'. 

> Aside from debug messages, there's this on second VT:
> 
> GEOM: ad0: geometry does not match label (255h,63s != 16h,63s).

This is a known issue, but cosmetic in almost all cases.

I suspect that you are doing something wrong, but it's hard to figure
out just what it might be.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net  Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


8.0 install fails to create filesystem ("unable to find device node")

2010-02-02 Thread Vitaly Magerya
Greetings everyone. I'm trying to install FreeBSD 8.0 from Disk1 on
ThinkPad T40, so far unsuccessfully.

Here are the setup steps:
Installer complains that "77520/16/63" may not be a good geometry for
ad0, proposes "4864/255/63" instead (both eventually lead to failure).
I create a single disk-wide slice (ad0s1), choose a boot manager, set up
standard labeling for ad0s1, choose distributions.
The setup tries to create filesystem and fails with this message:

Unable to find device node for /dev/ad0s1b in /dev!

Aside from debug messages, there's this on second VT:

GEOM: ad0: geometry does not match label (255h,63s != 16h,63s).

I also tried to setup 7.0 (w/o dangerously dedicated slicing), and then
freebsd-update to 8.0. On first reboot required by freebsd-update the
system drops to bootloader prompt and fails to find init on any of the
filesystems.

Help. Is there anything I can do to install 8.0?

The dmesg of this machine (as seen by 7.0) is at [1]. I'll provide any
further information -- just name it.

[1] http://tx97.net/~magv/dmesg-t40.70.txt
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"