Cannot mount USB on Solaris 10 10/08

I inserted the USB drive, I have tried the following, however it didnt work.
devfsadm -Cv
Format>
In format, Im seeing only 1 disk. (that is my harddisk)
0 -> c1todo
I did few more things,
Mount -F pcfs /dev/dsk/c2t0d0p0:c /mnt
How I found out its c2, iostat -En output.
Please someone assist.
Thanks,
Sylvester, Prasanth

& I tried making ZFS file system on pendrive,
zpool create myusb c2t0d0p0
zpool list myusb
Now I can see the file system, however windows doesnt recosgnise it now :( screwd again !!!Right, Windows has no idea what ZFS is so there is no way that it can mount the drive.
In order for it to work on both Windows and Solaris then you need to format the device with a filesystem in common.
The most common way to do this is to format it with a FAT32 filesystem or you could use NTFS if you load up the drivers for it on the Solaris side.
After you format it FAT32 then Windows should have no problems with it since it's a native format and Solaris vold mounts my FAT32 USB devices automatically.
alan

Similar Messages

Cannot mount USB disk in SIngle-user mode (solaris 10)

Hi all ,
I need some help please :
I can read/write to my USB disks when i'm in muti-user mode but when to I swith to single-user mode ( init S ), I cannot mount it.
in Single-user mode , i started volume management daemon :
#/etc/init.d/volgmt start
#volcheck
but i'm still not able to mount it.
I tried to mount manually:
#mount /dev/dsk/c2t0d0p0 /testpoint , i have this error: < mount : not a UFS magic number ( 0x0) , dev/dsk/c2t0d0p0 is not of this fstype.
My system recognizes the USB device though in single-user mode:
This is an output of #iostat -En
c2t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: BUFFALO Product: ClipDrive Revision: 2.00 Serial No:
Size:0.07GB <65339392 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0

Hi ,
thanks for your advice. My problem is resolved.
The USB drive was actually a FAT filesystem.
so I did # mount -F pcfs /dev/dsk/c2t0d0p0:c /testpoint and everything went fine
I can read/write to my USB disks when i'm in
muti-user mode but when to I swith to single-user
mode ( init S ), I cannot mount it.
in Single-user mode , i started volume management
daemon :
/etc/init.d/volgmt start
#volcheck
but i'm still not able to mount it.It probably requires other items to be started
first.
I tried to mount manually:
#mount /dev/dsk/c2t0d0p0 /testpoint , i have
this
error: < mount : not a UFS magic number ( 0x0) ,
dev/dsk/c2t0d0p0 is not of this fstype.
Looks like it's assuming UFS. If this is a pcfs
filesystem, give it the type on the mount line.
# mount -F pcfs /dev/dsk/c2t0d0p0 /testpointYeah, this was the right command, I had to specify option < -F pcfs >.
but I read somethere on this forum i had to specify :c as the drive for FAT at the end of c2t0d0p0 , so the full command was:
# mount -F pcfs /dev/dsk/c2t0d0p0:c /testpoint
>
DarrenThanks,
Sakolan.

Cannot mount root during Solaris install on SPARCengine ULTRA axi

I use boot cdrom which sucessfully formats swp partition and copies files to hd. But then when I reboot I get the following:
SPARCengine(tm)Ultra(tm) AXi (UltraSPARC-IIi 440MHz), PS/2 Keyboard
OpenBoot 3.10.10 ME, 512 MB memory installed, Serial #10660686.
Ethernet address 8:0:20:a2:ab:4e, Host ID: 80a2ab4e.
ok boot disk4
Boot device: /pci@1f,0/pci@1/scsi@1/disk@4,0 File and args:
SunOS Release 5.8 Version Generic_108528-11 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
Cannot mount root on /pci@1f,0/pci@1/scsi@1/disk@4,0:a fstype ufs
panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root
0000000010407970 genunix:vfs_mountroot+70 (10435c00, 0, 0, 10410920, 10, 14)
%l0-3: 0000000010435c00 00000000104391c8 000000002f000000 0000000010435dc0
%l4-7: 0000000000000000 00000000104136b8 00000000000b7bf6 0000000000001bf6
0000000010407a20 genunix:main+94 (10410168, 2000, 10407ec0, 10408030, fff2, 1004
ef88)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000ea5
%l4-7: 0000000010428c28 0000000010462320 00000000000cd920 0000000000000540
skipping system dump - no dump device configured
rebooting...
Resetting ...
PS: I have recently reset the NVRAM on this machine not sure if there are any env settings I should have setup in OBP (I reset HOST ID and MAC-ADDRESS).

disk@0,0:a is slice/partition 0
disk@0,0:b is slice/partition 1
I'm not sure where you told it your swap slice was going to be. Looks like slice 1. Mini-root gets installed in slice 1 and then the install begins from there.
In the future, if you just "boot cdrom" from disk 1 of 2 you won't run into these issues.

[SOLVED] Cannot mount usb (as normal user)

Hello
I'm facing this problem for the first time, but can't tell if it came after an update or an unexpected reboot (light went out).
I'm using latest kde (4.9.2?), and the latest kernel,
Linux gantz 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux
When I plug any usb device, kde ask me what to do. When trying to mount it, either from the kde "mount" plasmoid or from dolphin, I get a "Not authorized" error. Mounting via cli with sudo works fine.
After doing some research, I found that I need to be in the storage group in order to be able to mount, so I checked, and I was already on the storage group. Next.
More research sent me to lots of pages talking abour .xinitrc, wich doesn't exists (on my home, at least). Also tons of pages where talking about somethin like "exec ck-launch-session dbus-launch session-manager" (I login via kdm), but the ck-launch-session is not found on my computer either.
So i'm stucked right now, and don't know how to proceed, any clues? Thanks
Last edited by mzneverdies (2012-11-10 13:10:09)

mzneverdies wrote:
Solved, it was a polkit issue, don't know what caused it, since i didn't touch any config file/dialog.
after changing allow any to "yes" in this section
<action id="org.freedesktop.udisks.filesystem-mount">
<description>Mount a device</description>
<description xml:lang="da">Montér en enhed</description>
<message>Authentication is required to mount the device</message>
<message xml:lang="da">Autorisering er påkrævet for at montere et fil system</message>
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
on file /usr/share/polkit-1/actions/org.freedesktop.udisks.policy, everything came back to normal, and i'm able to mount usb devices.
pd @Raynman: removing myself from the storage group did not change anything.
that's not a fix, it's a crappy workaround. You are not supposed to touch these files, they will be overwritten on an upgrade. My guess is that you are simply not using systemd and therefore you are not in an active logind session. You have to boot with systemd, as mentioned in the news. Everything should then just work out of the box.

[SOLVED][XFCE] Cannot mount usb disks & manage network connections

Hi guys,
I'm using XFCE with 3.3.1-1 kernel. Since yesterday I'm not able anymore to automatically mount usb disks, manage my WiFi networks (networkmanage connects to the default access point but I can't select another AP nor editing my settings). I'm also prompted to type my password when I clik on the shutdown icon;
So it seems I lost some privileges but I can't figured out why...
I still belong to the same grousp as before:
[root@archLaptop sclarckone]# groups sclarckone
lp wheel games video audio optical storage scanner power users
Does anybody has an idea where to take a look?
Thanks
Last edited by sclarckone (2012-04-15 20:54:38)

Me too. Start a new thread?
Edit; Nope, this worked for me https://bbs.archlinux.org/viewtopic.php?id=142110
Last edited by Glinx (2012-05-25 11:44:47)

Mount usb in Solaris 10

Dear friends,
I am using Sun Sparc solaris 10, I am trying to Mount the usb using the following command and i was successfully & able to mount the usb, but now suprisingly i find problem.
the command I used in SU mode is
mount -F pcfs /dev/dsk/c2t0d0s0:c /mnt
mount : no such file or Directory,
please can any tell why i occurs,
Your immediate reply would be more hel[pful for me
Thanks in Advance
Raja

<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
mount -F pcfs /dev/dsk/c2t0d0s0:c /mnt
mount : no such file or Directory
</td></tr></table>
Hello.
1) Check if the device entry /dev/dsk/c2t0d0s0 exists
(by typing ls -L /dev/dsk/c2t0d0s0 - a block file must be displayed)
2) Are you sure the disk is /dev/dsk/c2t0d0s<u><b>0</b></u> and not /dev/dsk/c2t0d0s<u><b>2</b></u>?
3) Make sure that the /mnt directory exists and is not mounted.
I hope this helps.
Martin

