Can't mount data CD in KDE

Today, trying to mount a CD in KDE, this error message have appeared:
A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration files (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
I'm annoyed. I don't know what want to say that error.
I have change never any configuration of hal, dbus... and, a weeks ago, i hadn't problems to mount CD in KDE. The normal window saying "what do you want to do", now is missed and only appears that error.
As root, the CD can be mounted, and, music CD are ok as normal user.
I don't know what upgrade "crashed" the system, as there is a lot of time i don't mount a data CD.
I only use current, extra and community for ktorrent and kmldonkey.
Any idea or help?
Thanks!

Well, the solution found:
- add user to group 'storage' (and, may be, to 'optical' - in my case user already belong to this group) and REBOOT (logout was not enough in my case) the system
- remove or comment entries /dev/cdrom, /dev/dvd from /etc/fstab
Thanks to all
But the next trouble found: if CD/Flash/DVD contain non-English characters (for example, Cyriilic) in filenames, they appear as '?????'. Early, I could fix this using 'iocharset=' and 'codepage=' parameters in /etc/fstab. Now I don't use fstab for mount options. There I can set new mount options?
I send the bug report to KDE Team
http://bugs.kde.org/show_bug.cgi?id=133444
And the same problem was posted later
http://bugs.kde.org/show_bug.cgi?id=133456

Similar Messages

One of my partition is not mounted. I can't mount it, can't repair it. I have a lot of data in this partition. I can't erase it, how can I do now? pls help me.

one of my partition is not mounted. I can't mount it, can't repair it. I have a lot of data in this partition, I can't erase it. Please help me.

No way around this. Your phone has to be restored using a computer running iTunes. Make an appointment at an Apple Store to have your device examined by a technician. Or contact Apple Support.

KDE's Dolphin can't mount NTFS partitions after upgrade to systemd

Hi, I just finished to migrate my system to a pure systemd setup. Everithing seems to work fine, except that Dolphin can't mount NTFS partitions anymore, as it was able to do before. I'm not 100% sure that systemd is the culprit, but nevertheless it is a big change in my system so I assume that it may be the problem.
Trying to mount with Dolphin I get this error message:
An error occurred while accessing 'sATA-a', the system responded: The requested operation has failed.: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sdb1': Permesso negato
Failed to mount '/dev/sdb1': Permesso negato
Please check '/dev/sdb1' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
I used to get this kind of error aeons ago when trying to mount from CL; puzzling enough, mounting from CL now works:
$ mount /media/disks/sATA-a
$ ls /media/disks/sATA-a
Documenti Download $RECYCLE.BIN RECYCLER sATA-b System Volume Information Temp Video
This is the relevant entry in my fstab (I don't know if Dolphin cares about it...):
#sATA-a
UUID=D6789B21789B0003 /media/disks/sATA-a ntfs-3g noauto,users 0 0
And finally:
$ ll `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 21 apr 12.13 /bin/ntfs-3g
Can anybody give me a hint? Thanks.

OK, the mess is growing up. Today I switched my laptop to systemd, and the mount problem has appeared on this system as well. So I am confident that this is a systemd-related issue, and maybe some stock Arch config file is broken. I have this entry on my /etc/fstab for the ntfs-3g drive:
UUID=88705BA9705B9D2E /media/vista ntfs-3g noauto,users,exec 0 0
I compiled ntfs-3g with internal fuse support and did the setuid trick:
$ ls -l `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 16 apr 2012 /bin/ntfs-3g
I can mount the disk using the command:
$ mount /media/vista/
$
It works flawlessly, so ntfs-3g works. If I try to mount it with udisks I get:
$ /usr/bin/udisks --mount /dev/sda2 --mount-options users,exec
Mount failed: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sda2': Permesso negato
Failed to mount '/dev/sda2': Permesso negato
Please check '/dev/sda2' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
It sounds to me that udisks is trying to mount the disk as a different user, but I'm not an expert so I might be wrong. If I remove the entry in /etc/fstab then udisks will ask for the password. Repeating the same steps but for an ext3 partition, I am able to mount with udisks when there is a proper fstab entry, and I'm asked for a password when that entry is commented out.
Based on these findings, I strongly suspect that there is some problem with logind configuration in my system. I have been going round and round for hours, serching the web and the wiki (which BTW is in a very bad shape, containing outdated or no informations about mount policies in the polkit and udev sections), and now I feel I need some help to go through it... thanks.

Can't mount my Galaxy Nexus correctly with MTP

Hello everyone,
I am posting because I can't mount my Galaxy Nexus correctly and I am not sure where the problem is. I am glad for any pointers. I am basically following the Arch Linux Guide to MTP, so moving along I get these outputs:
[root@Caduceus parcival]# mtp-detect
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5
Listing raw device(s)
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Found 1 device(s):
Samsung: Galaxy models (MTP+ADB) (04e8:685c) @ bus 4, dev 4
Attempting to connect device(s)
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
USB low-level info:
Interface has a kernel driver attached.
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 04e8
idProduct: 685c
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 4
Device number: 4
Device entry info:
Vendor: Samsung
Vendor id: 0x04e8
Product: Galaxy models (MTP+ADB)
Vendor id: 0x685c
Device flags: 0x48008107
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
Device info:
Manufacturer: samsung
Model: Galaxy Nexus
Device version: 1.0
Serial number: 01498B301401B014
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Unknown (95c1)
95c2: Unknown (95c2)
95c3: Unknown (95c3)
95c4: Unknown (95c4)
95c5: Unknown (95c5)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3001: Association/Directory
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3004: Text
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3005: HTML
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3008: MS Wave
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
3009: MP3
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
300b: MPEG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc48: Description STRING data type READ ONLY
3801: JPEG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
3802: TIFF EP
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3804: BMP
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
3807: GIF
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
3808: JFIF
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
380b: PNG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc48: Description STRING data type READ ONLY
380d: TIFF
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b901: WMA
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
b902: OGG
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
b903: AAC
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc9b: Album Artist STRING data type READ ONLY
dc8b: Track UINT16 data type ANY 16BIT VALUE form READ ONLY
dc99: Original Release Date STRING data type DATETIME FORM READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc8c: Genre STRING data type READ ONLY
dc96: Composer STRING data type READ ONLY
b982: MP4
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b983: MP2
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b984: 3GP
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dce0: Display Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
dc46: Artist STRING data type READ ONLY
dc9a: Album Name STRING data type READ ONLY
dc89: Duration UINT32 data type ANY 32BIT VALUE form READ ONLY
dc48: Description STRING data type READ ONLY
ba05: Abstract Audio Video Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba10: WPL Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba11: M3U Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba14: PLS Playlist
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
ba82: XMLDocument
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
b906: FLAC
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
Special directories:
Default music folder: 0xffffffff
Default playlist folder: 0xffffffff
Default picture folder: 0xffffffff
Default video folder: 0xffffffff
Default organizer folder: 0xffffffff
Default zencast folder: 0xffffffff
Default album folder: 0xffffffff
Default text folder: 0xffffffff
MTP-specific device properties:
Friendly name: (NULL)
Synchronization partner: (NULL)
libmtp supported (playable) filetypes:
Folder
Text file
HTML file
RIFF WAVE file
ISO MPEG-1 Audio Layer 3
MPEG video stream
JPEG file
BMP bitmap file
GIF bitmap file
JFIF file
Portable Network Graphics
TIFF bitmap file
Microsoft Windows Media Audio
Ogg container format
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
ISO MPEG-1 Audio Layer 2
Abstract Playlist file
XML file
Free Lossless Audio Codec (FLAC)
OK.
[root@Caduceus parcival]#
[root@Caduceus parcival]# mtp-connect
Your system does not appear to have UTF-8 enabled ($LANG="en_US.utf8")
If you want to have support for diacritics and Unicode characters,
please switch your locale to an UTF-8 locale, e.g. "en_US.UTF-8".
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Android device detected, assigning default bug flags
Usage: connect <command1> <command2>
Commands: --delete [filename]
--sendfile [source] [destination]
--sendtrack [source] [destination]
--getfile [source] [destination]
--newfolder [foldername]
[root@Caduceus parcival]#
[root@Caduceus parcival]# lsusb
**clipped irrelevant devices**
Bus 004 Device 004: ID 04e8:685c Samsung Electronics Co., Ltd GT-I9250 Phone [Galaxy Nexus]
[root@Caduceus parcival]#
The content of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666"
[parcival@Caduceus ~]$ mtpfs -o allow_other /mnt/galaxy/
Error: Unable to open ~/.mtpz-data for reading.
Listing raw device(s)
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Found 1 device(s):
Samsung: Galaxy models (MTP+ADB) (04e8:685c) @ bus 4, dev 4
Attempting to connect device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
[parcival@Caduceus ~]$
Although it doesn't mount properly, Rhythmbox recognizes and lists the Galaxy Nexus in its GUI. I can even look at the device's properties window. Rhythmbox fails to list any files already on the Galaxy Nexus, though, and I can't transfer anything to it as the following error message in Rhythmbox appears:
Error transferring track
Unable to send file to MTP device: PTP Layer error 02ff: send_file_object_info(): Could not send object info.
Googling for Error 2 brought up some Ubuntu posts from Dec 12 when they had a bug in libmtp 1.1.1, but the current version installed on my system is 1.1.5-1 from the Arch repositories.
Thanks for any help in advance.

@all: so you are basically telling me that my Galaxy nexus should properly mount despite the error messages in my Terminal?
@k.sarend: thank you, I'll try that once I get home.
@mzneverdies: interesting point... I didn't think the choice of the DE would have any impact on mounting devices, that's why I posted in the Kernel & Hardware Support section.
(on a side note: I was a Linux user from 2001-2004 and had KDE as my primary desktop. I just came back to (this time Arch) Linux two weeks ago with a new box and I decided to install Gnome since it seems to have progressed more... but really, I am open for both DEs, I'm not a fanboy/evangelist or anything)

1 of my HD partition suddenly can't mount and want me to initialize! HELP!!

Hi,
If anyone who frequented these kind of problems before please let me know your solutions solving these problems. Thanks very much!!
I'm a musician and a frequent mac user,I have a Power Mac G4 dual 800 with 1.25GMhz ram running on Mac Os 9.21 but with Mac OS X installed (I need to use Mac OS classic due to some of my music softwares still need to be updated before I upgrade to OS X),I've put the Hard Disk in 2 other sub partition HD at the beginning and have been using it to put all my important audio files and songs files. No problems at all before these nightmare started!
The serious problem I'm having now is I suddenly can't mount one of my partition HD anymore.
-I heard weird sound when starting & re-starting the Mac. (Heard some Hard Disk weird sound like sound "crutch" sound" and since the partition can't be mounted, the first thing shows up after I boot the computer is asking me if I wanna Initialize the Hard Disk because it's unreadable. There is 2 choices for me "Cancel" & "Initialize" But there is no effect when I choose "Cancel" so I use the Force Quit.
2 little message saying my Main Hard Disk & the other partition are damaged but they still showing up properly and still running dangerously I think.
-I have tried to start-up by using the installer Disk came with the computer and runs the First Aid Kit to verify the disk. I can see the partition and can see the icon of it but it's just different from others (in a black tone basic classic icon) and after running the verification some following messages appears:
"Mountcheck found serious errors" (in red) then "Overlapped extent allocation,2.60" (in red) and "Hard disk need to be repaired" so I run the Repair mode and it just can't fix because it says it's not been mounted.
I've also checked the main HD and the other partition which sometimes had some problems with it but no problems been found.
-There was few times my computer do Freeze or appears a Bomb asking me to restart when I recording something using the partition for saving the data and a weird sound of hard disk comes before freezing. It seems it's always the same place of the hard disk. Also When I inserted a blank CD-R disk into the drive it just freeze and appears a Bomb message instead asking me if I wanna use the Toast or i-tunes for preparing the disk which I always used to do.
I really hope the computer can hang on just for 1 more month before I have a break to fix everything and backup everything inside or initialize everything inside.
P.S. I've another Powerbook G4 running on OS Tiger but it's mainly for my internet use. ( I don't use internet connection for my PowerMac G4)
And the Combo super Drive is DOWN,I just can't insert any Disk inside anymore. So if having another Mac is helpful for my issue,anything I would try.
Due To I'm having some urgent important jobs now so I really can't initialize or setup other new computers for my works now.
HELP! Thanks!!!

Just because you can't find them does not mean they aren't there.
Freeing Up Space on The Hard Drive
1. See Lion/Mountain Lion/Mavericks' Storage Display.
2. You can remove data from your Home folder except for the /Home/Library/ folder.
3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
4. Also see Freeing space on your Mac OS X startup disk.
5. See Where did my Disk Space go?.
6. See The Storage Display.
You must Empty the Trash in order to recover the space they occupied on the hard drive.
You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

Database can not mount in exchange server 2013 due to Unable to mount database. (hr=0x80004005, ec=-543)

Hello All,
Database can not mount. In this Database domain Administrator mailbox have.
Please suggest. It's very important
The error:
[PS] C:\Windows\system32>Mount-Database -Identity MBX-01 -Force
Confirm
At least one committed transaction log file is missing. Mounting this database will result in data loss. If you can
locate the missing log files, don't continue. Are you sure you want to continue?
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
Failed to mount database "MBX-01". Error: An Active Manager operation failed. Error: The database action failed.
Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database.
(hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x51FF5F0
    Lid: 57728   dwParam: 0x51FF68C
    Lid: 46144   dwParam: 0x51FF709
    Lid: 34880   dwParam: 0x51FF709
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 1c2c8cab-ae3f-40c8-8024-ffc776b22360
    Lid: 35200   dwParam: 0x2EFC
    Lid: 46144   dwParam: 0x51FFA55
    Lid: 34880   dwParam: 0x51FFA55
    Lid: 56264   StoreEc: 0x1388
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: MBX-01, Server: EG-EXCHG-01.ABC.com]
    + CategoryInfo          : InvalidOperation: (MBX-01:ADObjectId) [Mount-Database], InvalidOperationException
    + FullyQualifiedErrorId : [Server=EG-EXCHG-01,RequestId=ca57e784-43c7-4357-9ab6-08881c87bb77,TimeStamp=9/18/2014 5
   :31:08 AM] [FailureCategory=Cmdlet-InvalidOperationException] 51350054,Microsoft.Exchange.Management.SystemConfigu
rationTasks.MountDatabase
    + PSComputerName        : eg-exchg-01.ABC.com

Hi,
This issue indicate corrupted database or corrupted logs. I suggest you to check and repair the database or check and repair the database log.
1. Check the state of database by following command: eseutil /mh "Path of the database"
Ps: Default path of the database is “C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database\Mailbox Database.edb”
Default path of the log files is “C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database\E00”
2. If the state is in clean shutdown, move all the log files from the Transaction logs folder location and then mount the database.
3. If the state is in dirty shutdown, check if the log files that is indicated as Logs required is available or not.
4. You can run Eseutil ml “Path of the log file\e00” to make sure that the log files is required is in a Clean state. This command will help you check the health of all the log files in the location.
5. If the log files are healthy, then try Soft recovery with the command Eseutil /r e00 /l ”Path of log files” /p “Path of the database”
Note:
Make sure you make a backup of the database before attempting any kind of repairs
6. Once the command completes successfully, then mount the database.
7. In case the required log files are not available in a clean state or missing, either restore from a successful back up or perform Hard repair with defragment.
Refer to this file about hard repair:
http://gallery.technet.microsoft.com/Step-by-Step-Exchange-2013-f8bed401
Hope this will be helpful for you

How can I mount / fix my Windows 7 partition?

So a while ago my Win 7 partition was "unmounted" and it wouldnt show up in my Finder. When I tried mounting it in Disk Utility it would never work. I would click Mount, and it would't do anything. I wasn't really bothered by it since the partition would still show up when I booted and held 'alt'. I could boot Windows fine.
I was experiencing some problems with my Mac so I figured I'd reinstall the OS. After I did however, the Win 7 partition didnt show up in the 'alt' boot menu. In Disk Utility, the partition still exists, and I still can't mount it. I honestly have no clue what to do, other than to start over again. I REALLY dont want to do that, becuase I have a lot of data on my Win partition.
So im asking how the flip do i fix this...
Any help is, obviously, very apprechiated.

I think you missed my point. Something you've already done has resulted in corruption of the boot loader or boot block making it impossible for you to now boot from your Windows system via your original Boot Camp installation. Reformatting the Windows partition will just remove everything already installed on it, so that would not sound like a good solution for you.
It may be possible to recover the Windows volume using CampTune, but I don't know that myself. I've not used it. The other possibility is to install a new boot loader:
Boot Runner
The rEFInd Boot Manager - Roderick Smith

Can't mount volume

i've got a second hard drive and in doing some copying and the program coming to some error and crashing (no error reported, but it was while using Carbon Copy Cloner and after the copying was finished.
The disk was showing issues and Disk Repair in Disk Utility said it had a Volume Header error that it couldn't fix. when I have the drive in, I can't even boot up (even though it's not my startup drive) It just sits at a blank, gray screen (as if it's about to show the dark gray apple logo and spinning busy thing at the bottom, but it doesn't.
Sounds like this volume header error is causing the problem, but I dont have a clue on hwo to fix it, since I can't even mount the thing.
What if I was able to boot up with the drive's IDE and power plugged in, but the computer won't try to mount it. Instead, I'll mount it using diskutil at the command line. Maybe if I can mount the correct partition, it will 'ignore' the boot partition and I can get it mounted as a temp fix? I just don't know the /dev/xyz path
EDIT: this kind of makes sense to me... if i can go into single user mode on the good drive, plug the second drive in and then manually mount it. if it works, i can run fsck. thoughts?

I tried your advice and some other things. Here's what I've come up with:
- both hard drives work
- both can be mounted, but NOT AT THE SAME TIME
- having both connected (physically) at startup causes the computer to hang at the gray screen and never displaying anything more (no apple logo either). there's a little pin beside where the IDE cable goes in, and both drives are properly connected as Master w/ Slave and Slave, respectively.
- i can boot into both. in order to make the volume on the 2nd drive, i just had it archive the OS on there and replace it off my OS X cd. I told it to keep the user data for the new installation, but when i got to the login screen, no usernames worked. by default, the clue option wasn't on, so i couldn't even see if it somehow had an old copy of the password file (although i would think that's a stretch)
The only other info I think I've left out is that the second drive's volume still has its original name, so it's not like it somehow got to become literally an exact duplicate of the original, first hard drive's volume (initially, i wondered if that was the case and that the computer thought it was trying to mount the same volume from two locations)

After upgrading to osx 10.9.3, my external hard drive was not able to mount, but it can be mounted without issue in osx 10.6, how do I solve it? it was formatted by disk utility.

Hi
After upgrading to osx 10.9.3, my external hard drive was not able to mount, but it can be mounted without issue in osx 10.6, how do I solve it? it was formatted by disk utility.
Thanks
PT

From the menu bar, select
 ▹ System Preferences ▹ Energy Saver ▹ Power Adapter
and uncheck the box labeled Put the hard disk(s) to sleep when possible, if it's checked.
If the drive has more than one interface (USB, FireWire, Thunderbolt, eSATA), try one of the other interfaces.
Check that the data cable is securely inserted at both ends.
Try a different cable.
If you're connecting the drive through a hub, connect it directly to a built-in port on the Mac.
If you're connecting it directly, try a different port.
Disconnect all other devices on the bus, or as many as possible.
Test the drive with another Mac. Test another drive with this Mac.
If the drive is bus-powered, but has an AC adapter, connect the adapter.
Start up in Recovery mode and launch Disk Utility. Is the drive recognized?
Start up in Safe Mode and test.
Reset the NVRAM.
Reset the System Management Controller.
If the drive doesn't work under any of the above conditions, and if another drive does work with the same Mac, then the drive has failed. You may be able to salvage the mechanism by removing it from the enclosure and installing it in another one, or in a drive dock.

Disk Disaster: SMART status "failing", can't mount - what to do?

Hi,
My GF's PB 12" started getting slow on disk access, so I - suspecting a hard disk failure was impending - checked SMART monitor status, and all seemed fine. Just the same, I made a full backup using SuperDuper.
Now, two weeks later, the drive has failed. Booting from the SD backup, and using Disk Utility to investigate the internal drive shows it as "failing", and the helpful advise is to get the data off as soon as possible. Unfortunately I can't mount the drive...
What is the best way to proceed? Should I just give up, and contact a data recovery service straight away, or is there a better way?

Hello! If you backed up what you thought was an ailing drive didn't you backup your important data every day? Seriously though if it's really important I'd probably check out DATARESCUE. Tom

Can't connect then comes up with can't mount.

People, plugged my perfectly good 4th gen ipod on pc as normally as had been working fine but it asked me to reformat. so, did full restore and when then tried to connect it comes up with same message but when up dater comes up it takes ages before coming up with "can't mount ipod." Making a really loud ticking noise while trying to connect. can see it in windows but can't access disk. Then can't safely remove it and it's still saying do not dis-connect!
any ideas? Please!

re-post this question in the FaceTime for Mac forum.

Updater still "can't mount" while trying to restore

I posted the following in March and got nowhere:
"A few days ago, my iPod nano started to malfunction. It would act if it was continually resetting - it would turn on, display the Apple logo, then turn on, and start over again. I read a post on here that advised to hold down the center button and the play button simultaneously to switch to disk mode, then restore using the updater. This worked - or so I thought.
After doing these steps, it seemed that functionality had been restored. However, I had only loaded two songs on it before my computer acted as if the iPod had disappeared. I turn on the iPod and see the folder icon with the URL to the support site. I can switch it to disk mode, but I can't restore it.
I open the updater and wait for it to prompt me to plug in the iPod. I do this, then wait for it to acknowledge the iPod. Then I press the restore button. It starts to restore, but after a few moments it says "can't mount iPod". I have tried every USB port on my computer, I have tried rebooting my computer, I have tried resetting the iPod. Nothing seems to correct this problem. Please help!"
Someone suggested trying to change the drive letter, but the disc manager says the drive is unreadable. Then he said he would get back to me, but never did. Please, somebody, help me with this.

Hello,
If a sad iPod icon or an exclamation point and folder icon appears on your iPod’s screen, or with sounds of clicking or HD whirring, it is usually the sign of a hard drive problem and you have the power to do something about it now. Your silver bullet of resolving your iPod issue – is to restore your iPod to factory settings.
http://docs.info.apple.com/article.html?artnum=60983
If you're having trouble, try these steps at different levels one at a time until the issue is resolved. These steps will often whip your iPod back into shape.
Make sure you do all the following “TRYs”
A. Try to wait 30 minutes while iPod is charging.
B. Try another FireWire or USB through Dock Connector cable.
C. Try another FireWire or USB port on your computer .
D. Try to disconnect all devices from your computer's FireWire and USB ports.
E. Try to download and install the latest version of iPod software and iTunes
http://www.apple.com/ipod/download/
http://www.apple.com/itunes/download/
F. Try these five steps (known as the five Rs) and it would conquer most iPod issues.
http://www.apple.com/support/ipod/five_rs/
G. Try to put the iPod into Disk Mode if it fails to appear on the desktop
http://docs.info.apple.com/article.html?artnum=93651
If none of these steps address the issue, you may need to go to Intermediate level listed below in logical order. Check from the top of the lists to see if that is what keeping iPod from appearing on your computer in order for doing the Restore.
Intermediate Level
A. Try to connect your iPod with another computer with the iPod updater pre-installed.
B. Still can’t see your iPod, put it in Disk Mode and connect with a computer, instead of doing a Restore on iPod Updater. Go and format the iPod instead.
For Mac computer
1. Open the disk utility, hope your iPod appears there (left hand side), highlight it
2. Go to Tab “Partition”, click either “Delete” or “Partition”, if fails, skip this step and go to 3
3. Go to Tab “Erase” , choose Volume Format as “MAC OS Extended (Journaled), and click Erase, again if fails, skip it and go to 4
4. Same as step 3, but open the “Security Options....” and choose “Zero Out Data” before click Erase. It will take 1 to 2 hours to complete.
5. Eject your iPod and do a Reset
6. Open the iPod Updater and click “Restore”
For Window computer
Go to folder “My Computer”
Hope you can see your iPod there and right click on the iPod
Choose “Format”. Ensure the settings are at “Default” and that “Quick Format” is not checked
Now select “Format”
Eject your iPod and do a Reset
Open the iPod Updater and click “Restore”
In case you do not manage to do a “Format” on a window computer, try to use some 3rd party disk utility software, e.g.“Partition Magic”.
C. Windows users having trouble with their iPods should locate a Mac user. In many cases when an iPod won't show up on a PC that it will show up on the Mac. Then it can be restored. When the PC user returns to his computer the iPod will be recognized by the PC, reformatted for the PC, and usable again. By the way, it works in reverse too. A Mac user often can get his iPod back by connecting it to a PC and restoring it.
Tips
a. It does not matter whether the format is completed or not, the key is to erase (or partly) the corrupted firmware files on the Hard Drive of the iPod. After that, when the iPod re-connected with a computer, it will be recognized as an fresh external hard drive, it will show up on the iPod updater.
b. It is not a difficult issue for a Mac user to find a window base computer, for a PC user, if they can’t find any Mac user, they can go to a nearest Apple Shop for a favor.
c. You may need to switch around the PC and Mac, try to do several attempts between “Format” and “Restore”
Advance Level
A. Diagnostic mode solution
If you have tried trouble shooting your iPod to no avail after all the steps above, chances are your iPod has a hardware problem. The iPod's built-in Diagnostic Mode is a quick and easy way to determine if you have a "bad" iPod.
You need to restart your iPod before putting it into Diagnostic Mode. Check that your hold switch is off by sliding the switch away from the headphone jack. Toggle it on and off to be safe.
Press and hold the following combination of buttons simultaneously for approximately 10 seconds to reset the iPod.
iPod 1G to 3G: "Menu" and "Play/Pause"
iPod 4G+ (includes Photo, Nano, Video, and Mini): "Menu" and "Select"
The Apple logo will appear and you should feel the hard drive spinning up. Press and hold the following sequence of buttons:
iPod 1G to 3G: "REW", "FFW" and "Select"
iPod 4G+ (includes Photo, Nano, Video, and Mini): "Back" and "Select"
You will hear an audible chirp sound (3G models and higher) and the Apple logo should appear backwards. You are now in Diagnostic Mode. Navigate the list of tests using "REW" and "FFW". The scroll wheel will not function while in diagnostic mode. For further details on Diagnostic mode can be found at http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/
Try to do the 5in1, HDD R/W and HDD scan tests. Some successful cases have been reported after the running the few tests under the Diagnostic mode. In case it does not work in your case, and the scan tests reports show some errors then it proves your iPod has a hardware problem and it needs a repairing service.
B. Format your iPod with a start disk
I have not tried this solution myself, I heard that there were few successful cases that the users managed to get their iPod (you must put your iPod in disk mode before connecting with a computer) mounted by the computer, which was booted by a system startup disk. For Mac, you can use the Disk Utility (on the Tiger OS system disk), for PC user, you can use the window OS system disk. Try to find a way to reformat your iPod, again it does not matter which format (FAT32, NTFS or HFS+) you choose, the key is to erase the corrupted system files on the iPod. Then eject your iPod and do a Reset to switch out from Disk Mode. Reboot your computer at the normal way, connect your iPod back with it, open the iPod updater, and hopefully your iPod will appear there for the Restore.
If none of these steps address the issue, your iPod may need to be repaired.
Consider setting up a mail-in repair for your iPod http://depot.info.apple.com/ipod/
Or visit your local Apple Retail Store http://www.apple.com/retail/
In case your iPod is no longer covered by the warranty and you want to find a second repairing company, you can try iPodResQ at your own risk
http://www.ipodresq.com/index.php
Just in case that you are at the following situation
Your iPod warranty is expired
You don’t want to pay any service charges
You are prepared to buy a new one
You can’t accept the re-sell value of your broken iPod
Rather than leave your iPod as paper-weight or throw it away.
You can try the following, but again, only do it as your last resort and at your own risk.
Last Resort Level
1. . Disconnecting the Hard Drive and battery inside the iPod – Warning !! Your iPod warranty will be waived once you open the iPod.
In Hong Kong there are some electronic shops offering an iPod service for Sad iPod, the first thing they do is to open up the iPod’s case and disconnecting the battery and the Hard Drive from the main board of the iPod. Wait for 5-10 minutes and reconnecting them back. The reason behind which I can think of is to do a fully reset of a processor of the iPod. In case you want do it itself and you believe that you are good on fixing the electronics devices and have experience to deal with small bits of electronic parts, then you can read the following of how to open the iPod case for battery replacement (with pictures)
http://www.kokopellimusic.us/KM_instructions.htm
Have I tried this myself? No, I am afraid to do it myself as I am squeamish about tinkering inside electronic devices, I have few experiences that either I broke the parts (which are normally tiny or fragile) or failed to put the parts back to the main case. Therefore, I agree with suggestion to have it fixed by a Pro.
2. Do a search on Google and some topics on this discussion forum about “Sad iPod”
Strange error on iPod (probably death)
http://discussions.apple.com/thread.jspa?threadID=435160&start=0&tstart=0
Sad Face on iPod for no apparent reason
http://discussions.apple.com/thread.jspa?threadID=336342&start=0&tstart=0
Meeting the Sad iPod icon
http://askpang.typepad.com/relevanthistory/2004/11/meeting_thesad.html#comment-10519524
I am not suggesting that you should follow as well, but just read them as your reference. You are the person to make the call.

Can't mount 3rd party DAS storage and Xsan volume simutaneously

Xsan client(MacPro) equipped an Apple FC HBA card can't mount SGI TP9300 DAS storage and Xsan volume simutaneously when powering on or restarting.
Among 2 FC ports, one port is used for Xsan volume using Xserve RAID, and the other port is used for SGI TP9300 storage which is directly connected to that Mac.
When booting, Xsan volume is always mounted normally, but SGI TP9300 volume is not.
Sometimes TP9300 volume is mounted about 20~30 minutes later.(I attached system.log file)
The LUN of TP9300 is seen at Disk Utility, so it's not physical problem.
It seems that actual volume information is not correctly processed at booting time.
While, after booting the system with the FC cable for TP9300 disconnected and confirming that Xsan volume mounted normally, then connecting the FC cable for TP9300, the TP9300 volume is mounted immediately.
Mac OS X 10.4.8, Xsan 1.4 is being used.

Yes, I think you screwed your xsan volume. You can not remove luns from pools, and you can not remove volumes from volumes.
How important is your existing data? In your case I would concentrate on that. This is not trivial. Theorotically you have lost your data allready. In practise you might have luck.
Once I was in your kind of twilight zone, and managed to keep the data. It is a complete cli job. You have to be very carefull about with your config files. You could hire an experienced xsan consultant. If that is not possible, read the manpages very carefully before doing anything on the volume.
Regards
Donald

DiskWarrior can't fix disk, but I can still mount it?

My MacBook kernel panicked the other day while I was using it, so I shut it down, and tried to reboot it. Upon rebooting, the Apple logo will appear and the loading wheel starts to spin, but then it just shuts down.
I then decided to boot into single-user mode which worked fine. I proceeded to run fsck, and was told that I had keys out of order, and the drive couldn't be repaired. My volume can be mounted though, and I can browse through my files in the single-user mode.
I figured that I should probably give DiskWarrior a try. I booted from the DVD which also worked fine, and rebuilt it, but the disk error is still coming up, and it continues to shut down on boot. I even tried the scavenge mode that DiskWarrior has, but it was no use. I've also reset the PRAM, and the SMC.
So what do you guys think I should do next? I thought that if my filesystem was really badly hosed, I wouldn't be able to mount it and browse through it with no problems, but then again DiskWarrior couldn't even make it boot.

I just erased my drive, even zeroed it out. Disk Utility and fsck don't have a problem with my drive anymore. However, my Tiger DVD (which I must install first as I have a Leopard upgrade disc) is giving me an odd error when trying to install.
The installer goes for a little bit, then tells me "There were errors installing the software. Please try installing again". A quick check at the installer log tells me:
"BomFatalError - cpio read error: bad file format"
"Install failed: some files for Essentials may not have been written correctly."
The DVD verification prior to installing passes just fine though. This is really beginning to be a massive headache. Coincidently, while backing up my data onto my PC through SATA, that seems to have gone dead too. I'm stuck with just my iPhone for a computer right now. I can't say I'm a happy camper.

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 >\

Can't mount data CD in KDE

Similar Messages

Maybe you are looking for