Date: Fri, 28 Nov 2014 11:44:44 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-virtualization@freebsd.org Subject: Re: Unsupported cmd:c4 (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 00 00 00 40 00 00 00 00 01 00 Message-ID: <5478A67C.7030904@freebsd.org> In-Reply-To: <C47B8B4E-5127-4121-BC73-2B4E6129652B@develooper.com> References: <C47B8B4E-5127-4121-BC73-2B4E6129652B@develooper.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 2014-11-28 05:42, Ask Bjørn Hansen wrote: > Hi everyone, > > I’ve spent some time off this week upgrading my build-my-personal-NanoBSD-image tool from a VMware virtual machine to a physical box running a 32-bit build-box under bhyve. > > So far so good — all that has been working really well. > > My nanobsd image is only used on Soekris and PC Engines boxes and my production images are really small (some <100MB storage and ~32MB memory), so I have a crufty kernel config that excluded a bunch of stuff I (thought I) don’t need. > > Now I’d like to run my built image under bhyve for testing. It’s easier for me if the disk comes up as an ada device, so I’m using ahci-hd instead of virtio-blk. With virtio-blk the system boots but the device has the “wrong" name. > > With ahci-hd it can’t read my partition for some reason. > > I’ve tried with both file and zvol backing store. > > This is the error I’m getting: > > ada0: <BHYVE SATA DISK 001> ATA-8 SATA 2.x device > ada0: Serial Number 123456 > ada0: 300.000MB/s transfers (SATA 2.x, PIO4, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 260MB (532480 512 byte sectors: 16H 63S/T 528C) > ada0: Previously was known as ad4 > Unsupported cmd:c4 > (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 c1 1f 08 40 00 00 00 00 04 00 > (ada0:ahcich0:0:0:0): CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 04 (ABRT ) > (ada0:ahcich0:0:0:0): RES: 41 04 00 00 00 40 00 00 00 00 00 > (ada0:ahcich0:0:0:0): Retrying command > Unsupported cmd:c4 > > > Any suggestion for what I’m doing wrong? Did I compile my kernel with some idiotic set of not-working options? > > > Ask > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > When using zvols, you must set the 'volmode' to 'dev', otherwise GEOM on the host locks the disk and causes all kinds of interesting things to happen. Note: the volmode property is only applied when the device is created, so you might have to 'zfs rename' it to cause it to be recreated -- Allan Jude [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUeKZ/AAoJEJrBFpNRJZKf+EYQAJzI3K/QjmdntfRSjNDhVf/0 5soTK03w8cLIvxcO6GbOZToofXkvfUOPm0ujFo7k7KA4EkQT6zVPMn6LNkjRDZ4G GGxVzgUvAPHohi0Jy8sNuQKSXF48t4LRV9Sa+Ev2i0t1wP9HeTXVy2HwfHaiAVrt XdEil7vDN4LzFaLzJhjW26WzJ06Oh22fr1KMwxaiKrhmLZDulHIpXggp+4bYMd7d V60Nb/viJZat5fpuG0iJT98vYh+c6lKlixiZF3FCyvkdTv7bV/WoVoCFKxx7wBsP al1//tmWNQOalIKoupxSekGYKbxRuzvP/bcs5aLy63q9D1tNZaNk7OD2bGnffPfC 1huO/rEPBkU2EaVOsuXLDiTf95v7SOB7PQNZLR+3p0WyTC+WvoAFLZMbEv8W6oOo ibDTrbeWzDdPFnwV45L6xSGEZ3JPAkljB4ectrByoZAil5vlGGX9QLwg7xSKoXxb hzqbBHeEkKEMItPdbDzzJFyO1LhIymKtGkGFbXj3E62iXyTABSbaohj6TNlcXRlh YA0iB0po7GLinrmqd1cOaBFOeB00q0f5OiARWYMTA1vUpa2fpa/z5PV+IJ1GzQcz Cf/G5aCLmeFwRDQ0l0s3ElUS6JmrJG3v9Le7325xu975a0iSQm8sMjEa3/b6qfV2 MwoWPdUX3jkRj45Ise7b =ReGD -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5478A67C.7030904>