9.0 - Mount to root.. Sorted..
Hi all, As Warren Block mentioned: If there are no ada devices in /dev at all, I'd guess too much has been > removed from the custom kernel. > So I've checked my custom kernel config (based on GENERIC) & indeed made some changes to the [S]ATA disk section after which I rebuilt & installed the kernel again.. The difference now with previous was that I *was* able to boot in single-user mode, mount, label my disk with tunefs, update my /etc/fstab accordingly & managed to install the world as a final step to my upgrade.. Problem solved, many thanx for all the assistance.. Regards, E. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Upgrade to 9.0 - Mount to root failed..
Hi Matthew, Thanx for the quick reply.. Can't get it to work though.. On 08/04/2012 09:53, Airosoβicz fb. wrote: > > So I've upgraded from 8.1 to 9.0 & now the system can't mount in single > > user mode to go through the final step of installing the world.. > > As was mentioned else-thread, you are probably hitting problems due to > the name change from ad(4) to ada(4) for PATA/SATA disk devices. > It's starting to make sense now.. Mounting ufs:/dev/ad*a*2s1a i.o. from ufs:/dev/ad2s1a simply doesn't work because as I've put in my original post with # ls -l /dev/ad* it doesn't exist.. Only ad2,ad2s1 & ad2s1a do.. > One way to fix this is simply to type in the new boot device in the > loader and then edit /etc/fstab from single user mode > Which boot device..? I wish it was simple.. The preferred method nowadays is to label the partitions, so probably > tunefs(8) labelling would be the best choice to get you through > the 8.1 -> 9.0 reboot. ie. Create the label: > ># tunefs -L ROOT /dev/as2s1a > # man 8 tunefs: The tunefs can not be run on an active filesystem. To change an active filesystem it must be downgraded to read only or to unmounted.. [Which I've done with # mount -r -f..] # tunefs: /dev/ad2s1a: failed to write superblock.. I've updated the /etc/fstab with the ROOT label but I can't get the single-user mount nor the tunefs to work.. Regards, E. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Upgrade to 9.0 - Mount to root failed..
Greetings all,
It's my 1st time on any of the FreeBSD lists & I'm fairly new to FreeBSD to
please bear with me..
So I've upgraded from 8.1 to 9.0 & now the system can't mount in single
user mode to go through the final step of installing the world..
# cvsup.. Done..
# make buildworld.. Done..
# make buildkernel.. Done..
# make installkernel.. Done..
# reboot in single user mode to install world.. Failed to mount to
/dev/ad2s1a.. {Yes, that *is* my HD}
I rebooted from the loader prompt with my old (GENERIC) kernel & came up
with the following..
peggy# ls -l /dev/ad*
> crw-r- 1 root operator0, 79 Apr 8 08:47 /dev/ad2
> crw-r- 1 root operator0, 82 Apr 8 08:47 /dev/ad2s1
> crw-r- 1 root operator0, 84 Apr 8 08:47 /dev/ad2s1a
>
> peggy# cat /etc/fstab
> # DeviceMountpointFStypeOptionsDumpPass#
> /dev/ad2s1a/ufsrw11
> /dev/acd0/cdromcd9660ro,noauto00
>
> peggy# disklabel /dev/ad2s1a
> # /dev/ad2s1a:
> 8 partitions:
> #size offsetfstype [fsize bsize bps/cpg]
> a: 2004401704.2BSD 2048 16384 28552
> c: 200440170unused0 0 # "raw" part,
> don't edit
>
> peggy# fsck
> ** /dev/ad2s1a (NO WRITE)
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 415735 files, 3148200 used, 1702923 free (40563 frags, 207795 blocks, 0.8%
> fragmentation)
>
> peggy# kldstat
> Id Refs AddressSize Name
> 17 0xc040 bb5504 kernel
> 21 0xc2e1a000 26000linux.ko
>
I know there's many 'mount' problem discussions out there but I can't seem
to find out how to overcome this problem..
Many thanx in advance for any assistance..
Regards,
E.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
bge(4) for BCM5715S
Miladies, Gentlemen, Is there any chance to get a working driver for Broadcom Ethernet BCM5715S in a near future (7.0)? Or later? If not, is there any clue to patch the existing driver which claims to support this controller but actually doesn't. The linux driver does, but FreeBSD and linux driver frameworks (and quality) are not closed enough to do the trick easily. A quick look at pieces of code seems to indicate that a BCM800x ground would be needed. But we miss any data sheet... Any information, even negative, is welcome. Regards, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multiple IPs in Jail
Hey all - We patched mijail5 (http://garage.freebsd.pl/mijail.README) against RELENG_5_1. Most of the patch was successful with a little fuzz, except for a couple lines in jls which didn't patch due to cosmetic changes (easily fixed). Before the patch was applied, the jail environment had no problem with dns. After the patch was applied however (and userland rebuilt both on host and jail), dns breaks in the jail environment. Basically, gethostbyname fails and h_errno is set to 2 - Host name lookup failure. the system is configured properly, since the only changes are to the kernel and the modified jail mechanism. Also interesting is that the failure is immediate, there is no timeout. However, inbound/outbound TCP traffic is not effected. - we are able to ssh in/out of the jailed environment. I was testing outbound UDP traffic however - simple matter of binding a socket to send a packet to a remote host. Outside the jail, it worked fine. inside the jail, sendto failed with a EINVAL error. Any help on this topic would be much appreciated. -Mike PS: I apologize for the cross-post to the freebsd-hackers and freebsd-questions lists... Need to get this box up ASAP and this is a major setback. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.537 / Virus Database: 332 - Release Date: 11/6/2003 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PCI parallel port (2)
>Hi, I'm trying to install an additional lpt using PCI parallel port card NetMos >Nm9805CV. >The 4.7 kernel reports: >pci0: (vendor=0x9710, dev=0x9805) at 20.0 irq 11 >How can I use it? >Thanks. Well, it works on Linux, what about FreeBSD? This installation guide describes the procedure to install the Nm9705,Nm9735CV, Nm9805CV, Nm9715CV, Nm9835CV, Nm9755CV PCI parallel ports in Linux platform. Linux kernel provide a 'parport' code to support parallel port (/dev/lp0, /dev/lp1, /dev/lp2). This code provides the ability to share one port between multiple devices. And it is loadable when kernel is running. The 'parport' code is split into two parts : generic (which deals with port sharing) and architecture-dependent eg. X86, SPARC. (which deals with actually using the port). Thus, please take the following steps to install 'parport' module! Check the on-board parallel port's hardware resources Most likely each motherboard has a built-in parallel port. And its hardware resources are settable with BIOS utility. Enter the command more /proc/pci The response is similar to the following Bus 0, Device 11, function 0: Serial controller : Unknown vendor Unknown device (rev 01). Vendor id=9710, Device id=9705 Device id=9735 Device id=9805 Device id=9815 Device id=9835 Device id=9855 Medium devsel. Fast back-to-back capable. IRQ 11 Board with Nm9805CV part I/O at 0xc000 [0xc001] printer port I/O at 0xc400 [0xc401] ECP/EPP config registers I/O at 0xc800 [0xc801] not used I/O at 0xd000 [0xd001] not used I/O at 0xd400 [0xd401] not used I/O at 0xd800 [0xd801] not used Install 'parport' module To load the generic 'parport' code Typeinsmod parport.o To load the architecture-dependent code to tell 'parport' code insmod parport_pc.o io=0x378,0xc000,0xc800 irq=7, irq=11, none or insmod parport_pc.o io=0x378,0xc000,0xc800 irq=7,11,none You have three PC-style ports, one at 0x378 with IRQ 7, one at 0xc000 with IRQ11, one at 0xc800 with no IRQ. Check the attached printer device [optional] Once the architecture-dependent part of the paraport code is loaded into the kernel. You could enter the following command insmod parport_probe.o To check any attached devices and log a message similar to parport0: Printer, epson Then/dev/lp0, /dev/lp1 and /dev/lp2 are ready for service To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
PCI parallel port
Hi, I'm trying to install an additional lpt using PCI parallel port card NetMos Nm9805CV. The 4.7 kernel reports: pci0: (vendor=0x9710, dev=0x9805) at 20.0 irq 11 How can I use it? Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Wrong file sizes in the stand directory
Hi, I installed the 4.7-mini.iso and found the following: total 70766 -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 -sh -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 [ -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 arp -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 boot_crunch -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 camcontrol -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 cpio -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 dhclient -r-xr-xr-x 1 root wheel 7175 Oct 10 01:18 dhclient-script drwx-- 3 root wheel 512 Dec 8 07:01 etc -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 find -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 fsck -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 gunzip -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 gzip drwxr-xr-x 2 root wheel 1024 Dec 8 07:01 help -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 hostname -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 ifconfig -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 minigzip drwxr-xr-x 2 root wheel 512 Dec 8 07:01 modules -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 mount_mfs -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 mount_nfs -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 newfs -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 pccardc -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 pccardd -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 ppp -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 pwd -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 rm -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 route -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 rtsol -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 sed -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 sh -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 slattach -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 sysinstall -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 test -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 tunefs -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 usbd -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 usbdevs -r-xr-xr-x 33 root wheel 2175016 Oct 10 01:09 zcat Everything else is OK, fsck reports a clean system, df sees normal size. What's the problem? Thanks. DS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
