Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?


 
Thread Tools Search this Thread
Operating Systems Solaris Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?
# 1  
Old 10-07-2010
Question Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got
fdisk: "Error in ioctl DKIOCSMBOOT"

Details --

According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:
lrwxrwxrwx 1 root root 110 Oct 6 08:22 c9t6d0s6 -> ../../devices/iscsi/disk@0000iqn.1986-03.com.sun%3A02%3A7baf5e59-8829-44bf-d575
-e8931cf3bb16.watch0001,0:g,raw


When I tried fdisk, on slice 2 or 6 I get:
# fdisk /dev/rdsk/c9t6d0s6
Error in ioctl DKIOCGMBOOT: Invalid argument
No fdisk table exists. The default partition for the disk is:

a 100% "SOLARIS System" partition

Type "y" to accept the default partition, otherwise type "n" to edit the
partition table.

(going through the motions of this ends in the error again when you exit)

When I try any other slice or
c9t6d0s2:c
I get:
fdisk: Cannot open device /dev/rdsk/c9t6d0s2:c

Is it possible to mount any kind of pcfs iSCSI target on a Solaris (sparc) initiator?
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Linux

How to boot iSCSI target from console linux?

I need boot any images from iSCSI and I'd like to boot from linux console of a previous LiveCD booted. Is possible, without gpxe, ipxe firmware or similar? With a simple iSCSI initiator for example? (1 Reply)
Discussion started by: spark2k06
1 Replies

2. HP-UX

Unable to delete iscsi target

Hi Please can someone give me a hint on this, when I list the targets, I see two o them: #iscsiutil -p Operational Target Information ------------------------------ Target # 1 ----------- Target Name : iqn.1992-08.com.netapp:sn.142241859 Target Alias ... (2 Replies)
Discussion started by: fretagi
2 Replies

3. HP-UX

After adding new iscsi target port, still the session state of that target port is showing offline

Hi, I wanted to configure new iscsi port on HPUX system, i added the target port address and configured it, once done, went to array side and searched for that host iqn number , but was nt able to find the same, came to host, then when i ran "iscsiutil -pVS" command it gave me below result ... (0 Replies)
Discussion started by: Vinay Kumar D
0 Replies

4. UNIX for Advanced & Expert Users

Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got fdisk: "Error in ioctl DKIOCSMBOOT" Details -- According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (1 Reply)
Discussion started by: ctafret
1 Replies

5. UNIX for Advanced & Expert Users

LTO2 tape drive as iSCSI target

I'm using Bacula as my backup system, with full backups going to an LTO2 tape drive, while differentials and incrementals go to a disk array on my main server, babylon4. The tape drive is currently attached to a separate machine, because babylon4 does not have a SCSI controller, nor a free PCI-X... (0 Replies)
Discussion started by: Phil Stracchino
0 Replies

6. Solaris

Iscsi - target + initiator on the same host.

Hi all iscsiadm / iscsitadm. Ive created two devices on a host. # iscsitadm list target Target: 1-disk0 iSCSI Name: iqn.1986-03.com.sun:02:f105ddf3-52a4-ed7a-9590-c3d354b8fc32.1-disk0 Connections: 1 Target: 1-disk1 iSCSI Name:... (0 Replies)
Discussion started by: sbk1972
0 Replies

7. Solaris

Solaris 10 10/08 sparc + iSCSI

hi, I have installed Solaris 10 10/08 on sparc machine. I would like to configure iSCSI on that to mount SAN Volumes. Is there any need to install any additional patches for iSCSI to work. Thanks, Prashant. (4 Replies)
Discussion started by: prashantbhushan
4 Replies

8. Solaris

How can I mount a ufs filesystem on a solaris 10 sparc onto a Linux server

Hi there, I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server. *I have re-compiled the linux kernel t support ufs fstype with ro mount support. filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies

9. BSD

Mount Fat32,ext3