Cannot mount USB Hard Drive (750GB LaCie Desktop Hard Disk USB2 K)

I recently purchased a 750GB LaCie Desktop Hard Disk USB2 K, and used it to back-up my NAS (Ready NAS NV+). Now I want to transfer some of this data on the Lacie at a separate location to a Time Capsule, via my MacBook. When I insert the USB cable into TC it seems to recognize the disk, but I cannot see the contents (I have a separate post on this).
WHen I insert the USB cable into my MacBook, I get the message:
"The Disk you inserted was not readable by this computer."
I (THOUGHT) I had formatted the disc as ext3, but do not recall (and cannot access my notes remotely). Is there anyway I can use disk utility to check the formatting, or does the message above give the game away?
Any thoughts appreciated!

I did not think that EXT3 support was built into OS X. There are various utilities around but I do not know how well they work and they would only be useful for the Macbook.
http://ekettoz.blogspot.com/2009/06/mounting-linux-ext2ext3-partitions.html
https://www.paragon-software.com/home/extfs-mac/
Have a look at these.

Domain User cannot mount USB or shutdown

Hello,
after a few weeks when I installed Samba and joined a Domain I realized that when I put in an USB stick my file manager tells me that this operation is not allowed. So I have to mount the USB stick with sudo. Did I make something wrong in the PAM configuration? My domain user is in the local group of storage and power ...
It would be great if some one can give me some direction where to look for the problem.
Regards
Debellator

