Re: new openbsd 4.0 server, panic on ufsdirhash
--- John Mendenhall [EMAIL PROTECTED] wrote: The comp set isn't required to RUN OpenBSD. Install the minimal (kernel, base, etc) and I think that will get the system running. Then you can alter the booting mechanism (verbose) and make tweaks before loading comp. OK. I have installed the bare sets to get it working. It is up and running now. I rebooted and was able to access the UKC and requested verbose boot. The verbose boot log is at the bottom of the message. I'm hitting Google with your pciide0 string and for the 2 minutes of searching, all I see are various people having problems. Maybe because people won't complain or give this kind of information normally if things are working well. I'll continue to search... could you/would you install the minimal and work from there? Maybe it's corrupt on the source! CD pressed/burned badly. Older OpenBSD release working? I have not tried any other os installation. I have earlier versions which I could try, if we want to check that. That would not be a problem. JohnM - dmesg w/verbose snip! OK, now I'm clueless why this happens. I didn't see in your verbose dmesg at all any obvious PCI busses or devices. Yet the normal dmesg lists your PCI devices. I could be reading the devices wrong, but I read in your verbose dmesg that it found: 1: Audio 2: Realtek Ethernet (probably a PCI device??) 3: isa0 bus 4: Keyboard/mouse ports (which I really think they are attached on the ISA bus, internally on the motherboard) 5: speaker (again, same as #4, on the ISA bus in the motherboard) 6: parallel (ditto) 7: npx0 (I think this is your coprocessor, and I don't know what bus it is on) 8: COM/Serial ports (ditto as #4) 9: Floppy drive (I would think this is on the ISA bus, but I am not sure) Aside from #2, the realtek ethernet, I am not seeing any signs of PCI detection. But how can it boot off the drive, which is on pciide0 (from original, normal dmesg in digest #783). That device sure looks like it's on the PCI bus. I'm lost on this one, I totally expected to see anything, SOMETHING about the pci bus (wouldn't it be pci0?). John did state he has another version, and if *THIS* thing fails horribly bad on trying to get more information, I would try the other version. I'm not sure if the 4.1-RELEASE (at least the sparc32 one) was done correctly, I have a simple 64MB sparcstation5 that after I came home from work one day, the box was at the 4th prompt (for ya i386 folks, that's similar to the BIOS/SETUP program). A day or two later the same box, same config, same everything was waiting on a ddb prompt with what seemed to be a runaway application (smbd, ddb's ps command just kept endlessly returning smbd as processes running on the box). The only change to this box was an addon SBUS 4-port ethernet board. Anyway, I got sidetracked in the basic statement that there may be something wrong with the comp41.tgz set? bad press? bad release process on OpenBSD? I can't pin it down, but I didn't have *ANY* problem with 4.0, in any of it's platforms. The above paragraph may start flaming, and I want to defuse it right now. The problem I have above may not at all be related to John's original problem, but I've also seen other people having trouble installing 4.1 on this mailing list and wonder if it has something related/linked that we can use. Heck, my 4.1 i386 CD I burned locks up my keyboard/kvm so bad that I have to push the buttons on the front to reboot. It gets to the install, upgrade, shell and then locks up. John, please try 4.0 and then doing a source upgrade to 4.1, if this verbose dmesg doesn't help anybody. Sorry for bringing it up :( Good luck. If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill.
Re: new openbsd 4.0 server, panic on ufsdirhash
--- John Mendenhall [EMAIL PROTECTED] wrote: OK, now I'm clueless why this happens. I didn't see in your verbose dmesg at all any obvious PCI busses or devices. Yet the normal dmesg lists your PCI devices. I could be reading the devices wrong, but I read in your verbose dmesg that it found: 1: Audio 2: Realtek Ethernet (probably a PCI device??) 3: isa0 bus 4: Keyboard/mouse ports (which I really think they are attached on the ISA bus, internally on the motherboard) 5: speaker (again, same as #4, on the ISA bus in the motherboard) 6: parallel (ditto) 7: npx0 (I think this is your coprocessor, and I don't know what bus it is on) 8: COM/Serial ports (ditto as #4) 9: Floppy drive (I would think this is on the ISA bus, but I am not sure) Aside from #2, the realtek ethernet, I am not seeing any signs of PCI detection. But how can it boot off the drive, which is on pciide0 (from original, normal dmesg in digest #783). That device sure looks like it's on the PCI bus. I'm lost on this one, I totally expected to see anything, SOMETHING about the pci bus (wouldn't it be pci0?). I have no idea why that is happening. Strange. John did state he has another version, and if *THIS* thing fails horribly bad on trying to get more information, I would try the other version. ... John, please try 4.0 and then doing a source upgrade to 4.1, if this verbose dmesg doesn't help anybody. Sorry for bringing it up :( This is the 4.0 release. I usually run a release behind. And, I have not ordered a 4.1 yet. I will in the next week or two. I do have v3.9 and earlier releases available. Whatever you have onhand that you know has worked in the past. 3.9 isn't supported anymore, but using 3.9 to update to 4.0 or 4.1 would probably work as documented by the fabulous documentation! Let us know! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: new openbsd 4.0 server, panic on ufsdirhash
--- John Mendenhall [EMAIL PROTECTED] wrote: On Wed, May 16, 2007 at 09:30:44AM -0700, John Mendenhall wrote: If anyone knows of a tool I can use to determine the ATA controller, or any other hw things I need to find out, please post any pointers. dmesg(8) Well, I posted the dmesg at the beginning of this thread. Here is an excerpt with the ide/ata hardware: - pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: IC35L120AVV207-0 wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide0 channel 1 drive 0: WDC WD1200JB-00DUA3 wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors - There may be more. Please let me know if I need to repost it. Anyone know how to boot with more messages? man boot doesn't show any verbose options. Use UKC (boot -c), and the verbose command. See boot_config(8). Is this supported when booting from cd? I can only boot from the cd right now. Once it starts copying data, it crashes in the comp set. The comp set isn't required to RUN OpenBSD. Install the minimal (kernel, base, etc) and I think that will get the system running. Then you can alter the booting mechanism (verbose) and make tweaks before loading comp. I'm hitting Google with your pciide0 string and for the 2 minutes of searching, all I see are various people having problems. Maybe because people won't complain or give this kind of information normally if things are working well. I'll continue to search... could you/would you install the minimal and work from there? Maybe it's corrupt on the source! CD pressed/burned badly. Older OpenBSD release working? couple of things to try... i'll look when I get a second or two. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz
Re: new openbsd 4.0 server, panic on ufsdirhash
I (still) receive the digest, copied message without quoting characters - QUOTE: We have done a low level disk format using an ultimate boot cd. Didn't output any errors. Did this on both drives in the system. Took a very long time. Then, tried to install the OS. Received a panic on installing the comp set, ffs_valloc dup alloc. Reconfigured to have all install go to one drive. Same error, different inode. Tried all on other drive, same error, different inode. Kept trying it over and over. Always panicked on comp set. Always same error of ffs_valloc dup alloc. Always a different inode. I am unable to copy in the actual error. I just have this on a monitor in the room. No console capability. Same dmesg as before in this thread. I can post again if needed. My question is, to debug this, or fix it, do I need to start swapping out cables, hard disks, motherboard, etc? Any hints or suggestions are appreciated. Thanks in advance! JohnM /QUOTE John, since you were able to boot the ultimate boot cd and run both drives completely, I don't think any hardware is the culprit. Your CD drive, Hard Drive(s), memory, etc all work under that OS. My mindset is now leading to some bug that OpenBSD is doing (probably) with the ATA controller. Probe from the ultimate boot cd to see what ATA controller it is using, and then find what OpenBSD is finding the ATA controller to be. A minor model difference could be the culprit (model 1234 versus model 1234a, for example). Bug may not be the right word, but it's what's coming to mind. Not to steer away from OpenBSD, but if the three big BSDs all have trouble, we might be able to limit what might be the problem. FreeBSD operating system runs on a live CD either with their disc1 (install disk, look for the fixit option and then select CD/DVD) start running things like dd and etc to run data on the drive. Nothing valuable there now anyway, is there? Maybe using a *rand device under /dev NetBSD doesn't have (AFAIK) a live-cd, but i'm pretty sure you can escape to shell from their installer. Run similar/same tools. get dmesg from both Free and Net while you're on it. save it to external medium (usb stick, floppy). Compare the findings to OpenBSD's dmesg. Basically, it boils down to the fact that one OS ran for several hours with CONSTANT hdd activity with no errors. I think it's a software problem, including drivers into the software category. Thanks! If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/
Re: new openbsd 4.0 server, panic on ufsdirhash
Linux OS'en (IIRC) use lspci like what pciconf is for FreeBSD. I don't know if Open would have any of those tools built in. I don't have a ready openbsd box right now. Google search for thunderboot ultimate boot cd doesn't reveal anything. it suggested a spelling correction, for thunderboom, which didn't easily reveal any bootable cd. A link to the ISO and I'd offer what I can for diagnostics and probing solutions. Is there a way to get the kernel to more verbosely announce what it's probing and configuring, like what FreeBSD's boot loader's -v option will do? Haven't tried, haven't looked anything up. We are definately narrowing down the culprit, and I just hope we come to a solid conclusion. --- John Mendenhall [EMAIL PROTECTED] wrote: Tim, John, since you were able to boot the ultimate boot cd and run both drives completely, I don't think any hardware is the culprit. Your CD drive, Hard Drive(s), memory, etc all work under that OS. My mindset is now leading to some bug that OpenBSD is doing (probably) with the ATA controller. Probe from the ultimate boot cd to see what ATA controller it is using, and then find what OpenBSD is finding the ATA controller to be. A minor model difference could be the culprit (model 1234 versus model 1234a, for example). I am using the thunderboot ultimate boot cd. Any hints on which tool could get the ata controller the box is using? I can see the ATA-# supported (6,5,4,3,2). Lots of other information. I don't see a model/version number yet. I will keep checking all the tools on here. JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. You snooze, you lose. Get messages ASAP with AutoCheck in the all-new Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_html.html
Re: new openbsd 4.0 server, panic on ufsdirhash
I subscribe to the digest, so I've copied the message and excluded the quoting characters () - Quote -- Received:from a.mx.surfutopia.net (a.mx.surfutopia.net [69.63.196.98]) by shear.ucar.edu (8.14.1/8.13.6) with ESMTP id l47HTpuJ013519 for misc@openbsd.org; Mon, 7 May 2007 11:29:52 -0600 (MDT) Received: by a.mx.surfutopia.net (Postfix, from userid 1000) id 5B2B9F23B; Mon, 7 May 2007 10:29:50 -0700 (PDT) Date: Mon, 7 May 2007 10:29:50 -0700 From: John Mendenhall [EMAIL PROTECTED] To: Artur Grabowski [EMAIL PROTECTED] CC: misc@openbsd.org Subject:Re: new openbsd 4.0 server, panic on ufsdirhash Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To:[EMAIL PROTECTED] User-Agent: Mutt/1.5.6i X-Archive-Number: 200705/407 X-Sequence-Number: 49945 Artur, Have you done forced fsck of the partitions? This sounds like a problem with the data you have on disk. It would be even nicer if you could update to a newer fsck because it has been updated to deal with many new strange corner cases we've been seeing. Although, that might or might not require a fully -current system, I'm not fully aware of everything that has been going in fsck, but some of the ffs2 support might have messed things up. We've seen one of those panics recently on an important OpenBSD infrastructure machine and that led to a lot of fsck work (since fsck didn't catch the particular problem). But on production machines we deal with filesystem corruption by simply dumping the filesystem and restoring it from scratch. You might want to try that as well. We have done a forced fsck on the partition with the error. The problem is, there is no data other than the openbsd install. All I was trying to do was load the source from the openbsd cd into /usr/src. I don't need to restore since this is a new machine. I have not done anything to it. I'll just reinstall the entire thing. Unless someone wants me to try something else. Thanks! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services --- /QUOTE John, I've heard, and seen, a lot of odd problems that can't be duplicated with the same error when there's either of the following true. 1) overclocked hardware 2) bad system memory I'm doubting your system memory, but I'm curious about your overclocking. I don't think I've followed very carefully what you've already tried, and wonder if the mindset has ever drifted away from Hard Drives and ATA controllers. Another thread suggested catting /dev/ad0s1 /dev/null and seeing how many errors you get. If you get errors, it might point to what can't be read (and maybe can't be written then). You might have to use another tool, but you should get the jist of what I'm trying to suggest. Good luck. If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: new openbsd 4.0 server, panic on ufsdirhash
Replies interspersed. --- John Mendenhall [EMAIL PROTECTED] wrote: Tim, On Tue, 08 May 2007, Tim Judd wrote: - Quote -- Date: Mon, 7 May 2007 10:29:50 -0700 From: John Mendenhall [EMAIL PROTECTED] To: Artur Grabowski [EMAIL PROTECTED] CC: misc@openbsd.org Subject:Re: new openbsd 4.0 server, panic on ufsdirhash Artur, We have done a forced fsck on the partition with the error. The problem is, there is no data other than the openbsd install. All I was trying to do was load the source from the openbsd cd into /usr/src. I don't need to restore since this is a new machine. I have not done anything to it. I'll just reinstall the entire thing. Unless someone wants me to try something else. Thanks! JohnM --- /QUOTE John, I've heard, and seen, a lot of odd problems that can't be duplicated with the same error when there's either of the following true. 1) overclocked hardware 2) bad system memory I'm doubting your system memory, but I'm curious about your overclocking. I don't think I've followed very carefully what you've already tried, and wonder if the mindset has ever drifted away from Hard Drives and ATA controllers. Another thread suggested catting /dev/ad0s1 /dev/null and seeing how many errors you get. If you get errors, it might point to what can't be read (and maybe can't be written then). You might have to use another tool, but you should get the jist of what I'm trying to suggest. All hardware is as received, no overclocking is being done. The system memory was the first issue we had. I have set the bios such that the system memory gives no errors on very long memtest runs. Currently, we are running a low level format of the two disks. No errors yet, but will run another day or so. Then, we'll reinstall the os and see how it goes. Why would I want to cat /dev/ad0s1? Or, are you referring to the actual drive, which is /dev/wd0? I'm sorry, I switch between FreeBSD and OpenBSD so often, I don't catch myself often enough stating the right device name. This is the OpenBSD mailing list and I should have thought. I did mean OpenBSD's drive name, which would be wd0. 'cat'ting the drive is simply reading data from the surface and sending it to the bitbucket, so we can see if we can read the surface of the drive without errors. A low-level format is an interesting twist, and I would like to see if that helps. I've witnessed myself a drive with bad blocks dissapear after a high-level format. It was the oddest of things, the FS itself was corrupted and a disk check didn't help the situation. Maybe it was a glitch, I don't know. I put that drive back into rotation. Good luck. Thanks! You're welcome! JohnM -- john mendenhall [EMAIL PROTECTED] surf utopia internet services If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather
New Samba 3.0x on OpenBSD 4.x
Hello list, I'm subscribed to the digest, so I don't reply unless I see a posting in the next day. I would reply to privmsgs though. I'm trying to setup a OpenBSD box to provide user logins domain membership with samba 3.0.24-main (via packages). I configure it like I have configured samba in the past, but something is new, different. When I try to obtain the current mapping of NTGROUPS to UNIXGROUPS via net groupmap list -- all I get is my prompt back, not even a blank line. It's as if there are no groups defined. But shouldn't a group be defined for example, Domain Admins, or Users, etc? Maybe not mapped right, but defined.. I'm not able to find anything via google with the search terms I'm trying. And I would appreciate any help. CC me for a quicker response. :) thanks. If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Dynamic DNS (first setup, couple troubles)
--- Tim Judd [EMAIL PROTECTED] wrote: Thanks for ANY help from all of you excellent people out there. Of you want a configuration file, they are available at: http://usemy.homeunix.org:88/dhcpd.txt http://usemy.homeunix.org:88/named.txt I was seeing if anybody was checking my problem out by viewing the access log on my server, and I found named.txt to be getting error 403 -- which I should have fixed by now. If you still want to address this and want to look at my files, please try again. thank you all! If opportunity doesn't knock, build a door. I can is a way of life. More and Bigger is not always Better. The road to success is always uphill. Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Dynamic DNS (first setup, couple troubles)
Hi everyone -- I'm hoping that someone here can clue me in.
With a couple of websites' help, I got ddns working to create records,
but nothing I do seems to be able to remove those entries. They are
inserted under the name that the host had when it inserted the record,
and never updates. The single PC that is booting OpenBSD/i386 isn't
getting it's new name into ddns.
References:
#1:
http://72.14.253.104/search?q=cache:4Y72kR1rdNMJ:www.bsdguides.org/guides/openbsd/networking/dynamic_dns_dhcp.php+openbsd+ddnshl=enct=clnkcd=1gl=usclient=firefox-a
(The original page on bsdguides just gives me a blank page, so I used
Google's cached version. This howto was written with OpenBSD 3.6)
Network topology:
OpenBSD/sparc 4.0-RELEASE (will download and apply patches this
weekend, it's a new installation) is the DHCP/BIND ddns machine. It's
serving a network of 192.168.1/24 with two DHCP reservations.
Windows workstation is one of the reservations, and my FreeBSD box is
the other (.11 and .10 respectively).
The test box as mentioned above is OpenBSD/i386.
First problem:
The two machines with DHCP Reservations yield this error when being
booted.
- Quote -
Apr 13 20:23:46 usemy dhcpd: Dynamic and static leases present for
192.168.1.11.
Apr 13 20:23:46 usemy dhcpd: Remove host declaration FATMAN or remove
192.168.1.11
Apr 13 20:23:46 usemy dhcpd: from the dynamic address pool for
192.168.1/24
- /Quote -
And the host declarations are simple, like this:
- Quote -
host FATMAN {
hardware ethernet 00:02:B3:XX:XX:XX;
fixed-address 192.168.1.11;
}
- /Quote -
What should I do to eliminate the error above? clear the dhcpd.leases
file?
Second Problem:
Once a host has been established (as mentioned above), it's entry isn't
updated, in the 30-60 minutes of playing with this that I've done so
far. How can I force this update? Or for the matter, force a removal
of said entry?
As a side note: the Bind ARM mentions something about using rndc as the
tool to control the nameserver (freezing a zone if you need to edit the
zonefile for example). Can someone give me confirmation that's how you
do it? What I read didn't make much sense, but I may have been looking
in the wrong place! :( :(
Thanks for ANY help from all of you excellent people out there. Of you
want a configuration file, they are available at:
http://usemy.homeunix.org:88/dhcpd.txt
http://usemy.homeunix.org:88/named.txt
If opportunity doesn't knock, build a door.
I can is a way of life.
More and Bigger is not always Better.
The road to success is always uphill.
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