Hello All, How can i mount ext3 and Fat partition in FreeBSD 6.0 (0 Replies)
Discussion started by: jaibw
0 Replies
Login or Register to Ask a Question
ISCSI-INITIATOR(8)					    BSD System Manager's Manual 					ISCSI-INITIATOR(8)

NAME
iscsi-initiator -- refuse-based iSCSI initiator SYNOPSIS
iscsi-initiator [-46bcDfVv] [-a authentication-type] [-d digest-type] [-h target-hostname] [-p target-port-number] [-t target-number] [-u username] mount_point DESCRIPTION
The iscsi-initiator utility can be used to access an iSCSI target, such as iscsi-target(8), to access block storage which has been exported. Information pertaining to the target is displayed underneath the mount point, along with the device corresponding to the storage which the target exports. The various arguments are as follows: -4 Use an IPv4 connection to the target. -6 Use an IPv6 connection to the target. -a authentication-type Use the specified authentication type when communicating with the target. The possible values are chap, kerberos, srp or none. The default value is none. -b Show the storage as a block device. -c Show the storage as a character device. -d digest-type Use the specified digest type when communicating with the target. The possible values are header, data, both, all or none. The default value is none. -D List the LUNs on the specified target and exit (i.e. do discovery only) -f Show the storage as a regular file. -h hostname Connect to the iSCSI target running on the host specified as the argument. -p port-number Connect to the iSCSI target running on the port specified as the argument. The default value is 3260. -t target Connect to the number of the iSCSI target running as the argument. -u username Use the specified user's credentials when logging in to the iSCSI target. There is no default. -V Print out the version number and then exit. -v Be verbose in operation. The refuse(3) library is used to provide the file system features. The mandatory parameter is the local mount point. This iSCSI initiator presents a view of the targets underneath the mount point. Firstly, it creates a directory tree with the hostname of the target, and, in that directory, a virtual directory is created for each target name exported by the iSCSI target program. Within that virtual target directory, symbolic links exist for the hostname (for convenience), a textual representation of the IP address, the iSCSI tar- get product name, the iSCSI target IQN, the iSCSI target vendor and version number. One other directory entry is presented in the virtual target directory, relating to the storage presented by the iSCSI target. This can be in the form of a regular file, which is also the default, a block device or a character device. Please note that the iscsi-initiator utility needs the ``puffs'' kernel module loaded via modload(8) to operate. EXAMPLES
# ./iscsi-initiator -u agc -h iscsi-target0.alistaircrooks.co.uk /mnt # ls -al /mnt/target0 total 576 drwxr-xr-x 2 agc agc 512 May 11 22:24 . drwxr-xr-x 2 agc agc 512 May 11 22:24 .. lrw-r--r-- 1 agc agc 39 May 11 22:24 hostname -> iscsi-target0.alistaircrooks.co.uk lrw-r--r-- 1 agc agc 14 May 11 22:24 ip -> 172.16.135.130 lrw-r--r-- 1 agc agc 16 May 11 22:24 product -> NetBSD iSCSI -rw-r--r-- 1 agc agc 104857600 May 11 22:24 storage lrw-r--r-- 1 agc agc 43 May 11 22:24 targetname -> iqn.1994-04.org.netbsd.iscsi-target:target0 lrw-r--r-- 1 agc agc 8 May 11 22:24 vendor -> NetBSD lrw-r--r-- 1 agc agc 4 May 11 22:24 version -> 0 # SEE ALSO
puffs(3), refuse(3), iscsi-target(8) HISTORY
The iscsi-initiator utility first appeared in NetBSD 6.0. An earlier version called iscsifs was available in NetBSD 5.0 in source format only. AUTHORS
The iscsi-initiator utility was written by Alistair Crooks <agc@NetBSD.org>. BUGS
iscsi-initiator currently only supports a CHAP challenge length of 16 octets. Other initiators support up to 1024 and thus it is expected that most targets will also support such lengths. This means that CHAP compatibility with other targets apart from iscsi-target(8) is likely to be poor. To workaround this, please use authentication type none by not specifying a username with the -u option. BSD
February 22, 2011 BSD