Thanks for your fast response.
When there is a kernel update I do a restart.
I do not use a login manager.
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
setxkbmap de
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
exec ck-launch-session startlxde

Cannot mount any firewire/USB external drive after software update 10.5.4

After the last software update on 10.5.4 it did not complete the installation, and get stuck at the last step of running installation script for hours. So I have to restart the computer, and it restarted fine. Then I use Disk Utility to check my hard disk, and discovered some file system inconsistency error, so I repaired it (in target disk mode by another Mac). After it is repaired, the file system passed with no error.
But ever since then, I cannot mount any external firewire drive or USB drive. I cannot use Time Machine to backup my disk. I think my firewire and USB ports are fine because I can restart my iMac in target mode and connect to my MacBook via firewire, so the hardwire ports are functional, except that it seems 10.5.4 cannot detect or mount any external drive after the failed software update.
Does anyone encounter similar problem? How can I fix it? I have my disk backed up by TimeMachine but I cannot restore it if it won't let me mount my TimeMachine disk. Is there any other way other than completely reinstall 10.5 from scratch?

first, you should try reinstalling 10.5.4. download the [combo update|http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1054com boupdate.html] and run it. If that doesn't fix the issue, you can use full system restore from TM to go back to a time before the troubles started. to do that boot from the leopard install dvd, once past the language screen go to the Utilities menu at the top and choose "restore from backup".

Cannot mount external USB drive

During a recent update I remember pacman asking about replacing some package with another package to handle disk mounting. I think the added package was "gnome-volume-manager" or "gnome-disk-utility" (or both). I didn't see any postings describing problems with doing this, so went ahead and allowed the change. Now it's a few days later and I find I cannot mount an external USB hard drive anymore. It has an entry in fstab, and although I have tried mutiple edits of the device to associate the drive with, nothing works.
The disk used to associate with /dev/sdb1. Now this device no longer exists. Here is what has happened to my /dev/sd* entries:
brw-rw---- 1 root disk 8, 0 2009-10-27 11:08 /dev/sda
brw-rw---- 1 root disk 8, 3 2009-10-27 11:08 /dev/sda3
brw-rw---- 1 root disk 8, 1 2009-10-27 11:08 /dev/sda1
brw-rw---- 1 root disk 8, 2 2009-10-27 11:08 /dev/sda2
brw-rw---- 1 root disk 8, 4 2009-10-27 11:08 /dev/sda4
brw-rw---- 1 root storage 8, 16 2009-11-04 13:00 /dev/sdb
Trying to force association with "/dev/sdb" "/dev/sda5" (or some other number not in use) or "sdb1" (or 2,3,4, whatever) just yields "special device ... does not exist".
Does anybody know how to deal with this?
Does anybody know what package(s) I replaced when the update in question took place? I think I'd like to reverse whatever happened.
And on another note, I think another gnome-based package also recently replaced a package relating to printing. Yesterday I discovered I have printing problems too:
At first there were no printers found. Although cups is supposed to start according to rc.conf, cupsd was not running. I started it manually and then all the printers showed up again, though I cannot print duplex (again, worked fine before). What is going on with these gnome packages?!? Anyone know which package(s) I need to remove (and then what to put back) to make printing work like it used to also?
thanks much.

