Dell PowerEdge Virtual Media
Jeff Blank
I'm having a little trouble using the "virtual media" function of
Dell's PowerEdge R-series (R710 in this case) iDRAC6 under FreeBSD
(7.1, 8.0). This is presented as /dev/cd0, a USB/"SCSI" device, I
guess. This is in the dmesg buffer when I boot up the existing 7.1
installation with the virtual optical drive mapped to the 8.0-RELEASE
amd64 DVD image:
umass0: <Avocent USB Composite Device-1, class 0/0, rev 2.00/0.00, addr 2> on uhub6
[...]
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <iDRAC Virtual CD 0323> Removable CD-ROM SCSI-0 device
cd0: 40.000MB/s transfers
cd0: cd present [1058105 x 2048 byte records]
GEOM_LABEL: Label for provider cd0 is iso9660/FreeBSD_Install.
However,
# mount -t cd9660 /dev/cd0 /mnt
mount_cd9660: /dev/cd0: Invalid argument
When I boot from the DVD image via this virtual device, sysinstall
comes up and works fine except for the fixit shell, at which point it
wants me to insert a CD/DVD because it encounters an error mounting
acd0 (and would presumably have the same problems if I attempted a
fresh install). I have 'boot -v' output from such a boot attempt at
http://web.mr-happy.com/mlf/8.0-bootv-dell-poweredge-r710-virtualmedia.txt
in case it's useful.
Please let me know what other information I can provide, and thank you
for any help.
Jeff
Jeremy Chadwick
> umass0: <Avocent USB Composite Device-1, class 0/0, rev 2.00/0.00, addr 2> on uhub6
> [...]
> cd0 at umass-sim0 bus 0 target 0 lun 0
> cd0: <iDRAC Virtual CD 0323> Removable CD-ROM SCSI-0 device
> cd0: 40.000MB/s transfers
> cd0: cd present [1058105 x 2048 byte records]
> GEOM_LABEL: Label for provider cd0 is iso9660/FreeBSD_Install.
>
> However,
> # mount -t cd9660 /dev/cd0 /mnt
> mount_cd9660: /dev/cd0: Invalid argument
You want /dev/cd0c, not /dev/cd0.
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
Jeff Blank
> On Tue, Dec 08, 2009 at 12:41:45PM -0500, Jeff Blank wrote:
> > # mount -t cd9660 /dev/cd0 /mnt
> > mount_cd9660: /dev/cd0: Invalid argument
>
> You want /dev/cd0c, not /dev/cd0.
There is no /dev/cd0c or any other, just /dev/cd0.
Jeff
Jeremy Chadwick
Not sure what to say then -- someone familiar with the USB->CAM
framework may want to chime in.
Andriy Gapon
> On Tue, Dec 08, 2009 at 12:41:45PM -0500, Jeff Blank wrote:
>> umass0: <Avocent USB Composite Device-1, class 0/0, rev 2.00/0.00, addr 2> on uhub6
>> [...]
>> cd0 at umass-sim0 bus 0 target 0 lun 0
>> cd0: <iDRAC Virtual CD 0323> Removable CD-ROM SCSI-0 device
>> cd0: 40.000MB/s transfers
>> cd0: cd present [1058105 x 2048 byte records]
>> GEOM_LABEL: Label for provider cd0 is iso9660/FreeBSD_Install.
>>
>> However,
>> # mount -t cd9660 /dev/cd0 /mnt
>> mount_cd9660: /dev/cd0: Invalid argument
>
> You want /dev/cd0c, not /dev/cd0.
What? Are you still using 4.X?
Or using some other OS?
--
Andriy Gapon
Jeff Blank
>
> What? Are you still using 4.X?
> Or using some other OS?
I'm using 7.1 (installed to disk) and 8.0 (DVD ISO/virtual media).
Jeff
Miroslav Lachman
I can confirm this behavior on 7-STABLE amd64 GENERIC (built Sun Dec 6
23:21:17 CET 2009) on Dell R610 with iDRAC 6.
System was installed from CD ISO booted on this virtual drive, but now
it is not possible to mount anything by /dev/cd0
Miroslav Lachman
Steven Hartland
you can't start fixit as it simply doesnt appear to find the "cd". This
was done on a supermicro with ipmi, which I believe uses the same or similar
controller under a different name.
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postm...@multiplay.co.uk.
Karl Denninger
ipKVM implementations. Try the CD boot media ISO.
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
>
> %SPAMBLOCK-SYS: Matched [@freebsd.org+], message ok
Miroslav Lachman
> The ipmi implementation is limited to CD-sized media on the Supermicro
> ipKVM implementations. Try the CD boot media ISO.
>
> Steven Hartland wrote:
>> I can confirm that's the same on 8.0-RELEASE DVD, you can boot from it
>> but
>> you can't start fixit as it simply doesnt appear to find the "cd". This
>> was done on a supermicro with ipmi, which I believe uses the same or
>> similar
>> controller under a different name.
Virtual Media on Supermicro 6016TT-TF TwinServer works fine for me
(tested with memtest86+-2.01.iso 1.75MB):
-----------------
Unknown USB device: vendor 0x046b product 0xff92 bus uhub3
umass0: <American Megatrends Inc. Composite Device, class 0/0, rev
2.00/1.00, addr 2> on uhub3
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <AMI Virtual CDROM 1.00> Removable CD-ROM SCSI-0 device
cd0: 40.000MB/s transfers
cd0: cd present [898 x 2048 byte records]
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
(probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
(probe0:umass-sim0:0:0:1): Medium not present
(probe0:umass-sim0:0:0:1): Unretryable error
da0 at umass-sim0 bus 0 target 0 lun 1
da0: <AMI Virtual Floppy 1.00> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
GEOM_LABEL: Label for provider cd0 is iso9660/MT201.
# mount -t cd9660 /dev/cd0 /mnt/
# ls /mnt/
boot readme.txt
-----------------
With the same ISO on Dell R610 I got following:
-----------------
Unknown USB device: vendor 0x0624 product 0x0249 bus uhub6
umass0: <Avocent USB Composite Device-1, class 0/0, rev 2.00/0.00, addr
2> on uhub6
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0
(probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): NOT READY asc:3a,0
(probe0:umass-sim0:0:0:0): Medium not present
(probe0:umass-sim0:0:0:0): Unretryable error
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <iDRAC Virtual CD 0323> Removable CD-ROM SCSI-0 device
cd0: 40.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
(probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:1): UNIT ATTENTION asc:29,0
(probe0:umass-sim0:0:0:1): Power on, reset, or bus device reset occurred
(probe0:umass-sim0:0:0:1): Retrying Command (per Sense Data)
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
(probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
(probe0:umass-sim0:0:0:1): Medium not present
(probe0:umass-sim0:0:0:1): Unretryable error
da0 at umass-sim0 bus 0 target 0 lun 1
da0: <iDRAC Virtual Floppy 0323> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
-----------------
Medium is not detected in this virtual drive. I don't know if it is
FreeBSD or iDRAC issue.
Virtual Media / Virtual Console from all vendors is paint in the a...
I have iLO card in HP ML110 G5 and Virtual Media doesn't work at all.
Virtual device is not detected by FreeBSD nor in BIOS, so I can't even
boot from it.
Virtual Media (console) on Sun Fire X2100 M2 is accessible only by IP
address, not by its domain name (I reported it to Sun Microsystems 11
month ago and Sun leaves it unfixed.
In Virtual Console of Supermicro, there is problem with keyboard input
in sysinstall prior to FreeBSD 8.x
So I am disapointed by this hyped feature ;(
Miroslav Lachman
Steven Hartland
> The ipmi implementation is limited to CD-sized media on the Supermicro
> ipKVM implementations. Try the CD boot media ISO.
If thats the case why can it happily boot from it? The issue only seemed
to occur here when you tried to access it via the fixit menu even though
the console log showed it as being detected just fine.
I've just retested on the machine now its up and running and see similar
results with both dvd's and cdroms.
Connect dvd iso:
Dec 9 02:21:27 ipmitest root: Unknown USB device: vendor 0x14dd product 0x0002 bus uhub3
Dec 9 02:21:27 ipmitest kernel: ugen3.2: <Peppercon AG> at usbus3
Dec 9 02:21:27 ipmitest kernel: umass0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:21:27 ipmitest kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000
Dec 9 02:21:28 ipmitest kernel: umass0:1:0:-1: Attached to scbus1
Dec 9 02:21:28 ipmitest kernel: ums0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:21:28 ipmitest kernel: ums0: 3 buttons and [Z] coordinates ID=0
Dec 9 02:21:28 ipmitest kernel: ukbd0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:21:28 ipmitest kernel: kbd2 at ukbd0
Dec 9 02:21:28 ipmitest kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
Dec 9 02:21:28 ipmitest kernel: (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Dec 9 02:21:28 ipmitest kernel: (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
Dec 9 02:21:28 ipmitest kernel: (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0
Dec 9 02:21:28 ipmitest kernel: (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
Dec 9 02:21:28 ipmitest kernel: (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
Dec 9 02:21:28 ipmitest kernel: cd0 at umass-sim0 bus 0 target 0 lun 0
Dec 9 02:21:28 ipmitest kernel: cd0: <PepperC Virtual Disc 1 0.01> Removable CD-ROM SCSI-3 device
Dec 9 02:21:28 ipmitest kernel: cd0: 40.000MB/s transfers
Dec 9 02:21:28 ipmitest kernel: cd0: cd present [1058105 x 2048 byte records]
Attempt to mount:
Dec 9 02:23:58 ipmitest kernel: (cd0:umass-sim0:0:0:0): READ TOC/PMA/ATIP. CDB: 43 0 0 0 0 0 0 0 4 0
Dec 9 02:23:58 ipmitest kernel: (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Dec 9 02:23:58 ipmitest kernel: (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition
Dec 9 02:23:58 ipmitest kernel: (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0
Dec 9 02:23:58 ipmitest kernel: (cd0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
Dec 9 02:23:58 ipmitest kernel: (cd0:umass-sim0:0:0:0): Retries Exhausted
Dec 9 02:23:59 ipmitest kernel: g_vfs_done():cd0[READ(offset=32768, length=2048)]error = 5
disconnect iso:
Dec 9 02:26:50 ipmitest kernel: ugen3.2: <Peppercon AG> at usbus3 (disconnected)
Dec 9 02:26:50 ipmitest kernel: umass0: at uhub3, port 6, addr 2 (disconnected)
Dec 9 02:26:50 ipmitest kernel: (cd0:umass-sim0:0:0:0): lost device
Dec 9 02:26:50 ipmitest kernel: (cd0:umass-sim0:0:0:0): removing device entry
Dec 9 02:26:50 ipmitest kernel: ums0: at uhub3, port 6, addr 2 (disconnected)
Dec 9 02:26:50 ipmitest kernel: ukbd0: at uhub3, port 6, addr 2 (disconnected)
Dec 9 02:26:51 ipmitest kernel: ugen3.2: <Peppercon AG> at usbus3
Dec 9 02:26:51 ipmitest kernel: ums0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:26:51 ipmitest kernel: ums0: 3 buttons and [Z] coordinates ID=0
Dec 9 02:26:51 ipmitest kernel: ukbd0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:26:51 ipmitest kernel: kbd2 at ukbd0
Dec 9 02:28:10 ipmitest kernel: ugen3.2: <Peppercon AG> at usbus3 (disconnected)
Dec 9 02:28:10 ipmitest kernel: ums0: at uhub3, port 6, addr 2 (disconnected)
Dec 9 02:28:10 ipmitest kernel: ukbd0: at uhub3, port 6, addr 2 (disconnected)
connect cdrom iso:
Dec 9 02:28:11 ipmitest root: Unknown USB device: vendor 0x14dd product 0x0002 bus uhub3
Dec 9 02:28:11 ipmitest kernel: ugen3.2: <Peppercon AG> at usbus3
Dec 9 02:28:11 ipmitest kernel: umass0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:28:11 ipmitest kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000
Dec 9 02:28:13 ipmitest kernel: umass0:1:0:-1: Attached to scbus1
Dec 9 02:28:13 ipmitest kernel: ums0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:28:13 ipmitest kernel: ums0: 3 buttons and [Z] coordinates ID=0
Dec 9 02:28:13 ipmitest kernel: ukbd0: <Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2> on usbus3
Dec 9 02:28:13 ipmitest kernel: kbd2 at ukbd0
Dec 9 02:28:13 ipmitest kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
Dec 9 02:28:13 ipmitest kernel: (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Dec 9 02:28:13 ipmitest kernel: (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
Dec 9 02:28:13 ipmitest kernel: (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0
Dec 9 02:28:13 ipmitest kernel: (probe0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
Dec 9 02:28:13 ipmitest kernel: (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
Dec 9 02:28:13 ipmitest kernel: cd0 at umass-sim0 bus 0 target 0 lun 0
Dec 9 02:28:13 ipmitest kernel:
Dec 9 02:28:13 ipmitest kernel: cd0: <PepperC Virtual Disc 1 0.01> Removable CD-ROM SCSI-3 device
Dec 9 02:28:13 ipmitest kernel: cd0: 40.000MB/s transfers
Dec 9 02:28:13 ipmitest kernel: cd0: cd present [164374 x 2048 byte records]
try to mount:
Dec 9 02:29:01 ipmitest kernel: (cd0:umass-sim0:0:0:0): READ TOC/PMA/ATIP. CDB: 43 0 0 0 0 0 0 0 4 0
Dec 9 02:29:01 ipmitest kernel: (cd0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Dec 9 02:29:01 ipmitest kernel: (cd0:umass-sim0:0:0:0): SCSI Status: Check Condition
Dec 9 02:29:01 ipmitest kernel: (cd0:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0
Dec 9 02:29:01 ipmitest kernel: (cd0:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred
Dec 9 02:29:01 ipmitest kernel: (cd0:umass-sim0:0:0:0): Retries Exhausted
Dec 9 02:29:02 ipmitest kernel: g_vfs_done():cd0[READ(offset=32768, length=2048)]error = 5
Stuart Barkley
> Virtual Media / Virtual Console from all vendors is paint in the
> a...
>
> I have iLO card in HP ML110 G5 and Virtual Media doesn't work at
> all. Virtual device is not detected by FreeBSD nor in BIOS, so I
> can't even boot from it.
>
> Virtual Media (console) on Sun Fire X2100 M2 is accessible only by
> IP address, not by its domain name (I reported it to Sun
> Microsystems 11 month ago and Sun leaves it unfixed.
>
> In Virtual Console of Supermicro, there is problem with keyboard
> input in sysinstall prior to FreeBSD 8.x
>
> So I am disapointed by this hyped feature ;(
Does anyone here find this stuff useful?
We have a vendor pushing "Virtual Media" on us and I don't see the
point at all. I also don't see the point of the screen scraping and
graphics virtual display support.
I've just started playing with IPMI capable motherboard and another
system with an IPMI add in card. Seems like at lot of extra stuff I
need to disable to secure my operations. nmap shows ssh, http, https,
portmap and some other ports of unknown purpose (plus the silly thing
was configured to send email to the manufacture). The web interface
is a little useful, but not when dealing with several hundred systems.
All I think I really want is basic (secure, encrypted) IPMI 2.0 to
read system status (power, temperature, fan status, etc) and be able
to power cycle the thing into a network PXE boot.
The Serial Over Lan stuff looks useful but overly complicated (I come
from a background where we used terminal servers for console access).
I would rather see no video board in the system at all, but nobody
seems to know how to build these boards anymore.
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
Miroslav Lachman
> On Tue, 8 Dec 2009 at 20:07 -0000, Miroslav Lachman wrote:
>
>> Virtual Media / Virtual Console from all vendors is paint in the
[...]
>> So I am disapointed by this hyped feature ;(
>
> Does anyone here find this stuff useful?
>
> We have a vendor pushing "Virtual Media" on us and I don't see the
> point at all. I also don't see the point of the screen scraping and
> graphics virtual display support.
It would be useful in our environment if 100% functional. It allows us
to remotely do everything with the server - deploy new OS from new
media, change BIOS settings, recovery from failure when server boots in
to single user etc. All this meens shorter downtime for us without need
to drive to the datacenter.
> I've just started playing with IPMI capable motherboard and another
> system with an IPMI add in card. Seems like at lot of extra stuff I
> need to disable to secure my operations. nmap shows ssh, http, https,
> portmap and some other ports of unknown purpose (plus the silly thing
> was configured to send email to the manufacture). The web interface
> is a little useful, but not when dealing with several hundred systems.
It is better to have it in private LAN (VPN) or firewalled, not allowing
public access to management interfaces.
[...]
Miroslav Lachman
Steven Hartland
> Does anyone here find this stuff useful?
Yes its is very useful for remote installs etc but it doest have its
limitations when it doesnt play nice with the OS.
Randi Harper
> On Tue, 8 Dec 2009 at 20:07 -0000, Miroslav Lachman wrote:
>
>> Virtual Media / Virtual Console from all vendors is paint in the
>> a...
>>
>> I have iLO card in HP ML110 G5 and Virtual Media doesn't work at
>> all. Virtual device is not detected by FreeBSD nor in BIOS, so I
>> can't even boot from it.
>>
>> Virtual Media (console) on Sun Fire X2100 M2 is accessible only by
>> IP address, not by its domain name (I reported it to Sun
>> Microsystems 11 month ago and Sun leaves it unfixed.
>>
>> In Virtual Console of Supermicro, there is problem with keyboard
>> input in sysinstall prior to FreeBSD 8.x
>>
>> So I am disapointed by this hyped feature ;(
>
> Does anyone here find this stuff useful?
Virtual Media is usually crap, in my experience. It's slow as hell and buggy.
> We have a vendor pushing "Virtual Media" on us and I don't see the
> point at all. �I also don't see the point of the screen scraping and
> graphics virtual display support.
>
> I've just started playing with IPMI capable motherboard and another
> system with an IPMI add in card. �Seems like at lot of extra stuff I
> need to disable to secure my operations. �nmap shows ssh, http, https,
> portmap and some other ports of unknown purpose (plus the silly thing
> was configured to send email to the manufacture). �The web interface
> is a little useful, but not when dealing with several hundred systems.
I've never even seen an IPMI web interface. I found IPMI handy (when
it worked) when it came to rebooting a frozen server - although you're
running FreeBSD, so that shouldn't be a problem. ;) It's also nice for
detecting hardware faults. Clearly it's something that needs to be
carefully configured for your environment.
> All I think I really want is basic (secure, encrypted) IPMI 2.0 to
> read system status (power, temperature, fan status, etc) and be able
> to power cycle the thing into a network PXE boot.
>
> The Serial Over Lan stuff looks useful but overly complicated (I come
> from a background where we used terminal servers for console access).
> I would rather see no video board in the system at all, but nobody
> seems to know how to build these boards anymore.
SoL works sometimes. It's another one of those slightly buggy things
that you can't always count on. It *looks* useful, but usually if your
machine is in a bad state - when you need it most - it's not going to
work.
-- randi
Gary Palmer
> So it appears to work if I force the starting sector to be zero. I see the
> same result with an RHEL5 DVD image:
>
> (504) ~ $ sudo umount /mnt
> (505) ~ $ sudo mount_cd9660 -v /dev/cd0 /mnt
> using starting sector 512
> mount_cd9660: /dev/cd0: Invalid argument
> (506) ~ $ sudo mount_cd9660 -s0 /dev/cd0 /mnt
Hi,
I'm no expert at this code, but it might be interesting to see the
results of
cdcontrol -v info
The code in mount_cd9660 in 7.x reads the CD/DVD table of contents
to figure out where the data segment starts. The only thing I can
guess is that the TOC data is getting munged somehow.
Regards,
Gary
Scott Mitchell
> Hi,
>
> I'm having a little trouble using the "virtual media" function of
> Dell's PowerEdge R-series (R710 in this case) iDRAC6 under FreeBSD
> (7.1, 8.0). This is presented as /dev/cd0, a USB/"SCSI" device, I
> guess. This is in the dmesg buffer when I boot up the existing 7.1
> installation with the virtual optical drive mapped to the 8.0-RELEASE
> amd64 DVD image:
>
> umass0: <Avocent USB Composite Device-1, class 0/0, rev 2.00/0.00, addr 2>
> on uhub6 [...]
> cd0 at umass-sim0 bus 0 target 0 lun 0
> cd0: <iDRAC Virtual CD 0323> Removable CD-ROM SCSI-0 device
> cd0: 40.000MB/s transfers
> cd0: cd present [1058105 x 2048 byte records]
> GEOM_LABEL: Label for provider cd0 is iso9660/FreeBSD_Install.
>
> However,
> # mount -t cd9660 /dev/cd0 /mnt
> mount_cd9660: /dev/cd0: Invalid argument
I see exactly the same problem, also on an R710 (very annoying - I had to walk
all the way down the corridor to install 8.0 on it :-)
Messing around with it a bit more post-install, I did discover one interesting
thing:
(501) ~ $ sudo mount_cd9660 -v /dev/cd0 /mnt
Password:
using starting sector 512
mount_cd9660: /dev/cd0: Invalid argument
(502) ~ $ sudo mount_cd9660 -s0v /dev/cd0
(503) ~ $ ls /mnt
8.0-RELEASE/ README.TXT dev/ packages/ sys@
COPYRIGHT RELNOTES.HTM docbook.css proc/ tmp/
ERRATA.HTM RELNOTES.TXT etc/ rescue/ usr/
ERRATA.TXT bin/ lib/ root/ var/
HARDWARE.HTM boot/ libexec/ rr_moved/
HARDWARE.TXT boot.catalog media/ sbin/
README.HTM cdrom.inf mnt/ stand@
So it appears to work if I force the starting sector to be zero. I see the
same result with an RHEL5 DVD image:
(504) ~ $ sudo umount /mnt
(505) ~ $ sudo mount_cd9660 -v /dev/cd0 /mnt
using starting sector 512
mount_cd9660: /dev/cd0: Invalid argument
(506) ~ $ sudo mount_cd9660 -s0 /dev/cd0 /mnt
(507) ~ $ ls /mnt
Cluster/ RELEASE-NOTES-U2-de.html
ClusterStorage/ RELEASE-NOTES-U2-en.html
EULA RELEASE-NOTES-U2-es.html
GPL RELEASE-NOTES-U2-fr.html
README-as.html RELEASE-NOTES-U2-gu.html
README-bn.html RELEASE-NOTES-U2-hi.html
README-de.html RELEASE-NOTES-U2-it.html
README-en RELEASE-NOTES-U2-ja.html
[...]
RELEASE-NOTES-U1-ta.html Server/
RELEASE-NOTES-U1-te.html TRANS.TBL
RELEASE-NOTES-U1-zh_CN.html VT/
RELEASE-NOTES-U1-zh_TW.html eula.en_US
RELEASE-NOTES-U2-as.html images/
RELEASE-NOTES-U2-bn.html isolinux/
(508) ~ $ sudo umount /mnt
Also the same result with a CD (as opposed to DVD) image.
I've no idea if the problem lies in the virtual media driver or in FreeBSD,
but maybe someone who understands these things would like to investigate?
This machine is going into production in a couple of weeks time. I can run
reasonable experiments on it until then, time permitting.
Thanks,
Scott
Scott Mitchell
> Hi,
>
> I'm no expert at this code, but it might be interesting to see the
> results of
>
> cdcontrol -v info
>
> The code in mount_cd9660 in 7.x reads the CD/DVD table of contents
> to figure out where the data segment starts. The only thing I can
> guess is that the TOC data is getting munged somehow.
>
> Regards,
>
> Gary
Hi Gary,
Good call!
On the R710 (running 8.0) with the FreeBSD/amd64 8.0-R DVD image in the
virtual drive:
(501) ~ $ sudo cdcontrol -v info
Password:
Starting track = 1, ending track = 1, TOC size = 4608 bytes
track start duration block length type
-------------------------------------------------
1 0:08.62 144:07.29 512 -662 data
0 0:00.00 - -150 - -
On a different machine (running 6.4) with a real DVD burned from the same
image in the drive:
(501) ~ $ sudo cdcontrol -v info
Password:
Starting track = 1, ending track = 1, TOC size = 18 bytes
track start duration block length type
-------------------------------------------------
1 0:02.00 235:08.05 0 1058105 data
170 235:10.05 - 1058105 - -
Something definitely not right there.
I can try with the same DVD in the internal drive on the R710 tomorrow, just
in case that makes any difference.
Best regards,
Scott