search for: da0s1a

I successfully did my first FreeBSD upgrade yesterday after looking at the manual, and cross referencing with Googling and getting help from our network engineer here at CWU. Before the upgrade, running df showed: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 507630 77662 389358 17% / devfs 1 1 0 100% /dev /dev/da0s1e 507630 588 466432 0% /tmp /dev/da0s1f 268217320 4866120 241893816 2% /usr /dev/da0s1d 4298926 162066 3792946 4% /var Now it shows: Filesystem 1K-blocks...

...org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Right now, I am on step 21.4.8 Reboot into Single User Mode. I have compiled my new kernel, and I was trying to reboot into single user mode to test the new kernel. When I do this, I get the following error message: Mounting root from ufs:/dev/da0s1a no such device 'da' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 I don't understand what is going on here. THe device /dev/da0s1a exists. I compiled the new kernel using the same kernel config file I used to compile my 4.7RELEASE kernel. My old kernel...

Hi, looking at the messages i see errors with ntp everytime i reboot my server: shiva2# tail /var/log/messages Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC 2006 (1) Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Apr 5 15:32:46 shiva2 ntpd[385]: bind()...

...two disks, replacing them with two new ones. Now on the same Compaq box, I am still experiencing the same symptoms. For starters, `mount` does not report the correct disk sizes: da0 is 17GB da1 is 36GB but `df -h` gives following output Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 16G 4.5G 10.0G 31% / /dev/da1s1e 34G 17G 13G 56% /wananchi The output of `mount` is: wash@ns2 ('tty') ~ 129 -> mount /dev/da0s1a on / (ufs, local, soft-updates) /dev/da1s1e on /wananchi (ufs, local, soft-updates) I am beginning to think that disk space is...

...ne filesystem, though, which might be to do with its size. It's not over the 2TB marker, but it's pretty close. It's also backed by a hardware RAID system, although a smaller filesystem on the same RAID has no issues. Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 2078881084 921821396 990749202 48% /u2 To clarify "completely freezes up": unresponsive to all services over the network, except ping. On the console I can switch between the ttys, but none of them respond. The only way out is to hit the reset button. Any advice? I'm happy to...

...[2]: Tasting ad10s1. GEOM_MIRROR[2]: Tasting ad10s1a. GEOM_MIRROR[2]: Tasting ad10s1c. Trying to mount root from ufs:/dev/mirror/gm0.journals1a Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:da0s1a ? List valid disk boot devices <empty line> Abort manual input mountroot> With kernel.geom.journal.debug set to 2 I get: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB <SAMSUNG HD501LJ CR100-13> at ata2-master SATA300 ad4: 976...

...will try ... assuming that it doesn't, is there anything that I should run to get more information when something like this happens? Note that when this happens, I can't do an ls of /vm ... /vm isn't a unionfs: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 516062 84446 390332 18% / /dev/da0s1e 1032142 24 949548 0% /tmp /dev/da0s1f 10322414 7972110 1524512 84% /usr /dev/da0s1g 1032142 91890 857682 10% /var /dev/da0s1h 119837208 85749532 24500700 78% /vm...

...: NULL p for 'home.p0.s0' gv_plex_taste: NULL p for 'usr.p0.s0' gv_plex_taste: NULL p for 'var.p1.s0' gv_plex_taste: NULL p for 'tmp.p1.s0' gv_plex_taste: NULL p for 'home.p1.s0' gv_plex_taste: NULL p for 'usr.p1.s0' Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted WARNING: R/W mount of / denied. Filesystem is not clean - run fsck Subdisk usr.p0.s0: Size: 5898970624 bytes (5625 MB) State: up Drive donau (donau) at offset 2307002880 (2200 MB) /dev/da0s1b none swap sw 0 0 /dev/da1s1b none swap sw 0 0 /...

...enofreebsd/7.0/download/ The problem is that I can''t specify _any_ root, the kernel can recognize: Mount point / had 1 dangling refs Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:da0s1a ? List valid disk boot devices <empty line> Abort manual input mountroot> And here I''m stuck since it even doesn''t allow me to enter a char. I''ve tried several vfs.root.mountfrom specifications per googled advises, including /dev/md...

...v3.4.31 initialized. Default = block all, Logging = enabled acd0: CDROM <CD-ROM CDU571-Q> at ata0-master BIOSPIO sa0 at sym0 bus 0 target 6 lun 0 sa0: <HP C1533A A907> Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 16) Mounting root from ufs:/dev/da0s1a no such device 'da' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 -------------------- also, i added working 4.7-p10 kernel dmesg: ---------------------- Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 19...