oddly, fdisk -l shows nothing, even for disks which are mounted (eg. /dev/sda4). when I insert a standard USB thumb drive, the following show up properly:
brw-rw---- 1 root storage 8, 32 2009-11-05 10:50 /dev/sdc
brw-rw---- 1 root storage 8, 33 2009-11-05 10:50 /dev/sdc1
and I am able to mount and use the drive as usual.
The external drive I've been struggling with has xfs for filesystem type. After using the thumb drive, /dev/sdb showed up spontaneously, but no /dev/sdb1. attempting to mount gives:
mount: /dev/sdb is not a valid block device
or
mount: special device /dev/sdb1 does not exist
depending on which device is specified in fstab.
I am thinking that either a) my ability to mount xfs filesystems has somehow been hosed, or b) there is something wrong with drive, which must have spontaneously failed very recently (it is less than 1 yr old, but this happens from time to time).
If the drive is okay, any ideas about how mounting xfs filesystems could have been broken by recent upgrades?
btw, the fstab entry (which worked fine until a couple days ago) is: /dev/sdb1 /mnt/external_1 xfs rw,noauto,user,exec 0 0

After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md

Hi
I have a SUNW,Netra-440 with two SE 3300 SCSI each with two controllers. The server was working fine but after a boot, it can not see the metadevices stored in the 3300.
I have tried restarting the SE3300 and a boot -r from ok prompt but I still can see those disks or partitions.
Metaset Import
metaset: log01: setname "appvol": no such set
mount all SVM filesystems for group appvol
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d101
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d102
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d103
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d104
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d105
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d106
metaset: log01: setname "dbvol": no such set
mount all SVM filesystems for group dbvol
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d107
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d108
i can see the devices in /dev/md/appvol but i can't mount them.
Any ideas what this could be? using metaset shows nothing, metastat -s dbvol hangs.
Am I missing some patch or am I missing something here? is the SE3300 damaged? or is it a problem with SDS (solstice). I have solaris 9.
The system was working fine until we had to boot and power off to perform power tests in the rack.
thanks
Ryck
this is the output of prtdiag
root@log01 >prtdiag
System Configuration: Sun Microsystems sun4u Netra 440
System clock frequency: 177 MHZ
Memory size: 8GB
==================================== CPUs ====================================
E$ CPU CPU Temperature
CPU Freq Size Implementation Mask Die Amb. Status Location
0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
================================= IO Devices =================================
Bus Freq Slot + Name +
Type MHz Status Path Model
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1,1
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1c,600000/network@2
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1,1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@0
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@2
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@3
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,3f8
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,2e8
pci 33 MB isa/rmc-comm-rmc_comm (seria+
okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
pci 33 PCI0 SUNW,XVR-100 (display) SUNW,375-3290
okay /pci@1e,600000/SUNW,XVR-100
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@a
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@b
pci 33 MB pci10b9,5229 (ide)
okay /pci@1e,600000/ide@d
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1f,700000/network@1
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2,1
============================ Memory Configuration ============================
Segment Table:
Base Address Size Interleave Factor Contains
0x0 2GB 4 BankIDs 0,1,2,3
0x1000000000 2GB 4 BankIDs 16,17,18,19
0x2000000000 2GB 4 BankIDs 32,33,34,35
0x3000000000 2GB 4 BankIDs 48,49,50,51
Bank Table:
Physical Location
ID ControllerID GroupID Size Interleave Way
0 0 0 512MB 0,1,2,3
1 0 1 512MB
2 0 1 512MB
3 0 0 512MB
16 1 0 512MB 0,1,2,3
17 1 1 512MB
18 1 1 512MB
19 1 0 512MB
32 2 0 512MB 0,1,2,3
33 2 1 512MB
34 2 1 512MB
35 2 0 512MB
48 3 0 512MB 0,1,2,3
49 3 1 512MB
50 3 1 512MB
51 3 0 512MB
Memory Module Groups:
ControllerID GroupID Labels Status
0 0 C0/P0/B0/D0
0 0 C0/P0/B0/D1
0 1 C0/P0/B1/D0
0 1 C0/P0/B1/D1
1 0 C1/P0/B0/D0
1 0 C1/P0/B0/D1
1 1 C1/P0/B1/D0
1 1 C1/P0/B1/D1
2 0 C2/P0/B0/D0
2 0 C2/P0/B0/D1
2 1 C2/P0/B1/D0
2 1 C2/P0/B1/D1
3 0 C3/P0/B0/D0
3 0 C3/P0/B0/D1
3 1 C3/P0/B1/D0
3 1 C3/P0/B1/D1
root@log01 >

Hi,
thanks for your answer.
Yes format displays the physical devices, but metadb -i only shows the internal disks of the netra 440, not the ones in the 3320. metadb -s dbvol -i doesnt show anything.
metaset which is supposed to show me the metadevices, says the program is not registered.
cat /etc/lvm/md.tab has the configuration but since the scsi can be seen, the devices aren't mounted.
Any suggestions?
Cheers
Oscar
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootdisk
/pci@1f,700000/scsi@2/sd@0,0
1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootmirr
/pci@1f,700000/scsi@2/sd@1,0
2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare1
/pci@1f,700000/scsi@2/sd@2,0
3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare2
/pci@1f,700000/scsi@2/sd@3,0
4. c2t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> appvol
/pci@1c,600000/scsi@1/sd@8,0
5. c2t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol01
/pci@1c,600000/scsi@1/sd@9,0
6. c2t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol02
/pci@1c,600000/scsi@1/sd@a,0
7. c2t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol03
/pci@1c,600000/scsi@1/sd@b,0
8. c2t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol04
/pci@1c,600000/scsi@1/sd@c,0
9. c2t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol05
/pci@1c,600000/scsi@1/sd@d,0
10. c3t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol06
/pci@1c,600000/scsi@1,1/sd@8,0
11. c3t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1
/pci@1c,600000/scsi@1,1/sd@9,0
12. c3t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2
/pci@1c,600000/scsi@1,1/sd@a,0
13. c3t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3
/pci@1c,600000/scsi@1,1/sd@b,0
14. c3t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotAPP
/pci@1c,600000/scsi@1,1/sd@c,0
15. c3t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDB
/pci@1c,600000/scsi@1,1/sd@d,0
16. c4t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> APPVOLm
/pci@1d,700000/scsi@1/sd@8,0
17. c4t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@9,0
18. c4t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@a,0
19. c4t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@b,0
20. c4t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@c,0
21. c4t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@d,0
22. c5t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> d6Mirr
/pci@1d,700000/scsi@1,1/sd@8,0
23. c5t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1M
/pci@1d,700000/scsi@1,1/sd@9,0
24. c5t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2M
/pci@1d,700000/scsi@1,1/sd@a,0
25. c5t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3M
/pci@1d,700000/scsi@1,1/sd@b,0
26. c5t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1,1/sd@c,0
27. c5t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDBm
/pci@1d,700000/scsi@1,1/sd@d,0
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >metadb -s appvol -i
metadb: log01: setname "appvol": no such set
root@log01 >metaset
metaset: log01: metad client create: RPC: Program not registered
root@log01 >cat /etc/lvm/md.tab
# Copyright 2002 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)md.tab 2.4 02/01/29 SMI"
# md.tab
# metainit utility input file.
dbvol/d57 1 1 c2t12d0s0
dbvol/d58 1 1 c4t12d0s0
dbvol/d4 -m dbvol/d57 dbvol/d58 1
dbvol/d55 1 1 c2t11d0s0
dbvol/d56 1 1 c4t11d0s0
dbvol/d3 -m dbvol/d55 dbvol/d56 1
dbvol/d61 1 1 c3t8d0s0
dbvol/d62 1 1 c5t8d0s0
dbvol/d6 -m dbvol/d61 dbvol/d62 1
dbvol/d59 1 1 c2t13d0s0
dbvol/d60 1 1 c4t13d0s0
dbvol/d5 -m dbvol/d59 dbvol/d60 1
dbvol/d53 1 1 c2t10d0s0
dbvol/d54 1 1 c4t10d0s0
dbvol/d2 -m dbvol/d53 dbvol/d54 1
###dbvol/d51 1 1 c2t9d0s0
dbvol/d52 1 1 c4t9d0s0
#dbvol/d1 -m dbvol/d51 dbvol/d52 1
dbvol/d1 -m dbvol/d52 1
# SOFT Partitions
dbvol/d129 -p dbvol/d5 -o 19933376 -b 526336
dbvol/d128 -p dbvol/d5 -o 19407008 -b 526336
dbvol/d127 -p dbvol/d5 -o 18880640 -b 526336
dbvol/d126 -p dbvol/d5 -o 10489952 -b 8390656
dbvol/d125 -p dbvol/d5 -o 2099264 -b 8390656
dbvol/d123 -p dbvol/d4 -o 4724864 -b 133120
dbvol/d122 -p dbvol/d4 -o 4460640 -b 264192
dbvol/d121 -p dbvol/d4 -o 4196416 -b 264192
dbvol/d120 -p dbvol/d4 -o 32 -b 4196352
dbvol/d119 -p dbvol/d3 -o 30972032 -b 526336
dbvol/d118 -p dbvol/d3 -o 10489952 -b 20482048
dbvol/d117 -p dbvol/d3 -o 4196416 -b 6293504
dbvol/d116 -p dbvol/d3 -o 32 -b 4196352
dbvol/d115 -p dbvol/d2 -o 8925408 -b 526336
dbvol/d114 -p dbvol/d2 -o 8399040 -b 526336
dbvol/d113 -p dbvol/d2 -o 7872672 -b 526336
dbvol/d112 -p dbvol/d2 -o 7346304 -b 526336
dbvol/d111 -p dbvol/d2 -o 5247072 -b 2099200
dbvol/d110 -p dbvol/d2 -o 1050688 -b 4196352
dbvol/d109 -p dbvol/d2 -o 32 -b 1050624
dbvol/d108 -p dbvol/d1 -o 33554496 -b 1572864
dbvol/d107 -p dbvol/d1 -o 32 -b 33554432
dbvol/d124 -p dbvol/d5 -o 32 -b 2099200
dbvol/d138 -p dbvol/d4 -o 38416608 -b 133120
dbvol/d137 -p dbvol/d3 -o 31498400 -b 264192
dbvol/d136 -p dbvol/d4 -o 21637312 -b 16779264
dbvol/d135 -p dbvol/d4 -o 4858016 -b 16779264
dbvol/d134 -p dbvol/d6 -o 69212288 -b 23070720
dbvol/d133 -p dbvol/d6 -o 46141536 -b 23070720
dbvol/d132 -p dbvol/d6 -o 23070784 -b 23070720
dbvol/d131 -p dbvol/d6 -o 32 -b 23070720
dbvol/d130 -p dbvol/d5 -o 20459744 -b 526336
root@log01 >metadb -s dbvol -i
metadb: log01: setname "dbvol": no such set
root@log01 >\

Mounting usb devices as non-root user ??

How can a non-root user mount a usb flash device?
As root, the device is mounted as:
mount -F pcfs /dev/dsk/c1tod0s2:c /mnt
The vfstab entry for this is as follows:
/dev/dsk/c1t0d0s2:c /dev/rdsk/c1t0d0s2 /flash pcfs 2 no -
This is running Solaris 8 on a SunBlade150

Hello.
I had the same problem.
If you do not have root rights on the computer the answer is: You cannot mount the device.
I had root access and I wrote a C program that (un-)mounted all possible device files (the "s2" devices as well as the "s2:c" devices because some flash devices come without partition table).
I chowned the file to root and set the "set effective user ID" bit in the file's permissions using chmod after logging in as root - so any user can start the program.
I think this is the most flexible variant because USB devices sometimes are assigned other device names.
Martin

Disk Utility says everything's fine, but Install disk doesn't find my internal drive as a possible destination. When I startup with Command S, I get a looping "cannot mount errno = 19" message.

Disk Utility says everything's fine, but Install disk doesn't find my internal drive as a possible destination. When I startup with Command + S, I get a looping "cannot mount errno = 19" message.
Problem started when I used Tech Tool Pro 6 to "de-fragment volume". Had to cancel that process before it finished because I ran out of time. Thereafter, when I startup my machine normally, I get the gray Apple logo at first, but it changes to a prohibited symbol (circle with a slash thru it) and hangs.
When I startup holding the Option key, I can see my internal drive, but I get the same results as above.
When I startup using the MacBook OSX Install DVD, it does not find my internal drive as possible destination.
When I startup using the MacBook OSX Install DVD and then run Disk Utility, it finds my drive, allows me to "repair" and says everything is fine.
When I startup with Command + S, I get a looping error message "errno = 19" and cannot stop it to do anything else.
When I startup from Disk Warrior v4.4, it does not find my internal drive to do any repairs.
When I startup from Tech Tool Pro 6 and run the "computer check" diagnostics, everything passes but the Volume Structure, which fails at "Volume Extents (B-tree)." When I use TTP's "Tools" option to run "volume repair" it will show my internal drive and allow me to click the GO button, but nothing happens and nothing changes.
I have a Time Machine backup on an external USB drive, but for as long as the internal drive doesn't mount, I can't use the backup to restore.

It's a false report and should be ignored.
I would not rely on TT as I've already said earlier even before Grant posted similar advice.
I really think the Rigid Disk Block may be corrupted. This holds the partition map and could prevent a volume from being unmounted. Unfortunately, there is no way to fix that without repartitioning the drive which will remove everything. So, before going down this road I hope you have backups or can make a backup.
Drive Partition and Format
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Proceed with reinstalling OS X.
5. Download and install Mac OS X 10.6.8 Update Combo v1.1.

Mount NTFS under Solaris 10

Hi can anybody tell me if i can mount a NTFS partition under Solaris 10??
Thanks for ur help.

<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>korsabad wrote on Wed, 11 January 2006 06:23</b></td></tr><tr><td class="quote">
if you use solaris x86 and the ntfs-partition
Not possible. NTFS has those windows-security-id's (you know, those about-40-character-long-id's) for each object which cannot be read from solaris.
</td></tr></table>
I think writing to NTFS is nearly impossible (due to changes of the NTFS version, security stuff, and so on).
However reading from an <u>unencrypted</u> NTFS partition seems to be a possible thing. I do not know if a tool or a driver <u>already</u> exists but I think it is a possible task to write a tool that reads from NTFS partitions.
I think writing a tool that reads from UFS partitions under Windows is an easy task, too. I wrote such a tool for reading the EXT2 file system under Windows long time ago.
Martin

