search for: da0s1

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...

Hello there, I have some problem with my filesystem. #df -h ... /dev/da0s1e 288M 265M -208.0K 100% /var ... #du -h /var .. 19M /var .. Does anybody has an idea what Im supposed to do? Thank you. --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo.

I was using a GELI partition for /usr/home on 7.0, so it attaches and mounts on boot. The problem is it stopped working after the system was upgraded to RELENG_7/7.1-PRERELEASE. Here's how it goes: I have the following /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d

...d 0/ sector 1; end: cyl 896/ head 254/ sector 63 but when was time to label it, I did it wrong: bsdlabel -w da0 should have aimed slice 2 now, I just get da0 on /dev and sysinstall only sees da0 also. but fdisk sees it all (as showed above) how can I erase all label info from da0 (not da0s1 or da0s2). I tried to rewrite fdisk and all mbr info, but label info is still there. I'd like not to have to reinstall OpenBSD, if possible. thanks, matheus -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q...

...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...

...cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad0s1a Loading configuration files. kernel dumps on /dev/ad2s1b Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/ad0s1b as swap device swapon: adding /dev/da0s1b as swap device swapon: adding /dev/da1s1b as swap device swapon: adding /dev/ad2s1b as swap device Starting file system checks: /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 103068 free (772 frags, 12787 blocks, 0.2% fragmentation) fsck: /dev/da1s1a in fstab more than once!...

...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

...ass-sim0 bus 0 target 0 lun 0 Oct 3 14:02:23 katrin /kernel: da0: <MCC DSC-3 1.00> Removable Direct Access SCSI-0 device Oct 3 14:02:23 katrin /kernel: da0: 650KB/s transfers Oct 3 14:02:23 katrin /kernel: da0: 122MB (250081 512 byte sectors: 64H 32S/T 122C) Oct 3 14:02:52 katrin /kernel: da0s1: slice starts beyond end of the disk: rejecting it Oct 3 14:02:52 katrin /kernel: da0s2: slice starts beyond end of the disk: rejecting it Oct 3 14:02:52 katrin /kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x10, scsi status == 0x0 and trying to mount via mount_msdos retur...

This morning I found a frozen box. On the console was this: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ata0-slave: ATA identify retries exceeded done After reboot, those messages were found in /var/log/messages. I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003. Any ideas? -- Dan Langille : http://www.langille.org/

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

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

...250G9F6 pass0: Tagged Queueing Enabled da0 at asr0 bus 0 target 0 lun 0 da0: <SEAGATE ST336706LW 010A> Fixed Direct Access SCSI-3 device da0: Serial Number 3FD0ZE2H00007250G9F6 da0: Tagged Queueing Enabled da0: 35003MB (71687353 512 byte sectors: 255H 63S/T 4462C) Mounting root from ufs:/dev/da0s1a da0s1: type 0xa5, start 63, end = 41929649, size 41929587 : OK da0s2: type 0xa5, start 41929650, end = 71682029, size 29752380 : OK start_init: trying /sbin/init WARNING: driver rp should register devices with make_dev() (dev_t = "#rp/0x10000") -------------- next part -------------- # #...

...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 u...

Hi Everyone, This is off-topic, so please feel free to disregard it, but I'm sending it to this list in the hope that it will reach a largish number of users. I am currently looking at updating some of our advocacy material (which advertises exciting new features like SMP support), and before I do I'd like to get a better feel for why the rest of you are using FreeBSD. If you had to