..., 315721 blocks, 0.3% fragmentation)/dev/ad2s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da1s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad2s1g: clean, 35322687 free (74535 frags, 4406019 blocks, 0.1% fragmentation) /dev/da1s1a: clean, 508234 free (6146 frags, 62761 blocks, 0.8% fragmentation) /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1a: clean, 224734 free (670 frags, 28008 blocks, 0.1% fragmentation) /dev/ad2s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad2s1a: clean, 123038 free (1206 frags, 15229 blocks, 0.3% fragmentation) /dev/da0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1...

...in Solaris, FreeBSD I'm using both Solaris and FreeBSD quite extensively and, honestly, have never heard of that assumption. In fact, on the machine that I'm currently typing this message on, the file systems look like this: # uname -sr; mount -t ufs FreeBSD 10.1-RELEASE /dev/da0s1a on / (ufs, local, journaled soft-updates) /dev/da0s1d on /tmp (ufs, local, journaled soft-updates) /dev/da0s1e on /var (ufs, local, journaled soft-updates) /dev/da0s1f on /usr (ufs, local, journaled soft-updates) (Everything else, especially /home, is NFS-mounted.) Patrick

On Jun 8, 2015, at 8:16 PM, g <geleem at bellsouth.net> wrote: > > On 06/08/2015 09:11 PM, John R Pierce wrote: >> On 6/8/2015 6:29 PM, Peter wrote: >>> You can thank Fedora for making that rather pointless change and >>> breaking that capability. >> >> that 'capability' was a holdover of the 1980s when disks were >> measured in

A problem with 4.8 reported by myself and Aaron D. Gifford. Anyone in -stable who knows more? ******** I'm assembling a Compaq 1850R with attached storage system. For the built in scsi controller (sym), there are three drives internally on channel 1 + 5 drives externally on channel 2. During boot, I can see all disks being identified first by the machine itself and then in the early part

...bridge> on iicbus0 smbus0: <System Management Bus> on iicsmb0 smb0: <SMBus general purpose I/O> on smbus0 iic0: <I2C general purpose I/O> on iicbus0 acd0: CDROM <MATSHITA CR-176> at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da1 at ahc1 bus 0 target 0 lun 0 da1: <transtec > Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 293210MB (600494080 512 byte sectors: 255H 63S/T 37379C) da0 at ahc0 bus 0 target 0 lun 0 da0: <SEAGATE ST39236LC 0010&...

...byte sectors: 64H 32S/T 2049C) da0 at ahc0 bus 0 target 0 lun 0 da0: <SEAGATE ST32430N 0510> Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 64H 32S/T 2049C) Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted <118>Loading configuration files. <118>kernel dumps on /dev/da0s1b <118>Entropy harvesting: <118>. <118>swapon: adding /dev/da0s1b as swap device <118>Starting file system checks: <118>/dev/da0s1a: 1012 files, 21314 us...

...rupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 9671MB <WDC AC310100B> [19650/16/63] at ata0-master UDMA33 ad1: 39082MB <Maxtor 54098U8> [79406/16/63] at ata1-master UDMA33 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: <WDIGTL WD91 ULTRA2 1.00> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) -- Jacob S. Barrett jbarrett@amduat.net www.amduat.ne...

...bled SMP: AP CPU #1 Launched! acd0: CDROM <LG CD-ROM CRN-8245B> at ata0-master PIO4 da0 at mly0 bus 2 target 0 lun 0 da0: <RAID 5 online > Fixed Direct Access SCSI-2 device da0: 135.168MB/s transfers da0: 68664MB (140623872 512 byte sectors: 255H 63S/T 8753C) Mounting root from ufs:/dev/da0s1a --------------------------------------------------------------- Robert Westendorp Systems Administrator rjwsys@uniserve.com --------------------------------------------------------------- UNIServe Online Disclaimer: "The sender intends this message for a specific recipient and, as it may con...

...OAPIC #0 intpin 2 IPsec: Initialized Security Association Processing. Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc2 bus 0 target 6 lun 0 sa0: <HP HP35470A T603> Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers Mounting root from ufs:/dev/da0s1a cd0 at ahc2 bus 0 target 4 lun 0 cd0: <PLEXTOR CD-ROM PX-40TS 1.13> Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da0 at ahc0 bus 0 target 0 lun 0 da0: <WDIGTL WDE9180 ULTRA2 1.30> Fixed Dir...

...9. Loader variables: vfs.root.mountfrom=ufs:/dev/ad0p2 vfs.root.mountfrom.options=rw Manual root filesystem specification: <fstype>:<device> [options] Mount <device> using filesystem <fstype> and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) <empty line> Abort manual input mountroot> panic: mountroot: unab...