Re: fdisk / disklabel issues...

2000-03-01 Thread Jason Seidel

 Hi all,
 
 I've got a problem with a couple of machines...  The first time I saw the 
 problem, I thought it was my hardware, but now I've encountered the problem 
 on three different systems, all with different motherboards, and hard 
 disks.  The only think in common, is that with all of them I'm working with 
 FreeBSD 3.4, and that all the disks are LARGER than 12Gb IDE's.

This is a commom problem.

 
 One of the things that I notice are that the size of the disk that gets 
 reported by the BIOS, and FreeBSD are totally different...  As an example, 
 the following system reports:-
 
 wdc0: unit 0 (wd0): ST313021A
 wd0: 12419MB (25434228 sectors), 25232 cyls, 16 heads, 63 S/T, 512 B/S
 
 from dmesg
 
 yet, when I get the system BIOS to probe the disk, it reports:-
 24062 cyls
 16 heads
 63 sects.
 
 As you can see, FreeBSD recognizes the disk as larger than what it actually 
 is.  I've found that if I partition the disk using the entire disk (fdisk 
 -e wd0), then the last partition on the disk (the one that uses the last 
 sectors on the disk) won't be newfs'd...
 
 It's not at all good.  sysinstall also seems to have a problem with 
 allowing you to set the geometry.  I'd expect that if I set the geometry to 
 what the BIOS detects, and then say to use the entire disk, that it would 
 use that defined geometry.  It doesn't...  The moment you say to use the 
 entire disk, ('A', No), it resets the geometry to something it likes.  If I 
 calculate the number of sectors manually (to what the bios detects), and 
 then create a slice all things work fine within that slice.

Yep.. Seen this happen

 
 I think there is something wrong with the way that FreeBSD is detecting the 
 size of the disk.  (Interigating the disk that is...)  So far I've only had 
 this problem with IDE disks.

I have had a machine that the bios picks up the drive as one thing, the
BSD probe picks it up as another, the sysinstall picks that as another.
But the one thing that was weird was that the geometry on the drive said
another size yet.  

What you want to do in the sysinstall is pick "A" like you did and choose
to use the entire disk like before. Then after that, you want to set the
geometry according to what it says on the hard drive. If you don't have
that, look it up on the web. This will keep your partition and the new
drive geometry.

Remember, FreeBSD doesn't care what the bios says  

 
 Warren
 [EMAIL PROTECTED]
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-hackers" in the body of the message
 

+++++++
Jason Seidel [Systems Administrator]  
RapidNet, INC.  USA"Oh, Bother," said Pooh as he 
[EMAIL PROTECTED]reached for the reset button. 
 
Web Support:http://www.rapidnet.com
Local Phone Support#:   (605) 341-3283 FAX #: (605) 348-1031
800 Phone Support#: 1-800-763-2525
+++



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: samba problem

1999-12-24 Thread Jason Seidel


What does your smb.conf file look like?

 
 i'm not really sure if freebsd-hackers is the right place to ask this, so
 please feel free to redirect me to the correct place.
 
 situation:  samba 2.0.6 (installed via /stand/sysinstall) on 3.4-stable
 
 smbd and nmbd start fine.  testparm doesn't report and error w/ smb.conf.
 
 when _any_ kind of access attempt is made against the server, i get the
 following error in log.smb:
 
 [1999/12/24 00:05:44, 0] smbd/oplock.c:open_oplock_ipc(93)
   open_oplock_ipc: Failed to get local UDP socket for address 17f. Error was 
Can't assign requested address
 
 
 an smbclient -L SERVERNAME  (per the samba troubleshooting docs) 
 results in the following:
 
 added interface ip=XXX.XXX.XXX.16 bcast=XXX.XXX.XXX.63 nmask=255.255.255.192
 session request to SERVERNAME failed (code 0)
 session request to *SMBSERVER failed (code 0)
 
 
 i tried removing then reinstalling samba, to no avail.
 
 i've searched the samba.org docs and mail archives and didn't find any
 relevant info.  anyone have any suggestions?
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-hackers" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message