Error registering DS-Series VM with OS disk on Premium Storage

Hi, are there any known issues in relation to backing up DS-series VMs that are created with an OS disk on premium storage? I've
tried testing with two different subscriptions and two different premium storage accounts and get an error when trying to register a DS-series VM which has an OS disk on a premium storage account.
ERROR DETAILS
Microsoft Azure Backup encountered an internal error.
Wait for a few minutes and then try the operation again. If the issue persists, contact Microsoft Support.
I've just created a DS-series VM on a standard storage account and registered it successfully. I haven't tried attaching a premium disk and backing
up yet however.

Yes, VMs with disks on premium storage are not supported right now for Azure Backup. We will be updating our documentation shortly to reflect that limitation.
We will also update the forum when that support is available
Vikas Nahata

Similar Messages

Error registering a Cisco 2811 with a clustered CallManager 4.3

Hello, i'm having problems registering a Cisco 2811 Gateway with a VWIC2-1MFT-E1 interface card with Cisco CallManager 4.3.
The error displayed when debugging mgcp is the following:
//-1/xxxxxxxxxxxx/MGCP/mgcp_mp_get_not_entity(828):[lvl=2]
Invalid parameter (pkt 0x4708C5E8 pkt->mgcp_parm_lines 0x00000000)
I configured mgcp by the following:
mgcp
mgcp call-agent VOIPSVR1 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp restart-delay 300
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp validate call-agent source-ipaddr
mgcp rtp payload-type g726r16 static
mgcp profile default
dial-peer voice 100 pots
service mgcpapp
direct-inward-dial
port 0/0/0:15
Previously, the gateway downloaded xml config files from the Cisco CallManager without problems and, in addition, when trying to add a Route Group (in the CallManager) this Gateway does not appear
in the list of Available Devices although
I have added it through the Device->Gateway Menu.
Need some advice and help. Thank you in advance.

Hi Jose,
The Domain name issue is outlined nicely in this doc;
MGCP Gateway Registration Failure with Cisco CallManager
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00805a316c.shtml#prob
If the IP domain name is configured in Cisco IOS on the MGCP gateway, enter the Fully Qualified Domain Name (FQDN) in the Domain Name field.
In the example: test and cisco.com represent the hostname and domain name respectively. If the IP domain name is not configured in Cisco IOS on the MGCP gateway, enter only the hostname of the MGCP gateway in the Domain Name field.
You would enter test.cisco.com (in CCM)
Hope this helps!
Rob

