search for: ada1

...0 on atapci0 ata1: <ATA channel> at channel 1 on atapci0 ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: <IBM-DJNA-352500 J51OA30K> ATA-4 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 24405MB (49981680 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata1 bus 0 scbus1 target 0 lun 0 ada1: <ST3250824A 3.AAE> ATA-7 device ada1: 100.000MB/s transfers (UDMA5, PIO 8192bytes) ada1: 238475MB (488397168 512 byte sectors: 1H 255S/T 16383C) ada1: Previously was known as ad2 (ada1:ata1:0:0:0): READ_DMA. ACB: c8 00 00 00 00 40 00 00 00 00 10 00 (a...

...to start the volume, glusterd dumps core. The tail of the log after the crash: +------------------------------------------------------------------------------+ [2014-04-28 21:49:18.102981] I [glusterd-rpc-ops.c:356:__glusterd_friend_add_cbk] 0-glusterd: Received ACC from uuid: 84c0bb8e-bf48-4386-ada1-3e4db68b980f, host: fed-gfs4, port: 0 [2014-04-28 21:49:18.138936] I [glusterd-handler.c:2212:__glusterd_handle_friend_update] 0-glusterd: Received friend update from uuid: 84c0bb8e-bf48-4386-ada1-3e4db68b980f [2014-04-28 21:49:18.138982] I [glusterd-handler.c:2257:__glusterd_handle_friend_update]...

...bus1 ada0 at ahcich0 bus 0 scbus1 target 0 lun 0 ada0: <INTEL SSDSA2CT040G3 4PC10362> ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich1 bus 0 scbus2 target 0 lun 0 ada1: <INTEL SSDSA2CT040G3 4PC10362> ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 ses0 at m...

Hi Guys, Has somebody encountered (significantly) different read/write speeds when using gmirror? I have 2xWD WD30EFRX RED drives which are configured as follows: $ gmirror status Name Status Components mirror/root COMPLETE ada0p2 (ACTIVE) ada1p2 (ACTIVE) mirror/data COMPLETE ada0p4 (ACTIVE) ada1p4 (ACTIVE) mirror/root is mounted as the root fs (UFS2). Doing write: $ time dd if=/dev/zero of=/IMAGE bs=1024k count=`expr 4 \* 1024` 4096+0 records in 4096+0 records out 4294967296 bytes transferred in 29.326044 sec...

...0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 raidz1 UNAVAIL 0 0 0 insufficient replicas ada0 UNAVAIL 0 0 0 cannot open ada1 UNAVAIL 0 0 0 cannot open ada2 UNAVAIL 0 0 0 cannot open ada3 UNAVAIL 0 0 0 cannot open 0(offsite)#

...p1 crw-r----- 1 root operator 0x66 Nov 3 10:01 /dev/ada0p2 crw-r----- 1 root operator 0x74 Nov 3 10:01 /dev/ada0p3 crw-r----- 1 root operator 0x8f Nov 3 10:01 /dev/ada0p3.eli crw-r----- 1 root operator 0x76 Nov 3 10:01 /dev/ada0p4 crw-r----- 1 root operator 0x61 Nov 3 10:01 /dev/ada1 crw-r----- 1 root operator 0x79 Nov 3 10:01 /dev/ada1p1 crw-r----- 1 root operator 0x7b Nov 3 10:01 /dev/ada1p2 crw-r----- 1 root operator 0x7d Nov 3 10:01 /dev/ada1p3 crw-r----- 1 root operator 0x9b Nov 3 10:01 /dev/ada1p3.eli crw-r----- 1 root operator 0x7f Nov 3 10:01 /dev/ad...

I have a GPT formatted disk where I recently expanded the size of a partition. I used "gpart resize -i 6 ada1" first to expand the partition to use the remaining free space and then growfs to modify the FFS file system to use the full partition. This was all done in single-user mode, of course, but when I enter "exit" to bring the system up, it failed to mount /usr. This was because /dev/ufs...

I had a sparc64 (Netra X1) running a stable/9 from late March 2013. Actually, the kernel may've been a bit newer than that as I was working with folks to diagnose and repair some Netra-X1 specific issues. But, ZFS worked fine. I have two pools, zroot as a RAID1 (using equally sized partitions at the front of two large disks), and a zdata that is a large pool of the remaining space of both

...r according to ''lspci'': 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (rev 40) Everything "works", but is it painfully slow. Reading from a single SATA drive within the DomU gives me about 0.5MB/s: [root@freenas /dev]# dd if=/dev/ada1 of=/dev/null skip=100000 bs=4096 count=1000 1000+0 records in 1000+0 records out 4096000 bytes transferred in 8.058105 secs (508308 bytes/sec) Concurrent reads from all five SATA drives show that they''re able to achieve this speed all at the same time: [root@freenas /dev]# for disk in ada...

...2 cs 00000000 ss 00000000 rs 00000008 tfd 50 serr 00000000 cmd 00046317 (aprobe0:ahcich0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ahcich0:0:0:0): CAM status: Command timeout (aprobe0:ahcich0:0:0:0): Error 5, Retry was blocked After this event, gpart show lists only ada1, ada2, and ada3. The boot drive is ada0. The entire dmesg can be seen at http://pastebin.com/RqR8LiSb. -- Jim Ohlstein

...0 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich0:0:15:0): CAM status: Command timeout (aprobe0:ahcich0:0:15:0): Error 5, Retries exhausted In both cases ada[01] are detected and available, but with 9.1-PRE I see: GEOM_RAID: Promise: Disk ada0 state changed from NONE to SPARE. GEOM_RAID: Promise: Disk ada1 state changed from NONE to SPARE. (I see the same when I # kldload geom_raid # from running 9.0, doesn't breaks anything...) I attach the full boot log with 9.1-PRE (bios with NO-raid nor AHCI enabled, but this changes nothing in the output) I could test patches or try any command required t...

...63S/T 243201C) ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: <OCZ-VERTEX4 1.5> ATA-9 SATA 3.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 122104MB (250069680 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: <OCZ-VERTEX4 1.5> ATA-9 SATA 3.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 122104MB (250069680 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 ada2 at ahcich2 bus...

...d 2.25T 1.91T 46.9K /storage/compressed storage/compressed/bacula 2.25T 1.91T 42.7K /storage/compressed/bacula storage/pgsql 5.50G 1.91T 5.50G /storage/pgsql $ sudo camcontrol devlist Password: <Hitachi HDS722020ALA330 JKAOA28A> at scbus2 target 0 lun 0 (pass1,ada1) <Hitachi HDS722020ALA330 JKAOA28A> at scbus3 target 0 lun 0 (pass2,ada2) <Hitachi HDS722020ALA330 JKAOA28A> at scbus4 target 0 lun 0 (pass3,ada3) <Hitachi HDS722020ALA330 JKAOA28A> at scbus5 target 0 lun 0 (pass4,ada4) <Hitachi HDS722020ALA330 JKAOA28A> at scbus6 target...

Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many

Hi, very periodically, we see I/O hangs for about 10 seconds, roughly once per minute. Each time this happens, the I/O rate simply drops to zero, and all disk access hangs; this is also very noticeable on the shell, for NFS clients etc. Everything else (networking, kernel, ?) seems to continue normally. Environment: FreeBSD 9.1R GENERIC on amd64, using ZFS, on a ARC1320 PCIe with 24x Seagate

...h2: <AHCI channel> at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: <AHCI channel> at channel 3 on ahci0 ahcich3: [ITHREAD] ahcich4: <AHCI channel> at channel 4 on ahci0 ahcich4: [ITHREAD] ahcich5: <AHCI channel> at channel 5 on ahci0 ahcich5: [ITHREAD] camcontrol identify ada1 pass1: <KINGSTON SH103S3120G 501ABBF0> ATA-8 SATA 3.x device pass1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 3.x device model KINGSTON SH103S3120G firmware revision 501ABBF0 serial number 50026B7223027059 WWN...

So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I

>> #1. Map the physical drive slots to how they show up in FBSD so if a >> disk is removed and the machine is rebooted all the disks after that >> removed one do not have an 'off by one error'. i.e. if you have >> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >> missing ada8 drive and the next drive (that used to be ada9) is now >> called ada8 and so on... > >How do you do that? If I'm in that situation, I think I could find the >bad drive, or at least the good ones, wi...

Hi Folks, I've facing an intermittent hang with a USB port which seems cam related: Event's that happen are: o USB modem (HUAWEI E220) plugged into PC ugen3.2: <HUA WEI> at usbus3 u3g0: <3G Modem> on usbus3 u3g0: Found 3 ports. umass0: <USB MASS STORAGE> on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:6:0:-1: Attached to scbus6 umass1: <USB

Hello -STABLE@, So I've seen this situation seemingly randomly on a number of both physical 9.1 boxes as well as VMs for I would say 6-9 months at least. I finally have a physical box here that reproduces it consistently that I can reboot easily (ie; not a production/client server). No matter what I do: reboot shutdown -p shutdown -r This specific server will stop at "All buffers