10.9: cannot mount westerndigital drive usb3 external, but in 10.8 yes

please why is my text shown on white background? can i change this?
i could not mount my 2 external wd drives (mypassport 2,5" 2TB)
(USB3.0) since install of 10.9 on my 2 brand new macs. (imac 27" i5 late 2013 and mbair i7 mid 2013)
before, with 10.8 it worked fine!
i thought the wd drive is faulty, so i got a new one by warranty, and sent the "old" back. it took only 5 days to get the swap by wd.
i could not mount the new drive either under 10.9
but today i installed techtool pro 7.0.2, did nothing but a reboot and after that, i plugged it into my imac with 10.9, it mounted correctly on my imac, the first time ever! and showed a techtool symbol as drive symbol instead of the orange colored usb symbol.
appearantly techtool pro 7.0.2 installed something into 10.9 which helps the system mount discs?
- i never did lock the drive with the wd security app
- before that, i tried to remove all wd related stuff and uninstalled every single wd app and driver, still no mount !
- before that, apple disctools under 10.9 did not show the drives in the left column, as no other harddisc app did. (drive genius)
- i can mount both drives on the old mbair with 10.8, my wife´s mac
- wd drive utilites would show the disc, but not mount, if i tried to format it, it showed an error after 1min: cannot format disc,
as it cannot be mounted. (or so..)
- now, after install of techtool pro 7.0.2, when i plug the drive into my imac, it is mounted correctly, but there is
always another volume mounted by default "wd drive unlock volume" which says "your wd drive is not locked, so you can not unlock it)
weird?
i still cannot mount the wd drive on my new macbook air with 10.9,
etre check lists as difference:
imac:
Kernel Extensions:
com.wdc.driver.USB.64.10.9 (1.0.1 - SDK 10.9) (today mount possible for the first time since weeks)
macbook air:
no wd driver at all (and no mount possible)
any idea?
thanks
Message was edited by: peppermint

first, you should try reinstalling 10.5.4. download the [combo update|http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1054com boupdate.html] and run it. If that doesn't fix the issue, you can use full system restore from TM to go back to a time before the troubles started. to do that boot from the leopard install dvd, once past the language screen go to the Utilities menu at the top and choose "restore from backup".

Cannot mount USB on Solaris 10 10/08

Similar Messages

Maybe you are looking for