My MacBook Pro version 10.7.5 4GB (keeps crashing with the error message 'Your MAC OSX start up disk has no more space available for application memory' - what do i do

My MacBook Pro (version 10.7.5 4GB)keeps crashing with the error message 'Your MAC OSX start up disk has no more space available for application memory' - what do i do. I keep force quitting the applications and turning the computer off but it happens again after a while

Hhow much goal and free hard disk space is available? Sounds like you need to move some things off of that hard drive.

Hello, I have a series of language cd's that I am trying to put onto my iTunes but when I download them, they will not save separately instead they are saving as the first disk so i am ending up with 3 disks on 1. Please help

Hello, I am trying to copy a series of language cd's onto iTunes but each cd will not save separately, instead it is saving all as one disk. So I am ending up with 3 disks on 1 with 3 different track1, 2 etc. Please help as I am sure there is an easy solution to this that I have no clue about. Thanks

After you insert the CD but before you import it into iTunes, select all tracks and set the disc number to 1, 2, 3 ... as appropriate.

HT3275 What if my error message is the following: The backup disk image "/Volumes/********'s Time Capsul/****'s MacBook Pro.sparsebundle" is already in use. (I have redacted the name of the computer with asterixes)

What if my error message is the following: The backup disk image “/Volumes/********'s Time Capsul/****’s MacBook Pro.sparsebundle” is already in use. (I have redacted the name of the computer with asterixes)

This is a complex procedure.
Pull the power cord from the back of the Time Capsule
Wait a minute or two
Plug the power cord back in to the back of the Time Capsule
This will fix the issue 98% of the time. If you are in the unlucky 2% category, more help is here from Pondini, the Time Machine guru:
The Backup disk image ... sparsebundle ... is already in use.

Currently cannot burn a dvd or cd post install of snow leopard. Various errors to some times just ejecting the disk with no reason. System was fine prior to upgrading to snow leopard.

Currently cannot burn a dvd or cd post install of snow leopard. Various errors to some times just ejecting the disk with no reason. System was fine prior to upgrading to snow leopard.

MATSHITA DVD-R UJ-857E:
Firmware Revision: ZA0E
Interconnect: ATAPI
Burn Support: Yes (Apple Shipping Drive)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
Write Strategies: CD-TAO, CD-SAO, DVD-DAO
Media: To show the available burn speeds, insert a disc and choose View > Refresh

Dual Layer DVD write error #80020022 - failure to communicate with disk

This only happens on Dual Layer DVDs, and always just as it's finishing. "Communcation with the disk drive failed error code: 80020022"
Used Disk Util and direct burn via finder - both give same error. The image is a .cdr created via DiskUtil, original from a factory cut dual layer DVD, about 7.2GB. The target blank is a "Double Layer DVD+R" Memorex.
The resultant disk is full, but unusable. Re-insertion sees it as a blank disk with no usable space. It wrote something, but certainly not the TOC?
MacBook Pro 2.5, about 6 months old, lastest Leopard
Please - any ideas? Do I have a hardware issue?

Wow - thanks for the quick reply, pullman! I did all of the ideas you listed, no luck. The only way to make this fail is to write to a double sided DVD, I've gone through a stack already just testing/failing. This also fails when writing to a double sided DVD through the finder (then clicking on "burn")
Here's a copy of the console error logs:
http://baxnet.com/bs/picture6.png
-- which indicate a hardware/polling error on the DVD drive itself.
Note that it is complaining about /dev/disk1, which on my system maps to the DVD drive:
Model: MATSHITADVD-R UJ-867
Revision: HA13
Serial Number: HG010865
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: Yes
Thanks again for your help - but still no luck. According to the logs, this may well be a device/hardware problem. Would you suggest a call to Apple support?

I downloaded mavericks but the install failed. The message stated there was an error with the disk which required repairing.

Help please! I downloaded mavericks but the install failed. The message stated there was an error with the disk which required repairing. Using disk utility repair disk is not available ( greyed out) and verify disk stops and says disc requires repairing. So the online support page suggests I erase the disc and reinstall then back up from time machine ( I have a recent backup). But when I try to erase the Macintosh HD I get the message volume erase failed with the error couldn't unmount disk.
I'd be very grateful for any help anyone can give me.
I have a macbook pro 17" mid 2009- running on snow leopard 10.6.8 ... I lost the snow leopard disk so I don't know what to do from there ... I tried restarting by clicking SHIFT (safe mode) after the chime comes up, but It doesnt seem to make any difference ... please help !!
thank you sooo much
many many thanks for your hep guys !!

Whenever you install a new version of OS X being installed, the disk is checked just as if you were using Disk Utility checks the disk to see if the disk is damaged. And,, from what you report, your disk is damaged and needs to be replaced. This isn't a fault with Mavericks - your disk may have been failing for years.
It's a very good thing that you've a recent backup as you're going to need it. I would suggest that you evaluate what functionality that you need in a new disk and go shopping at OWC for a new drive - HGST (or any Hitachi), Seagate SSHDs or Toshiba drives are all good. Be sure that you buy an enclosure for the 'new' drive so that you can format it using Disk Utility before installing it into your machine - you can get one of those from OWC as well.
Good luck - call back with any questions...
Clinton

When login, i see a error message saying " there is a eminent problem with hard disk " smart check

G72-250US Notebook , Win 7 64 Home Premium,
Error :
When i login " There is a eminent problem with Hard disk, SMART check faled" ,Prmary hard disk self test failed .
Please help me with ths problem

Hi,
If this message is coming up in a black screen.
Then the harddrive in the system is about to go bad or already bad.
If you are able to boot to windows, FIRST BACKUP DATA.
Also run a startup test by tapping F2 as soon as you power on the system.
The smart test is a BIOS feature in most of the computer which is designed to keep cust informed if the HDD is about to go bad. But their are instances where the SMART will only let you know that the HDD is bad only when the HDD has bad.
More Info: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01443317&cc=us&dlc=en&lc=en&jumpid=reg_R1002_US...
Although I am an HP employee, I am speaking for myself and not for HP.

I'm having problem with hard disk problem. I recently purchased HP pavilion G series notebook.

There is error displaying that there is a problem with hard disk please back up your data and contact manfature. I purchased these recently in 2011 december in india. Please help me what to do.

The error usually means what it says. Back up your data to a thumb drive or something before it crashes and call HP Support for a hard drive replacement.

Problem with partitioning - disk permanently falls back to old p-table

Hey Guys!
I'm quite desperate and can't find answers for the following problem - maybe some of you already had a similiar problem.
I want to reuse a SSD that I used on a different machine as primary system drive. It's partition-table:
# fdisk -l /dev/sda
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0004f0e5
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 499711 497664 243M 83 Linux
/dev/sda2 501758 250068991 249567234 119G 5 Extended
/dev/sda5 501760 250068991 249567232 119G 8e Linux LVM
There is a LVM volume group with two volumes (root and swap) on sda5. No matter how I try to destroy the LVM setup and the partitioning, it is always "reseted" to this setup.
I tried: lvremove, vgremove, pvremove, fdisk, cfdisk, gdisk, cgdisk, dd from /dev/null, testdisk - with and without reboots, from arch-linux booted from usb and from an ubuntu-live-cd. No matter what, the partitioning does not change.
Why I want to reformat it? I want to use the drive as cache for zfs-on-linux.
It feels like the drive is somehow write-protected.
Has anyone suggestions what to try next?

Thanks @ROOKIE
Sadly didn't work either - see below. Underneath I added results of smart-tests - maybe I miss something.
$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 119.2G 0 disk
|-sda1 8:1 0 243M 0 part
|-sda2 8:2 0 1K 0 part
`-sda5 8:5 0 119G 0 part
sdc 8:32 1 7.4G 0 disk
|-sdc1 8:33 1 512M 0 part
`-sdc2 8:34 1 6.9G 0 part
sdd 8:48 1 7.4G 0 disk
|-sdd1 8:49 1 512M 0 part /boot
`-sdd2 8:50 1 6.9G 0 part
sr0 11:0 1 1024M 0 rom
zram0 254:0 0 75.1M 0 disk [SWAP]
zram1 254:1 0 75.1M 0 disk [SWAP]
zram2 254:2 0 75.1M 0 disk [SWAP]
zram3 254:3 0 75.1M 0 disk [SWAP]
$ sudo blkdiscard -v /dev/sda
/dev/sda: Discarded 128035676160 bytes from the offset 0
$ sudo blkdiscard -v /dev/sda
/dev/sda: Discarded 128035676160 bytes from the offset 0
$ sudo fdisk /dev/sda
Welcome to fdisk (util-linux 2.26.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): o
Created a new DOS disklabel with disk identifier 0x591d429c.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 119.2G 0 disk
|-sda1 8:1 0 243M 0 part
|-sda2 8:2 0 1K 0 part
`-sda5 8:5 0 119G 0 part
sdc 8:32 1 7.4G 0 disk
|-sdc1 8:33 1 512M 0 part
`-sdc2 8:34 1 6.9G 0 part
sdd 8:48 1 7.4G 0 disk
|-sdd1 8:49 1 512M 0 part /boot
`-sdd2 8:50 1 6.9G 0 part
sr0 11:0 1 1024M 0 rom
zram0 254:0 0 75.1M 0 disk [SWAP]
zram1 254:1 0 75.1M 0 disk [SWAP]
zram2 254:2 0 75.1M 0 disk [SWAP]
zram3 254:3 0 75.1M 0 disk [SWAP]
$ sudo blkdiscard -v /dev/sda
/dev/sda: Discarded 128035676160 bytes from the offset 0
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 119.2G 0 disk
|-sda1 8:1 0 243M 0 part
|-sda2 8:2 0 1K 0 part
`-sda5 8:5 0 119G 0 part
sdc 8:32 1 7.4G 0 disk
|-sdc1 8:33 1 512M 0 part
`-sdc2 8:34 1 6.9G 0 part
sdd 8:48 1 7.4G 0 disk
|-sdd1 8:49 1 512M 0 part /boot
`-sdd2 8:50 1 6.9G 0 part
sr0 11:0 1 1024M 0 rom
zram0 254:0 0 75.1M 0 disk [SWAP]
zram1 254:1 0 75.1M 0 disk [SWAP]
zram2 254:2 0 75.1M 0 disk [SWAP]
zram3 254:3 0 75.1M 0 disk [SWAP]
I checked smart too now:
$ sudo smartctl -t long /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Fri Apr 17 12:22:27 2015
Use smartctl -X to abort test.
$ sudo smartctl -H /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
$ sudo smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: JMicron based SSDs
Device Model: KINGSTON SNV425S2128GB
Serial Number: 07WA50010371
Firmware Version: D100309a
User Capacity: 128,035,676,160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Fri Apr 17 12:31:57 2015 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 30) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 1) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Unknown_Attribute 0x0007 100 100 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0
7 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
8 Unknown_Attribute 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 12054
10 Unknown_Attribute 0x0013 100 100 050 Pre-fail Always - 0
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 5448
168 SATA_Phy_Error_Count 0x0012 100 100 000 Old_age Always - 0
175 Bad_Cluster_Table_Count 0x0003 100 100 010 Pre-fail Always - 29
192 Unexpect_Power_Loss_Ct 0x0012 100 100 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 052 100 020 Old_age Always - 52 (Min/Max 29/52)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
240 Unknown_Attribute 0x0013 100 100 050 Pre-fail Always - 0
170 Bad_Block_Count 0x0003 100 100 010 Pre-fail Always - 144 329 118
173 Erase_Count 0x0012 100 100 000 Old_age Always - 6399 10521 7887
SMART Error Log Version: 1
ATA Error Count: 153 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 153 occurred at disk power-on lifetime: 11818 hours (492 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 28 66 d3 eb Error: UNC at LBA = 0x0bd36628 = 198403624
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 28 66 d3 eb 08 36d+21:07:12.000 READ DMA
ec 00 00 00 00 00 a0 08 36d+21:07:12.000 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 36d+21:07:12.000 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 08 36d+21:07:12.000 IDENTIFY DEVICE
c8 00 08 28 66 d3 eb 08 36d+21:07:12.000 READ DMA
Error 152 occurred at disk power-on lifetime: 11818 hours (492 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 28 66 d3 eb Error: UNC at LBA = 0x0bd36628 = 198403624
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 28 66 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 08 20 66 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 08 18 66 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 08 10 66 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 08 08 66 d3 eb 08 36d+21:07:12.000 READ DMA
Error 151 occurred at disk power-on lifetime: 11818 hours (492 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 00 66 d3 eb Error: UNC at LBA = 0x0bd36600 = 198403584
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 00 00 66 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 00 00 65 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 00 00 64 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 00 00 63 d3 eb 08 36d+21:07:12.000 READ DMA
c8 00 00 00 62 d3 eb 08 36d+21:07:12.000 READ DMA
Error 150 occurred at disk power-on lifetime: 6211 hours (258 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 a8 f6 75 eb Error: UNC at LBA = 0x0b75f6a8 = 192280232
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 a8 f6 75 eb 08 04:55:01.600 READ DMA
ec 00 00 00 00 00 a0 08 04:55:01.600 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 08 04:55:01.600 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 08 04:55:01.600 IDENTIFY DEVICE
c8 00 08 a8 f6 75 eb 08 04:55:01.500 READ DMA
Error 149 occurred at disk power-on lifetime: 6211 hours (258 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 a8 f6 75 eb Error: UNC at LBA = 0x0b75f6a8 = 192280232
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 a8 f6 75 eb 08 04:55:01.500 READ DMA
c8 00 08 a0 f6 75 eb 08 04:55:01.500 READ DMA
c8 00 08 98 f6 75 eb 08 04:55:01.500 READ DMA
c8 00 08 90 f6 75 eb 08 04:55:01.500 READ DMA
c8 00 08 88 f6 75 eb 08 04:55:01.500 READ DMA
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 12054 -
# 2 Extended offline Completed without error 00% 11117 -
# 3 Short offline Completed without error 00% 11116 -
# 4 Extended offline Completed without error 00% 11100 -
# 5 Short offline Completed without error 00% 6804 -
# 6 Short offline Completed without error 00% 2818 -
# 7 Short offline Completed without error 00% 2750 -
# 8 Short offline Completed without error 00% 2744 -
# 9 Short offline Aborted by host 00% 2521 -
#10 Short offline Completed without error 00% 2448 -
#11 Short offline Completed without error 00% 2290 -
#12 Short offline Completed without error 00% 2120 -
#13 Short offline Completed without error 00% 2021 -
#14 Short offline Completed without error 00% 1936 -
#15 Short offline Completed without error 00% 1859 -
#16 Short offline Completed without error 00% 1823 -
#17 Short offline Completed without error 00% 1727 -
#18 Short offline Completed without error 00% 1687 -
#19 Short offline Completed without error 00% 1580 -
#20 Short offline Completed without error 00% 1292 -
#21 Short offline Completed without error 00% 1245 -
Selective Self-tests/Logging not supported

I bought few years ago a Creative Suite Design Premium and when I want to register my series number, yours services say that the number is invalid. I very surprise because I used it before on a PC computer that doesn't work anymore. I change my computer

I bought few years ago a Creative Suite Design Premium and when I want to register my series number, yours services say that the number is invalid. I very surprise because I used it before on a PC computer that doesn't work anymore. I change my computer with a Mac. Can You verify the number you customer services gave me, L. Fernandes : <serial num removed-kglad>. I give you my phone number in Paris : <phone num removed - kglad>. Best regard. Chantal

http://helpx.adobe.com/creative-suite/kb/error-serial-number-valid-product.html
p.s. this is a public forum. posting your phone number is a bad idea and posting your serial number will get it banned (or used by someone else and unavailable to you).

Trouble with LaCie disk and time machine

HI everyone,
I've been having trouble with using time machine to back-up to my 1 TB LaCie drive (purchased 5/12, unfornuately I was dumb and didn't register the drive and no longer have the box with the serial number and there is no serial number on my drive. The only problem I had up until the end of August was that every so often the LaCie drive (using my FW 800 port) would unmount after waking up from sleep.
The end of August the drive unmounted for no reason while I was on the computer doing a task. Could not get the LaCie drive remounted (rebooting, etc. etc.) To make a long story short, ended up calling apple care who took me through resetting my SMC and PRAM to no avail. Was booted to higher level of support who walked me through trying to repair my drive using the disk utiltiy. When that didn't work, she walked me through erasing and reformatting the LaCie drive and starting a new time machine back-up. Every thing ok until about ten days ago.
Last week, when I woke my iMac up from sleep, I got an error saying that the disk was not ejected properly and I could not mount the drive. Restarting did nothing, the disk did not mount. Shutting down and rebooting seemed to solve the problem and the disk was mounted. Every so often I've had the problem with the disk unmounting after waking up from sleep before. So, I changed my energy sleep preferences. At the end of the day when I am done, I'd unmount the LaCie drive before putting the Mac to sleep using the apple menu.
Today I came in to start my day, plugged the drive in and it would not mount. Tried rebooting nothing. Went into the disk utility, at first the LaCie drive passed the disk verify (6:26:25 and 6:26:38). Then I went into repair disk on the indented drive at 6:27:13, I wasn't sure what it is was doing, thinking that it had hung, I stopped the repair at 6:27:24. Exited disk utility, and the LaCie drive mounted. But I was getting a read only error when I tried to back-up using time machine. So, I went back into disk utility at 6:27:35, when I verified the disk (indented disk), I got an error saying the disk need to be repaired. After several minutes the disk could not be repaired. So, I erased and reformatted the drive. Ran a time machine back-up and it seemed to back-up everything on my hard drive. Just ran another verify disk and it passed.
Is the drive failing? Have some other back-ups of my documents, my address book, iCal and am going to make a backup of some of my pref files and important e-mail files and am going to do some more back-ups after I am done.
Have reached out to the women at apple care whom I talked to last August, but don't expect to hear back from her for at least 24 hours.
Here is my disk utility log
2013-11-07 06:26:25 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:25 -0500: Starting verification tool:
2013-11-07 06:26:25 -0500: Checking prerequisites
2013-11-07 06:26:25 -0500: Checking the partition list
2013-11-07 06:26:25 -0500: Checking for an EFI system partition
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:25 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:25 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:25 -0500: The partition map appears to be OK
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:38 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:38 -0500: Starting verification tool:
2013-11-07 06:26:38 -0500: Checking prerequisites
2013-11-07 06:26:38 -0500: Checking the partition list
2013-11-07 06:26:38 -0500: Checking for an EFI system partition
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:38 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:38 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:38 -0500: The partition map appears to be OK
2013-11-07 06:26:38 -0500:
2013-11-07 06:26:38 -0500:
2013-11-07 06:27:13 -0500: Disk Utility started.
2013-11-07 06:27:21 -0500: Verifying and repairing partition map for “LaCie”
2013-11-07 06:27:21 -0500: Starting repair tool:
2013-11-07 06:27:21 -0500: Checking prerequisites
2013-11-07 06:27:21 -0500: Checking the partition list
2013-11-07 06:27:21 -0500: Checking for an EFI system partition
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s size
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s file system
2013-11-07 06:27:23 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:27:24 -0500: Reviewing boot support loaders
2013-11-07 06:27:24 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:27:24 -0500: Updating Windows boot.ini files as required
2013-11-07 06:27:24 -0500: The partition map appears to be OK
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:35 -0500: Verifying volume “LaCie”
2013-11-07 06:27:35 -0500: Starting verification tool:
2013-11-07 06:27:35 -0500: Checking file system2013-11-07 06:27:35 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:27:35 -0500:
2013-11-07 06:27:35 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:28:05 -0500:
2013-11-07 06:28:13 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:28:13 -0500: Starting repair tool:
2013-11-07 06:28:13 -0500: Checking file system2013-11-07 06:28:13 -0500: Volume repair complete.2013-11-07 06:28:13 -0500: Updating boot support partitions for the volume as required.2013-11-07 06:35:05 -0500: Stopped by user
2013-11-07 06:44:56 -0500: Disk Utility started.
2013-11-07 06:45:20 -0500: Verifying volume “LaCie”
2013-11-07 06:45:20 -0500: Starting verification tool:
2013-11-07 06:45:20 -0500: Checking file system2013-11-07 06:45:20 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:45:20 -0500: Checking extents overflow file.
2013-11-07 06:45:20 -0500: Checking catalog file.
2013-11-07 06:45:59 -0500: Missing thread record (id = 5057741)
2013-11-07 06:46:06 -0500: Checking multi-linked files.
2013-11-07 06:46:19 -0500: Checking catalog hierarchy.
2013-11-07 06:46:38 -0500: Invalid directory item count
2013-11-07 06:46:38 -0500: (It should be 0 instead of 4)
2013-11-07 06:46:38 -0500: Invalid volume directory count
2013-11-07 06:46:38 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:46:38 -0500: Checking extended attributes file.
2013-11-07 06:47:05 -0500: Checking multi-linked directories.
2013-11-07 06:48:10 -0500: Checking volume bitmap.
2013-11-07 06:48:12 -0500: Checking volume information.
2013-11-07 06:48:12 -0500: The volume LaCie was found corrupt and needs to be repaired.
2013-11-07 06:48:12 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:48:12 -0500:
2013-11-07 06:48:12 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:48:12 -0500:
2013-11-07 06:50:02 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:50:02 -0500: Starting repair tool:
2013-11-07 06:50:02 -0500: Checking file system2013-11-07 06:50:02 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:50:02 -0500: Checking extents overflow file.
2013-11-07 06:50:02 -0500: Checking catalog file.
2013-11-07 06:50:41 -0500: Missing thread record (id = 5057741)
2013-11-07 06:50:48 -0500: Checking multi-linked files.
2013-11-07 06:51:02 -0500: Checking catalog hierarchy.
2013-11-07 06:51:20 -0500: Invalid directory item count
2013-11-07 06:51:20 -0500: (It should be 0 instead of 4)
2013-11-07 06:51:20 -0500: Invalid volume directory count
2013-11-07 06:51:20 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:51:20 -0500: Checking extended attributes file.
2013-11-07 06:51:47 -0500: Checking multi-linked directories.
2013-11-07 06:52:55 -0500: Checking volume bitmap.
2013-11-07 06:52:56 -0500: Checking volume information.
2013-11-07 06:52:56 -0500: Repairing volume.
2013-11-07 06:52:56 -0500: Missing directory record (id = 5057741)
2013-11-07 06:52:56 -0500: Look for missing items in lost+found directory.
2013-11-07 06:53:10 -0500: Rechecking volume.
2013-11-07 06:53:10 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:53:10 -0500: Checking extents overflow file.
2013-11-07 06:53:10 -0500: Checking catalog file.
2013-11-07 06:53:16 -0500: Incorrect number of thread records
2013-11-07 06:53:22 -0500: Checking multi-linked files.
2013-11-07 06:53:35 -0500: Checking catalog hierarchy.
2013-11-07 06:53:53 -0500: Invalid directory item count
2013-11-07 06:53:54 -0500: (It should be 5 instead of 6)
2013-11-07 06:53:54 -0500: Invalid volume directory count
2013-11-07 06:53:54 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:53:54 -0500: Invalid volume file count
2013-11-07 06:53:54 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:53:54 -0500: Checking extended attributes file.
2013-11-07 06:54:20 -0500: Checking multi-linked directories.
2013-11-07 06:55:25 -0500: Checking volume bitmap.
2013-11-07 06:55:26 -0500: Checking volume information.
2013-11-07 06:55:26 -0500: Repairing volume.
2013-11-07 06:58:06 -0500: Rechecking volume.
2013-11-07 06:58:06 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:58:06 -0500: Checking extents overflow file.
2013-11-07 06:58:07 -0500: Checking catalog file.
2013-11-07 06:58:12 -0500: Incorrect number of thread records
2013-11-07 06:58:18 -0500: Checking multi-linked files.
2013-11-07 06:58:31 -0500: Checking catalog hierarchy.
2013-11-07 06:58:50 -0500: Invalid volume directory count
2013-11-07 06:58:50 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:58:50 -0500: Invalid volume file count
2013-11-07 06:58:50 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:58:50 -0500: Checking extended attributes file.
2013-11-07 06:59:17 -0500: Checking multi-linked directories.
2013-11-07 07:00:22 -0500: Checking volume bitmap.
2013-11-07 07:00:24 -0500: Checking volume information.
2013-11-07 07:00:24 -0500: Repairing volume.
2013-11-07 07:03:03 -0500: Rechecking volume.
2013-11-07 07:03:03 -0500: Checking Journaled HFS Plus volume.
2013-11-07 07:03:03 -0500: Checking extents overflow file.
2013-11-07 07:03:04 -0500: Checking catalog file.
2013-11-07 07:03:09 -0500: Incorrect number of thread records
2013-11-07 07:03:15 -0500: Checking multi-linked files.
2013-11-07 07:03:29 -0500: Checking catalog hierarchy.
2013-11-07 07:03:47 -0500: Invalid volume directory count
2013-11-07 07:03:47 -0500: (It should be 166844 instead of 166842)
2013-11-07 07:03:47 -0500: Invalid volume file count
2013-11-07 07:03:47 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 07:03:47 -0500: Checking extended attributes file.
2013-11-07 07:04:14 -0500: Checking multi-linked directories.
2013-11-07 07:05:19 -0500: Checking volume bitmap.
2013-11-07 07:05:20 -0500: Checking volume information.
2013-11-07 07:05:20 -0500: The volume LaCie could not be repaired after 3 attempts.
2013-11-07 07:05:21 -0500: Volume repair complete.2013-11-07 07:05:21 -0500: Updating boot support partitions for the volume as required.2013-11-07 07:05:21 -0500: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 07:05:21 -0500:
2013-11-07 07:05:21 -0500: Disk Utility stopped repairing “LaCie”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
2013-11-07 07:05:21 -0500:
2013-11-07 07:09:45 -0500: Disk Utility started.
2013-11-07 07:11:45 -0500: Preparing to erase : “LaCie”
2013-11-07 07:11:45 -0500:     Partition Scheme: GUID Partition Table
2013-11-07 07:11:45 -0500:     1 volume will be erased
2013-11-07 07:11:45 -0500:         Name        : “LaCie”
2013-11-07 07:11:45 -0500:         Size        : 999.86 GB
2013-11-07 07:11:45 -0500:         File system    : Mac OS Extended (Journaled)
2013-11-07 07:11:45 -0500: Unmounting disk
2013-11-07 07:11:45 -0500: Erasing
2013-11-07 07:11:54 -0500: Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume with a 81920k journal
2013-11-07 07:11:54 -0500: Mounting disk
2013-11-07 07:11:54 -0500: Erase complete.
2013-11-07 07:11:54 -0500:
2013-11-07 10:38:00 -0500: Disk Utility started.
2013-11-07 10:38:12 -0500: Verifying volume “LaCie”
2013-11-07 10:38:12 -0500: Starting verification tool:
2013-11-07 10:38:14 -0500: Checking file system2013-11-07 10:38:14 -0500: Checking Journaled HFS Plus volume.
2013-11-07 10:38:14 -0500: Checking extents overflow file.
2013-11-07 10:38:14 -0500: Checking catalog file.
2013-11-07 10:38:29 -0500: Checking multi-linked files.
2013-11-07 10:38:29 -0500: Checking catalog hierarchy.
2013-11-07 10:38:41 -0500: Checking extended attributes file.
2013-11-07 10:39:04 -0500: Checking multi-linked directories.
2013-11-07 10:39:31 -0500: Checking volume bitmap.
2013-11-07 10:39:32 -0500: Checking volume information.
2013-11-07 10:39:32 -0500: The volume LaCie appears to be OK.
2013-11-07 10:39:32 -0500: Repair tool completed:
2013-11-07 10:39:32 -0500:
2013-11-07 10:39:32 -0500:

I just got a call back from the upper level support person at apple care who had been advising me on my trouble with time machine and my LaCie 1 TB FWD. I had sent her much of the same verbiage as I posted here. As some of you have probably figured out, the verdict is that the drive is probably failing. She says this because I have had to do two erase and reformats. She thought that the intermitant problem that I have had with the drive unmounting when my iMac wakes from sleep could be related to the drive failing.
In the meantime I have a secondary back-up (not using time machine) and the LaCie 1 TB FWD is working for the moment.
Thanks to all who read all my verbiage.
And in the meantime, I've learned something. I marked this question as solved. But I'm open to other things to try.
Message was edited by: njtreehugger minor edits and update

RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE

제품 : RMAN
작성날짜 : 2002-12-09
RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
==========================================================
PURPOSE
이 자료는 Oracle 9.2 이상의 RMAN에서 사용 가능한 MAXSIZE 기능에 대하여
설명할 것이다.
How to restore archive logs with limited disk space
Old Backup을 사용하여 RMAN으로 database를 recvoery할때, 모든 archived
redo logfile들을 Restore할 destination의 disk space가 모자란 경우를 종종 만난다.
이러한 경우 여러 개의 restore and recovery job으로 나누어 수행한다.
즉, 첫 번째 restore and recovery job이 끝나면 archived redo logfile들을 지우고
다음 적용될 것들을 restore한다. 그리고 다시 Recovery를 수행한다. 이러한 작업을
원하는 시점까지 recovery를 하기위해 반복적으로 수행한다.
Oracle 9iR2(9.2.0.x)부터 RMAN은 MAXSIZE option을 제공하는데 이것은 archive log
file이 restore될 disk의 space를 control할 수 있게 해 준다.
만약 disk space가 매우 제한적이라면, 즉 예를 들어 모든 archive log의 size 합보다
disk free space가 적다면 MAXSIZE option을 사용하는 것은 매우 유용하다.
이 OPTION이 기술되면 RMAN은 Media Manager에게 disk space 크기에 부합하는 만큼만
archive log들을 restore하도록 한다. 부가적인 restore operation들은 restore된
마지막 archive log가 적용될 때마다 발생한다.
MAXSIZE option은 이러한 작업들을 하나의 rman job으로 처리하게 해 주고
실수를 하지 않게 해 준다.
아래는 MAXSIZE를 설명하기 위한 예제이며 총 6 단계로 구성되어 있다.
STEP 1: Add data to the database to enforce log switches
STEP 2: Backup the database and archive logs and delete the logs
STEP 3: Add additional data to enforce new log switches
STEP 4: Remove the data file and simulate a database crash
STEP 5: Restore the data file from the backup
STEP 6: Recover the database using MAXSIZE
위 예제는 Unix와 Windows 모두에 적용될 수 있다.
STEP 6 는 다음과 같은 조건으로 두 번 수행될 것이다.
1) MAXSIZE가 archive log size보다 작은 경우:
이 경우 RMAN-6558 Error message를 만나게 된다.
그러므로 MAXSIZE를 archive log보다는 크게 설정해야한다.
2) MAXSIZE가 archive log size보다 큰 경우:
예를 들어 여러 개의 archive log를 포함할 수 있을 정도로 크게 설정하면
restore/recovery는 user에게 transparent하게 수행되어진다.
즉 archive log들은 restore된 후 applied되고 deleted되어 진다. 다시 새로운
archive log들이 restore되어지고 applied된 후 deleted 되어 진다. 이러한 작업은
recovery가 끝날 때까지 반복되어진다. 이러한 작업들이 진행되는 동안 RMAN은
아무런 Message도 발생시키지 않는다.
# Step 1: INSERT enough new data to generate log switches
create table rman_tst (col1 varchar2 (10));
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 2: BACKUP the database and the archive logs automatically
# and then delete the input
run {
backup database format='/web01/usupport/krosenme/admin/backups/db_%d%s%t'
plus archivelog format='/web01/usupport/krosenme/admin/backups/arch_%d%s%t'
delete input;
# Step 3: INSERT enough new data to generate new log switches
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 4: REMOVE users01.dbf file and crash the database
mv users01.dbf users01.org
shutdown abort
# Restore is now needed as the data file is deleted. The backup was
# taken before the new data was added to it, thus archive logs are
# needed to bring the database up to date
# Step 5: RESTORE the data file from the full backup
run {
restore datafile '/web01/usupport/krosenme/oradata/kro_920/users01.dbf';
# Step 6: RECOVER
run {
recover database delete archivelog maxsize 10 K;
# This will fail with RMAN-6558 as the archived log has a size of 16 KB,
# which is bigger than MAXSIZE limit of 10 KB. So the error is expected
# and MAXSIZE works as designed.
# Now rerunning STEP 6: but with MAXSIZE 50 K
run {
recover database delete archivelog maxsize 50 K;
RELATED DOCUMENTS
Recovery Manager Reference, Release 2 (9.2)

cold backup means offline backup, you shut database normally and copy datafiles to another location.
i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
backing up archivelogs whith rman script which is:
run {
allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
change archivelog all validate;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
release channel c1;
so here is the details.
1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
So
first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
and then restore them and then apply them.
we need rman commands to register these backups and restore them.
Regards,
Kamil

Disk Utility has Lost Connection with the Disk Managment Tool

Hi,
For starters, this problem is not associated with the thread that Brian Z. has posted at the top of this forum. Having said that, here's my problem:
I had installed Security Update 2006-003, and Quicktime 7.1. Permissions were repaired before and after each installation, and all went well.
Some hours later, I was experimenting with Apple Remote Desktop. I had activated ARD in the System Preferences>Sharing pane, and it provided me an IP address associated with ARD. I then turned on Airport, and ARD provided me with an IP address associated with that connection. However when I turned off my modem connection, System Preferences>Sharing hung, and had to be Force Quit.
Console Log follows:
===== Mon May 15 2006 ===== 21:09:09 America/Anchorage =====
2006-05-15 21:09:17.488 System Preferences[2732] Can't open input server /Library/InputManagers/Menu Extra Enabler.bundle
2006-05-15 21:09:28.224 System Preferences[2732] ### Error:268435460 File:FileSharing.m Line:308
2006-05-15 21:09:38.230 System Preferences[2732] ### Error:268435460 File:FileSharing.m Line:343
2006-05-15 21:09:48.415 System Preferences[2732] ### Error:268435460 File:FileSharing.m Line:343
Thinking a plist had become corrupted, I trashed the following:
com.apple.systempreferences.plist
com.apple.RemoteDesktop.plist
com.apple.Remotemanagement.plist
com.apple.sharing.firewall.plist.
System Preferences started out very slowly, but then all the panes except Sharing would work ok.
I booted from the install disk and performed a Disk Repair. There were no problems reported.
When I tried to run a Repair Permissions, after about 20 seconds I got the, "Disk Utility has lost connection with the disk management tool and can not continue. Please quit and relaunch Disk Utility."
I quit D.U. and the Installer, and was able to successfully run a Repair Permissions from the D.U. in my Utilities folder. It had no problems to report.
Continuting to troubleshoot the System Preferences problem, I then trashed the com.apple.preferencepanes.cache. This solved my System Preferences>Sharing problem.
However, I am still unable to perform a Repair Permissions after booting from my install disk (I get the subject message). Repairing permissions from the Disk Utility in my Utilies folder works fine.
Any thoughts out there on a logical way to troubleshoot where my problem is? Is there a way to get a console log when I'm running DU from the install disk, or a comparable source??
Thanks,
Bob

I found this crash log that was generated about the time I had problems with System Preferences hanging.
Thoughts?
Bob
Entitled "writeconfig.crash.log"
Host Name: Bobs-Big-Mac.local
Date/Time: 2006-05-15 21:08:17 -0800
OS Version: 10.3.9 (Build 7W98)
Report Version: 2
Command: writeconfig
Path: /System/Library/PrivateFrameworks/Admin.framework/Resources/writeconfig
Version: ??? (???)
PID: 2707
Thread: 0
Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001
Code[1]: 0x90a8d2c0
Thread 0 Crashed:
0 com.apple.Foundation 0x90a8d2c0 _NSRaiseError + 0xf8
1 com.apple.Foundation 0x90a349d8 -[NSConnection sendInvocation:] + 0x6a4
2 com.apple.Foundation 0x90a2d8e0 -[NSObject(NSForwardInvocation) forward::] + 0x198
3 libobjc.A.dylib 0x90866810 objcmsgForward + 0xb0
4 writeconfig 0x0000baac 0x1000 + 0xaaac
5 writeconfig 0x0000ec84 0x1000 + 0xdc84
6 writeconfig 0x0000ad88 0x1000 + 0x9d88
7 writeconfig 0x0000abfc 0x1000 + 0x9bfc
PPC Thread State:
srr0: 0x90a8d2c0 srr1: 0x0202f030 vrsave: 0x00000000
cr: 0x24000442 xer: 0x00000000 lr: 0x90a8d298 ctr: 0x90a23528
r0: 0x00000000 r1: 0xbffff430 r2: 0xa0a204bc r3: 0xa0a34e20
r4: 0x9086eb88 r5: 0x20000000 r6: 0xbffff110 r7: 0x00000000
r8: 0x00000001 r9: 0x0030d370 r10: 0x00000239 r11: 0x28000442
r12: 0x90a23528 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00310680 r25: 0xbffffcd8 r26: 0x00311c50 r27: 0xa0a2af6c
r28: 0xa0a30e7c r29: 0xa0a24ae0 r30: 0x003109a0 r31: 0x90a8d1d0
Binary Images Description:
0x1000 - 0x28fff writeconfig /System/Library/PrivateFrameworks/Admin.framework/Resources/writeconfig
0x80830000 - 0x8090efff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x8c2bc000 - 0x8c2c5fff libBSDPClient.A.dylib /usr/lib/libBSDPClient.A.dylib
0x8fe00000 - 0x8fe4ffff dyld /usr/lib/dyld
0x90000000 - 0x9014ffff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901c0000 - 0x9026efff com.apple.CoreFoundation 6.3.9 (299.37) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x902b0000 - 0x90529fff com.apple.CoreServices.CarbonCore 10.3.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x905a0000 - 0x90610fff com.apple.framework.IOKit 1.3.6 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90640000 - 0x906c8fff com.apple.CoreServices.OSServices 3.0.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90733000 - 0x90740fff com.apple.CommonPanels 1.2.1 (1.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x90810000 - 0x90810fff com.apple.ApplicationServices 1.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x90860000 - 0x908cffff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x908f5000 - 0x90912fff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x90940000 - 0x909b3fff com.apple.DesktopServices 1.2.5 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x90a20000 - 0x90b7bfff com.apple.Foundation 6.3.8 (500.61) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x90d40000 - 0x90d40fff com.apple.Carbon 10.3 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x90d50000 - 0x90d6bfff com.apple.SystemConfiguration 1.7.1 (???) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x90d7c000 - 0x90d8cfff com.apple.speech.recognition.framework 3.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x90dd0000 - 0x90df0fff com.apple.DirectoryService.Framework 1.7.2 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x90e10000 - 0x90e11fff com.apple.ServerControl 10.2.3 /System/Library/PrivateFrameworks/ServerControl.framework/Versions/A/ServerCont rol
0x90e13000 - 0x90e4bfff com.apple.LaunchServices 10.3.5 (98.4) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x90e60000 - 0x90e66fff com.apple.ServerPrefs 10.2.3 /System/Library/PrivateFrameworks/ServerPrefs.framework/Versions/A/ServerPrefs
0x90e80000 - 0x90e9ffff com.apple.MediaKit 2.6 (232.3) /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x90ec0000 - 0x90ec0fff com.apple.Cocoa 6.3 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x9102d000 - 0x91047fff com.apple.openscripting 1.2.1 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x910c0000 - 0x910c1fff com.apple.AFPDefines 2.0.1 /System/Library/PrivateFrameworks/AFPDefines.framework/Versions/A/AFPDefines
0x910e0000 - 0x91134fff com.apple.bom 1.2.7 (64.1) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x91141000 - 0x91141fff com.apple.CoreServices 10.3 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x91230000 - 0x9123afff com.apple.framework.machinesettings 1.3.3 /System/Library/PrivateFrameworks/MachineSettings.framework/Versions/A/MachineS ettings
0x91242000 - 0x9124cfff com.apple.framework.AppleTalk 1.2.0 (???) /System/Library/Frameworks/AppleTalk.framework/Versions/A/AppleTalk
0x91251000 - 0x9125afff com.apple.DiskArbitration 2.0.5 /System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbi tration
0x912e0000 - 0x912f7fff com.apple.LangAnalysis 1.5.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x91303000 - 0x91370fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x913a0000 - 0x9145ffff ColorSync /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x915e0000 - 0x91699fff com.apple.QD 3.4.71 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x916f0000 - 0x91728fff com.apple.AE 1.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x91760000 - 0x917f3fff com.apple.print.framework.PrintCore 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x9194f000 - 0x9194ffff com.apple.audio.units.AudioUnit 1.3.3 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x91970000 - 0x919befff com.apple.print.framework.Print 3.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x91a40000 - 0x91ab3fff com.apple.NavigationServices 3.3.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x91afb000 - 0x91b0bfff com.apple.ImageCapture 2.1.5 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x91b30000 - 0x91b44fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x91b60000 - 0x91b6bfff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x91ba3000 - 0x91bbdfff libresolv.9.dylib /usr/lib/libresolv.9.dylib
0x91bd0000 - 0x91bdffff libPSRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libPSRIP.A.dylib
0x91c00000 - 0x91c13fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x92037000 - 0x92052fff libcurl.2.dylib /usr/lib/libcurl.2.dylib
0x92070000 - 0x92096fff com.apple.FindByContent 1.4 (1.2) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x92170000 - 0x92357fff com.apple.security 2.4 (179) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x927f0000 - 0x92827fff com.apple.CFNetwork 1.2.2 (7) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x9283f000 - 0x92857fff com.apple.WebServices 1.1.1 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x92880000 - 0x92c05fff com.apple.HIToolbox 1.3.7 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x92de0000 - 0x92e30fff com.apple.HIServices 1.4.1 (0.0.1d1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x92e70000 - 0x9336ffff com.apple.AppKit 6.3.10 (743.42) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x93680000 - 0x93958fff com.apple.CoreGraphics 1.203.30 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x939d0000 - 0x939d4fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x93a50000 - 0x93a64fff libcups.2.dylib /usr/lib/libcups.2.dylib
0x93a6a000 - 0x93a84fff libPDFRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libPDFRIP.A.dylib
0x93bec000 - 0x93ca4fff com.apple.audio.toolbox.AudioToolbox 1.3.4 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x94270000 - 0x94333fff com.apple.DiskImagesFramework 10.3.8 (77) /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages
0x94580000 - 0x9458bfff com.apple.securityhi 1.2 (90) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x94593000 - 0x9459ffff com.apple.help 1.0.1 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x945b0000 - 0x945b9fff libz.1.dylib /usr/lib/libz.1.dylib
0x94650000 - 0x946affff com.apple.SearchKit 1.0.2 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x94720000 - 0x94721fff com.apple.securityfoundation 1.0 (6) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x94800000 - 0x9488cfff com.apple.ink.framework 101.1.4 (55.12) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x94e0b000 - 0x94e1efff com.apple.speech.synthesis.framework 3.2 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x95140000 - 0x951b5fff com.apple.DiscRecordingEngine 2.1.17 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingEngine.framework/Versions/A/DiscRecordingEngine
0x954c0000 - 0x95ac6fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x95b20000 - 0x95df0fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x95f00000 - 0x95f20fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x96028000 - 0x960f0fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x968d0000 - 0x969b2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x96a04000 - 0x96a6dfff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x96aa0000 - 0x96acefff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
0x96b50000 - 0x96bdffff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x96c00000 - 0x96c67fff com.apple.audio.CoreAudio 2.1.3 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x96cb0000 - 0x96d9efff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x96de0000 - 0x96df0fff com.apple.vecLib 3.0.3 (vecLib 3.0.3) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x96ee0000 - 0x96ee8fff libbsm.dylib /usr/lib/libbsm.dylib

Error registering DS-Series VM with OS disk on Premium Storage

Similar Messages

Maybe you are looking for