Unable to create a filesystem on an USB-stick

Hello,
since the switch to SL I can't create a filesystem on my USB-sticks with the disk utility, no matter what kind of filesystem (HFS+, FAT...).
Repair of permissions was unsuccessful.
Anybody an idea?
Thanks
matze

Do the following:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

Similar Messages

Can you burn what you create in idvd to a usb stick or sd memory card

Can you burn what you create in idvd to a usb stick or sd memory card and if so how?

on iDVD, click HELP on the menu bar.
Than click iDVD Help
Than click: Saving a project and burning a DVD
Than click at "saving a projekt" Creating a disc image of a project
Follow the instructions
Choose USB drive or menory card as target.
Lupunus
Edit: If you want the image as ISO on your drive, use disk utility to create a CD/DVD master from the image and rename the file extension movie.cdr afterwards from cdr to iso
Message was edited by: lupunus

Unable to create new filesystem

Hi all,
I am trying to create new filesytem in solaris 9 machine(HP Proliant hardware).
I have partitioned using format command and below is the output,
Current partition table (unnamed):
Total disk cylinders available: 6047 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 64 502.03MB (64/0/0) 1028160
1 swap wu 65 - 319 1.95GB (255/0/0) 4096575
2 backup wm 0 - 6046 46.32GB (6047/0/0) 97145055
3 unassigned wm 320 - 321 15.69MB (2/0/0) 32130
4 unassigned wm 322 - 832 3.91GB (511/0/0) 8209215
5 var wm 833 - 5602 36.54GB (4770/0/0) 76630050
6 usr wm 5603 - 5921 2.44GB (319/0/0) 5124735
7 home wm 5922 - 6036 902.09MB (115/0/0) 1847475
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
I have made entries in /etc/vfstab and below are the entries:
# vi /etc/vfstab
"/etc/vfstab" 14 lines, 720 characters
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s1 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no
/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /var ufs 1 no
/dev/dsk/c0t0d0p0:boot - /boot pcfs - no -
/dev/dsk/c0t0d0s7 /dev/rdsk/c0t0d0s7 /export/home ufs 2
yes -
/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /opt ufs 2 yes
swap - /tmp tmpfs - yes -
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /kameleon ufs 2 no
logging
When i try to create filesystem using newfs command, i am getting the I/O error as shown below,
# newfs /dev/rdsk/c0t0d0s6
/dev/rdsk/c0t0d0s6: I/O error
Please help me to get rid of this error for creating fs.
Regards

Check you /etc/vfstab entry for s6
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr
It is mounted to /usr. You cannot created filesystem on a live volume.

Making a Windows 7 Installation USB Stick

This is a discussion of making a bootable Windows 7 Installation USB-stick Media. It might apply to making other USB connected "Disks" like Smartcards bootable too.
I recently had to do this (a Laptop with no build-in DVD drive and no USB DVD drive around). And it turned out to be surprisingly simple, using nothing but build in Windows tools from the Disk. I only found
this german langauge guide and nothing in english (but I might just have searched after the wrong terms, google has been wierd regarding langauge lately), so I thought I write it up (along with some problems I ran into).
Making a USB-Stick into a bootable Windows 7 (and propably Vista) Media is a 3 step process:
1. Create a Active, Primary, FAT32 Partition of 4+ GB on the stick
2. use bootsect.exe from Windows Disk to create the MBR and Partition Boot Record for that Partition
3. Copy all files from the Disk to said Partition
4. Test if it boots
Detail analysis:
Step 1 is so simple I doubt it needs explanations. Create enough free space on the USB disk (at worst delete all previous Partitions). Make a Priamry Partition of 4+ GiB. Mark it as Active. Format it in FAT32. The Guide used Diskpart,
but this step can be done with any Partition Tool under any Windows, Linux, UNIX or DOS.
While the choice of FAT32 seems a bit outdated, theye propably did not gave the relevant bootlaoder the ability to read NTFS. Or maybe they just though FAT32 is enough for a media that is mostly read. I have not tried what happens if I format it in NTFS, but
it might be possible.
Step 2 was the only tricky part. You need the programm "boot\bootsect.exe" from the Installation Media. It also must be run on a non-UEFI booted OS (otherwise it cancels out).
I had a Windows 8 on a new Laptop so I had a UEFI booted system. Luckily I also had a VMWare Windows 7 lying around. I just assigned the Windows 7 ISO image to the Windows 7 VM, then connected the USB drive to the host.
Once you have the USB stick in a a proper Windows mount the Parttion you created under 1 under any driveletter (should happen automatically under Windows), and open a console as Administrator (asumes DVD is drivletter is D: and the USB stick's partition
ins Driveletter E:):
//Go into the boot directory on the Install DVD
D:
cd boot
//You should see a command promt like "D:\BOOT>"
//Run bootsect.exe
bootsect.exe /nt60 d:
Step 3 is to either copy the contents of the DVD media (copy and paste) or the Image (Mount into Virtual DVD Drive and copy/paste, unpack ISO images contents) into the partition.
How does this compare to other Distribution ways?
To DVD:
There is no need for a DVD drive. Even if a bootable USB-DVD drive is avalible, the Stick or Card will only need only USB port (most USB drives need 2 Ports due the 1 Ampere energy need of the drives).
Flash Media has no seek times and much better throughput (the old weakpoint of any Disk and DVD/CD in particular)
A FAT32 partition is inherently writeable. So modifications to the "Installation media" like Implementing Service Packs and other Windwos Updates, Modifying ei.cfg/preactivation/setup answer files, implementing special Disk/RAID drivers into the Windows
PE or adding stuff that should be installed with Windows is easy (and do not requrie reburning a 4 GiB Image file).
Since it only needs a 4 GiB partition, on a big USB stick there would still be place for other Data Partitions
Since it relies on old techniques (Generic Bootloader + Active Primary Partition + partition boot loader), multiple Installation media on a big enough stick might be feasible (with a more advanced bootloader like GRUB). Have to test that part.
However, the cost/media is a lot higher then a DVD. So if you need multiple Medias it will propably be cheaper to use the old DVD approach.
Due to the needs of bootsec.exe, first creating the media can be more difficulty then just burning an image. But once it is bootable this programm is no longer needed.
To PXE/network Distrubution:
If you have the nessesary setup already (DHCP/PXE Server, powerfull network), the USB stick is likely inferior. The USB stick should beat a 100 MBIT Network easily, but will propably be beaten by a 1 GBIT Network. Network isntallation uses existing infrastructure
(that you need for other reasons anyway) so the cost per media is even lower then the DVD.
The PXE way also has even better modifyability - sending out different answer files or even automatically booting different images based on the Compuers MAC adress are tried techniques.
If you lack the nessesary setup, the USB stick is a lot easier to implement and a lot easier to transport.
Advanced things:
Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
Need to check if using a advanced boot manager techniques (like Grub or modifciations to the BCD of the Windows PE) allows me to put multiple install media on one Stick (with one primary partition per "media"). Especially combining the x32/x86 and
x64 Windows Installation Media would be worthwhile. As would be inlcuding a Window 8 or Vista installation media.
Current Step 3 and 2 can propably be switched. I see no reason bootsect could not run from the USB stick as it runs from the DVD (it only accesses the MBR and
VBR of the Disk, areas not in use by Windows)
Steps 1 through 3 might be possible from the Windows PE environment. If so, only a computer with legacy BIOS boot would be nessesary (no actuall installation).
Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary.
Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

Advanced things:
Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary.
I converted the stick to NTFS using the convert.exe and it continued booting. So chances are high they only choose FAT32 in the example because no feature of NTFS was per nessesary in a "almost only reading" scenario like installation media.
The second part depends on the BIOS. I have a more advanced one where I can choose legacy boot options (like USB stick) in the boot option menu even when the default setting is UEFI, as long as I don't need Secure boot (wich I do not).
Another question arose: Windows 7 has the Kernel/BCD level ability to boot from .VHD Files. The only thing preventing version below corporate from using this feature is a license check that is run just before the login (so way after the booting has been
completed).
Starting with 3.0 Windows PE is based on the kernel of Windows 7. So the instlaltion system might have the ability to boot from .VHD too and might have no such check in place. If so, I could put both versions of the Windows 7 installer into .VHD, reducing the
need to have physical primary partitions for those.
Windows bootprocess vs. Linux boot process under BIOS:
The BIOS goes over all the boot media. If it finds one with a MBR, that one is executed and the BIOS part of the boot process is officially over.
-> Under Windows the MBR contains the "generic boot loader". A simple piece of code as old as BIOS (25 Years) that looks for the primary partition with "Active" Flag on "it's" disk. If it finds one, the Partition Boot Record of that parition is executed.
The MBR has done it's part
    -> NTLDR (NT too 2000), this one reads the boot.ini file and gives/executeds apropirate options
    -> BOOTMGR (Vista, 7), this one reads the BCD files
      -> Since Windows 7 BOOTMGR can also chainload the Partition Boot Record that is inside a .VHD File
    -> Wicher was used in Windows 3.X/95/98/ME
Higher versions can chainload lower versions, but must be designed for this and (re)installed in the proper "order".
The sometimes odd behavior that Windows 7 tries to keep 100 MiB in a seperate primary partition is there to have proper places for later additions to the BOOTMGR settings. Specifically it allows multiple BOOTMGR OS to use/edit the same BOOTMGR instace without
running into problems with "whose partition is active?" (since it is always the System Reserved one). It's not disimilar to having an extra /boot partition in Linux or how a GRUB's stage 2 works.
-> Under a typical Grub Legacy the MBR contains the Stage 1. It directly reads the Stage 2 from the proper partition/file system with a hardcoded path, but due to size limit of the MBR cannot do more. In some cases it starts a stage 1.5 wich has more
space to do work (63 sectors between MBR and first partition), but I never used this Setup
    -> Stage 2 loads the Grub Configuration from the disk. From here it depends on what OS you want to boot.
        -> For Linux or Unix the kernel is started directly.
        -> Any Windows OS up to 7 can be booted using the chainloader command. For the OS this is identical to having the partition choosen by the Generic Bootloader.
While it can be chainloaded by the Generic Bootloader from the active primary partition, GRUB and thus Linux has no
requirement for any Primary Partitions. Stage 1 is designed to directly access the specific File System containng the Stage 2. In fact it does not even need to reside on the same disk (as the Generic Bootloader has to).
If one does not need the Active Flag to control the Generic Bootloader (because a proper Stage 1 is installed in MBR) it is adviseable to mark wichever Windows Partition is chainloaded as active (up to Vista at least I had very odd behavior if the Windows boot
partition was not marked active, down to randomly shredded Partition boot managers).
After running a Windows Setup usually the Stage 1 has to be restored, as Windwos Setup will always write it's Generic Bootloader in the MBR. In order to get "rid" of a Grub all one has to do is overwrite the MBR with the Generic Bootloader and set the active
flag properly.
Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

Unable to create filesystem (mkfs.ext4) 2TB CentOS 6.5 VM

All, We have been having trouble creating disk volumes larger than 2TB on CentOS machines in our lab environment that consists of Hyper-V 2012 R2.
Today we came a step closer with the help of
http://social.technet.microsoft.com/Forums/windowsserver/en-US/bc1ee7e7-dcaf-455b-baec-01e6128ddd28/action?threadDisplayName=unable-to-create-filesystem-mkfsext4-on-large-gt-2tb-gpt-virtual-disk-using-linux-vm - which suggests mkfs with the '-K' option.
This has created a mountable logical volume, however it only registers as 2TB, rather than the actual size of 4TB. I notice the article is over a year old. Has there been any fixes?
The alternative would be multiple 2TB drives..

As part of the product team that does Linux on Hyper-V, we've recently spent some time investigating this problem. It occurs because Linux issues a SCSI "WRITE_SAME(16)" command, which is not implemented by Hyper-V. WRITE_SAME(16) is optional
in the SCSI spec, so it's OK that Hyper-V doesn't implement it, but the problem is that Hyper-V doesn't return the correct error code and sense info to indicate that it's unimplemented. With the correct error code from Hyper-V, Linux would use alternate
SCSI commands and everything would work.
We're looking into possible fixes. Hopefully in the next couple of weeks we can have an update on what to expect.
We believe Ubuntu 14.04 actually works correctly on Hyper-V due to a complicated set of other reasons. RHEL 7.0 does not work, and the other file system types don't typically avoid the problem either.
Michael Kelley, Lead Program Manager, Open Source Technology Center

Unable to create filesystem (mkfs.ext4) on large 2TB GPT virtual disk using Linux VM.

I am unable to create a file system on a large (> 2TB disk) virtual disk for a Linux VM. I can create the disk, attach it to the VM, partition it with "parted", but I cannot run mkfs.ext4. Details below.
Hyper-V 2012 Core (w/ all Windows/Microsoft updates as of 4/19).
CentOS 6.4 VM w/ 4 virtual processors, 4GB RAM, and 3 dynamic drives:
/dev/sda 100GB IDE dynamic vhdx
/dev/sdb 75GB IDE dynamic vhdx
/dev/sdc 10TB SCSI dynamic vhdx
Using parted, created 500GB partition on the 10TB drive (/dev/sdc1).
(parted) select /dev/sdc
Using /dev/sdc
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 11.0TB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 500GB 500GB production_archive
then run: mkfs.ext4 /dev/sdc1
repeating error on console from mkfs.ext4:
INFO: task mkfs.ext4:2581 blocked for more than 120 seconds
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Runaway error in var/log/messages until my /var system filled up - 25G worth of it:
-rw-------. 1 root root 25085329408 Apr 19 23:15 messages
Apr 19 17:39:28 nfs2 kernel: sd 4:0:0:0: [sdc] Sense Key : No Sense [current]
Apr 19 17:39:28 nfs2 kernel: sd 4:0:0:0: [sdc] Add. Sense: No additional sense information
Apr 19 17:39:28 nfs2 kernel: hv_storvsc vmbus_0_13: cmd 0x93 scsi status 0x2 srb status 0x6
Same problem happens when running "mkfs.ext4 -E lazy_itable_init=1 /dev/sdc1"

Hi,
Thank you for your post.
I am trying to involve someone familiar with this topic to further look at this issue.
Lawrence
TechNet Community Support

Unable to create temporary backing file

My program is throwing out the error:
temporary open: /var/tmp/BDB20825: Too many open files
unable to create temporary backing file
This happens after my program has been running for about 4 hours. The program appears to run out of file descriptors. The listing of /proc/<PID>/fd shows hundreds of lines naming the same file (/var/tmp/BDB20825), like this:
lrwx------ 1 zobell users 64 Jul 28 14:41 622 -> /var/tmp/BDB20825 (deleted)
That file does not exist. I suspect that someone is deleting but failing to close the file. A few open file descriptors with this deleted file occur slowly in the early hours, but not at a fast enough rate to bring the program down when it does. It looks like there is a sudden flood at the end.
The program repeats this error slowly, and is stuck inside the db code. Here is the gdb backtrace I am seeing every time I interrupt:
(gdb) where
#0 0x00e74410 in __kernel_vsyscall ()
#1 0x003d51dd in ___newselect_nocancel () from /lib/libc.so.6
#2 0x002e5d39 in __os_sleep () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#3 0x002e43f1 in __os_openhandle () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#4 0x002e52ad in __os_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#5 0x002c0357 in __db_tmp_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#6 0x002c006c in __db_appname () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#7 0x002d50c9 in __memp_bhwrite () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#8 0x002d4a27 in __memp_alloc () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#9 0x002d62ec in __memp_fget () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#10 0x00232003 in __bam_new_file () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#11 0x002abc79 in __db_new_file () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#12 0x002abaff in __db_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#13 0x002a5d15 in __db_open_pp () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#14 0x0080644c in Db::open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb_cxx-4.6.so
#15 0x0053ebbe in DbXml::DbWrapper::open (this=0x405bbee0, txn=0x0, type=DB_BTREE, flags=65537, mode=0) at Transaction.hpp:62
#16 0x00549247 in CacheDatabase (this=0x405bbed8, env=0x9c5a848, type=DB_BTREE, compare=0) at CacheDatabase.cpp:28
#17 0x005497e2 in DocDatabase (this=0x405bbed8, env=0x9c5a848, compare=0) at CacheDatabase.cpp:46
#18 0x00584ced in DbXml::Manager::createDocDatabase (this=0x9c5a830, compare=0) at Manager.cpp:694
#19 0x00519467 in DbXml::CacheDatabaseMinderImpl::verify (this=0xfffffdfe, entry=@0x6ac2f790, cid=-514) at CacheDatabaseMinder.hpp:31
#20 0x00519398 in DbXml::CacheDatabaseMinderImpl::findOrAllocate (this=0x6ac5b4f0, cid=1, allocate=true) at CacheDatabaseMinder.cpp:71
#21 0x00518e59 in DbXml::CacheDatabaseMinder::findOrAllocate (this=0x6acd9fa0, mgr=@0x9c5a830, cid=1, allocate=true) at CacheDatabaseMinder.cpp:21
#22 0x0055b12d in LazyDIResults (this=0x6acd9f98, context=0x6acd9fa0, contextItem=0x4979abc0, expr=@0x9ce5de8, txn=0x0, flags=0) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlManager.hpp:80
#23 0x0052f9cd in DbXml::QueryExpression::execute (this=0x9ce5de8, txn=0x0, contextItem=0x4979abc0, context=@0xbfcb0e04, flags=0) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlQueryContext.hpp:86
#24 0x00565a3a in DbXml::XmlQueryExpression::execute (this=0x0, contextItem=@0xfffffdfe, context=@0xbfcb0e04, flags=4294966782) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlValue.hpp:186
#25 0x0805af4b in XmlRecordWithCounts::ExtractQueryString (this=0xbfcb0dd0, select=@0xbfcb0e2c, result=@0xbfcac1d0, qDocument=0xbfcb0e14) at src/XmlRecordWithCounts.cpp:401
#26 0x080585f6 in OdRecord::GetRequiredContent (this=0xbfcb0dd0, name=@0xbfcac1e0, origin=@0xbfcac1d0, dest=@0xbfcac1c0, type=@0xbfcac1b0, dist=@0xbfcac198, totalCount=@0xbfcac194, route=@0xbfcac1a0, qDocument=0x0) at src/OdRecord.cpp:143
#27 0x0804d9c3 in ProcessOd (fpPrivate=0x8e11098, odDb=@0xbfcb0dd0, fdDb=@0xbfcb0d20) at src/BuildFdDb.cpp:263
#28 0x0804f4c8 in ProcessOneDest (fpPrivate=0x8e11098, odDb=@0xbfcb0dd0, fdDb=@0xbfcb0d20, dest={static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<No data fields>}, Mp = 0x9da758c "LAX"}, static Sempty_rep_storage = {0, 0, 69041, 0}}) at src/BuildFdDb.cpp:464
#29 0x080501cd in main (argc=6, argv=0xbfcb10c4) at src/BuildFdDb.cpp:589
At this time, the program is trying to extract fields out of an XmlDocument that is the result of a query. The program uses a pre-calculated XmlQueryExpression to extract a specific field. This may not be the best way to extract a field from a document, given the apparent overhead of needing a temporary file!
My program queries two database files (OD.dbxml and FD.dbxml.new), and uses the information to add records to the second file. The databases are rather big:
bash-3.2$ ls -l /tmp/*dbxml*
-rw-rw---- 1 zobell users 5233745920 Jul 28 14:42 /tmp/FD.dbxml.new
-rw-rw---- 1 zobell users 6539427840 Jul 13 10:16 /tmp/OD.dbxml
(I keep them in /tmp because everywhere else uses NFS and performance is awful with NFS.)
My environment:
Red Hat Enterprise Linux Client release 5.3 (Tikanga) 32 bit.
Berkeley DB XML 2.4.16, C++ interface.
Disk space should not be an issue:
bash-3.2$ df /tmp /var
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-tmp
28948572 13044384 14409968 48% /tmp
/dev/mapper/VolGroup00-root
144742920 5333544 131938272 4% /
I ran this program about a year ago and did not see this issue. I have made a few changes and linked to the newer version of the XML database since then. Any help is appreciated.

I have more information about this problem.
If I "disable" the routine __os_zerofill() in os_fzero.c, by having it always return (0), I no longer get an exception and my application appears to run smoothly. However, I have not determined what in this routine leads to the exception. And, I have no idea what the short and long term consequences of "disabling" this routine will be....
-Coralie

Windows 7 Ultimate isn't installing on my iMac. Setup was unable to create a new system partition or locate an existing system partition

I have a 21.5" iMac (Late 2012) running OS X Mavericks. I'm trying to install Windows 7 Ultimate via Bootcamp but whenever i get to the setup part it goes wrong
These are the steps I followed
I selected all the options since I didn't have the drivers or an install disk
it copied the Windows 7 iso image, downloaded the support software, and saved the support software to the flash drive (8GB)
I selected a partition size - I gave windows roughly 100GB
and I let it install
Right now I'm at the part where it says " where do you want to install windows? I selected the bootcamp partition and formatted it. It now says
"Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information"
WHAT DO I DO?

I had to read the apple instructions several times before they started to make sense. I burned my iso onto a DVD and had the required USB for support software. Are you trying to use the single USB method?
This article has a lot of info on the single usb method

[URGENT HELP] Why is cannot install Windows 7 on my X120e? ERROR : Setup was unable to create..

i have got X120e from my college with ubuntu 11.04 installed. But my half of softwares dont work on this Lunix OS so decided to install windows 7, downloaded officially as i have keys for activation.
I used USB drive to install, Windows 7 setup sucessfully started on boot up but its getting error
"Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information"
I have not connected any other devices.
My Hard disk is NOT dynamic, its basic.
I have contacted lenovo service centre, but this are taking up calls.
I am fed up of this, please help me..
I have exams coming and i need this urgently.
Solved!
Go to Solution.

Hello,
Do you just want to delete the Ubuntu partition? If so, you may be able to do by booting from the Microsoft Windows 7 installation disc, pressing Shift+F10 to get to a Command Prompt, and then using the DISKPART.EXE program to erase the hard disk drive.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

Boot Camp - Setup was unable to create a new system partition....from Windows install

Hi folks. So I ran the boot camp wizard and made a USB install key for windows from that. I boot to it and everything works until I get to the install. I format the Boot Camp partition as indicated in the walkthrough and then I get "Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information." from the Windows installer. What do I do? Thanks.

just to add to the mix. . . i just got a new macbook retina.
Originally used a USB flash drive. Hit the same barrier described here.
Spent a few hours with drive unplugging / replugging silliness. No progress. Went back into OSX to attempt using an external DVD drive. There is no option for that in Bootcamp assistant now - must use USB.
Grabbed a different USB stick and started again. This time I used the other USB port on the macbook (the one on the left). Everything worked fine this time!?
You still have to go into "advanced options" and hit "format" when you get to the partition screen.
Moral of the story: different stick, different port. Sounds random. If that doesn't work, try changing your socks and putting on a hat.
Good luck!

Unable to create xml from xml schema

JDeveloper 10.1.3 EA1
I am unable to create a new xml file from an xml schema when the starting root element is a complex type (but it works with a simple type). It does not matter if the xml schema is registered within JDeveloper.
Is this a bug or intended behaviour?
Error message:
''XML Document from XML Schema creation could not be competed succesfully. Make sure the source schema is valid and that you have write permissions to the output directory."
NB The xml schema is valid and I have write permissions on the specified directory.

When I do not register this (or other) schema with JDeveloper, I can create an xml document from xml schema. However, when I register this schema and then try to generate an xml document (either from the registered xsd either from a filesystem xsd) with person as starting node it fails with the mentioned error. However, when I use city as starting node it is generated successfully.
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.amis.nl/demo/hrm"
targetNamespace="http://www.amis.nl/demo/hrm"
elementFormDefault="qualified">
<xsd:element name="person">
<xsd:annotation>
<xsd:documentation>
A sample complex element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="length" type="xsd:int"/>
<xsd:element name="weight" type="xsd:int" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="city" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A sample simple element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>

Unable to create a whole root zone

Hi Folks,
I wanted to create a whole-root zone. I am unable to create one :(. Did some one encounter this problem ?.
BTW: I have SC 3.2 installed on this two node cluster. I was able to validate our Data services on this setup without any problem Now I am trying to experiment with zones, by creating zones. I am unable to move further with my validation of our data services on zones.
*) mkdir -m 700 /export/zone-1
*) The version of the OS used
# cat /etc/release
Solaris 10 11/06 s10s_u3wos_09 SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 01 November 2006
# zonecfg -z zone-1
zone-1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-1> create
zonecfg:zone-1> remove inherit-pkg-dir dir=/sbin
zonecfg:zone-1> remove inherit-pkg-dir dir=/usr
zonecfg:zone-1> remove inherit-pkg-dir dir=/platform
zonecfg:zone-1> remove inherit-pkg-dir dir=/lib
zonecfg:zone-1> set autoboot=true
zonecfg:zone-1> set zonepath=/export/zone-1
zonecfg:zone-1> add net
zonecfg:zone-1:net> set address=192.18.75.237
zonecfg:zone-1:net> set physical=eri0
zonecfg:zone-1:net> end
zonecfg:zone-1> info
zonename: zone-1
zonepath: /export/zone-1
autoboot: true
pool:
limitpriv:
net:
address: 192.18.75.237
physical: eri0
zonecfg:zone-1> verify
zonecfg:zone-1> commit
zonecfg:zone-1> exit
# cat /etc/zones/zone-1.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">

<zone name="zone-1" zonepath="/export/zone-1" autoboot="true">
<network address="192.18.75.237" physical="eri0"/>
</zone>
# zoneadm list -civ
ID NAME STATUS PATH
0 global running /
- zone-1 configured /export/zone-1
# zoneadm -z zone-1 verify
# zoneadm -z zone-1 install
Preparing to install zone <zone-1>.
Creating list of files to copy from the global zone.
Copying <6080> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1071> packages on the zone.
Initialized <1071> packages on zone.
Zone <zone-1> is initialized.
Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
# pkginfo -i SUNWsczr
application SUNWsczr Sun Cluster (non-global zones support)
# pkginfo -i SUNWsczr
application SUNWsczr Sun Cluster (non-global zones support)
# pkginfo -i SUNWdtlog
system SUNWdtlog System boot for Desktop Login
# pkginfo -i SUNWsmmgr
system SUNWsmmgr System Management Agent Startup scripts
*** package <SUNWsczr> failed to install with fatal errors:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/stoprgm> failed
pathname does not exist
NOTE: When the package <SUNWsczr> was installed in the global zone, the file <etc/init.d/stoprgm> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone <zone-1> in the file </export/zone-1/root/etc/init.d/stoprgm>.
ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWsczr/save/pspool/SUNWsczr/archive.
pkgadd: ERROR: class action script did not complete successfully
Installation of <SUNWsczr> on zone <zone-1> failed.
*** package <SUNWnisr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nis> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <etc/nsswitch.nis> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/nsswitch.nis>.
WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nisplus> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <etc/nsswitch.nisplus> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/nsswitch.nisplus>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nisplus> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <lib/svc/method/nisplus> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/nisplus>.
WARNING: attribute verification of </export/zone-1/root/var/nis/NIS+LDAPmapping.template> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <var/nis/NIS+LDAPmapping.template> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/nis/NIS+LDAPmapping.template>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ nis/client.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/nisplus.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/rex.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/nisplus.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rex.xml> failed
pathname does not exist
Installation of <SUNWnisr> on zone <zone-1> partially
failed.
*** package <SUNWypr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/var/yp/updaters> failed
pathname does not exist
NOTE: When the package <SUNWypr> was installed in the global zone,
the file <var/yp/updaters> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/yp/updaters>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/passwd.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/server.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/update.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/xfr.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/passwd.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/server.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/update.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/xfr.xml> failed
pathname does not exist
Installation of <SUNWypr> on zone <zone-1> partially
failed.
*** package <SUNWipplr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWipplr/save/pspool/SUNWipplr/reloc/var/svc/manifest/applic ation/print/ipp-listener.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/ipp-listener.xml> failed
pathname does not exist
Installation of <SUNWipplr> on zone <zone-1> partially
failed.
*** package <SUNWaccr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-sar> failed
pathname does not exist
NOTE: When the package <SUNWaccr> was installed in the global zone,
the file <lib/svc/method/svc-sar> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-sar>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWaccr/save/pspool/SUNWaccr/reloc/var/svc/manifest/system/s ar.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/sar.xml> failed
pathname does not exist
Installation of <SUNWaccr> on zone <zone-1> partially
failed.
*** package <SUNWbsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/rpld.conf> failed
pathname does not exist
NOTE: When the package <SUNWbsr> was installed in the global zone,
the file <etc/rpld.conf> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/rpld.conf>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/ra rp.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/rp c/bootparams.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rarp.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/bootparams.xml> failed
pathname does not exist
Installation of <SUNWbsr> on zone <zone-1> partially
failed.
*** package <SUNWdhcsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/dhcp> failed
pathname does not exist
NOTE: When the package <SUNWdhcsr> was installed in the global zone,
the file <etc/init.d/dhcp> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/init.d/dhcp>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWdhcsr/save/pspool/SUNWdhcsr/reloc/var/svc/manifest/networ k/dhcp-server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dhcp-server.xml> failed
pathname does not exist
Installation of <SUNWdhcsr> on zone <zone-1> partially
failed.
*** package <SUNWatfsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-autofs> failed
pathname does not exist
NOTE: When the package <SUNWatfsr> was installed in the global zone,
the file <lib/svc/method/svc-autofs> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-autofs>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWatfsr/save/pspool/SUNWatfsr/reloc/var/svc/manifest/system /filesystem/autofs.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/filesystem/autofs.xml> failed
pathname does not exist
Installation of <SUNWatfsr> on zone <zone-1> partially
failed.
*** package <SUNWkdcr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWkdcr/save/pspool/SUNWkdcr/reloc/var/svc/manifest/network/ security/krb5_prop.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/security/krb5_prop.xml> failed
pathname does not exist
Installation of <SUNWkdcr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.gif> failed
pathname does not exist
NOTE: When the package <SUNWapch2r> was installed in the global zone,
the file <var/apache2/icons/world2.gif> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.gif>.
WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.png> failed
pathname does not exist
NOTE: When the package <SUNWapch2r> was installed in the global zone,
the file <var/apache2/icons/world2.png> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.png>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWapch2r/save/pspool/SUNWapch2r/reloc/var/svc/manifest/netw ork/http-apache2.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/http-apache2.xml> failed
pathname does not exist
Installation of <SUNWapch2r> on zone <zone-1> partially
failed.
*** package <SUNWbindr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbindr/save/pspool/SUNWbindr/reloc/var/svc/manifest/networ k/dns/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dns/server.xml> failed
pathname does not exist
Installation of <SUNWbindr> on zone <zone-1> partially
failed.
*** package <SUNWbnur> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbnur/save/pspool/SUNWbnur/reloc/var/svc/manifest/network/ uucp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/uucp.xml> failed
pathname does not exist
Installation of <SUNWbnur> on zone <zone-1> partially
failed.
*** package <SUNWcnsr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ chargen.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ daytime.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ discard.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ echo.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ time.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/chargen.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/daytime.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/discard.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/echo.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/time.xml> failed
pathname does not exist
Installation of <SUNWcnsr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/etc/lp/fd/pr.fd> failed
pathname does not exist
NOTE: When the package <SUNWpsr> was installed in the global zone,
the file <etc/lp/fd/pr.fd> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/lp/fd/pr.fd>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/print-svc> failed
pathname does not exist
NOTE: When the package <SUNWpsr> was installed in the global zone,
the file <lib/svc/method/print-svc> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/print-svc>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWpsr/save/pspool/SUNWpsr/reloc/var/svc/manifest/applicatio n/print/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/server.xml> failed
pathname does not exist
Installation of <SUNWpsr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/var/snmp/mib/sun.mib> failed
pathname does not exist
NOTE: When the package <SUNWsacom> was installed in the global zone,
the file <var/snmp/mib/sun.mib> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/snmp/mib/sun.mib>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.dmi> is corrupt
file size <373> expected <1125> actual
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.snmpdx& gt; is corrupt
file size <382> expected <685> actual
ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.dmi> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.snmpdx> failed
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/dmi.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/snmpdx.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/dmi.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/snmpdx.xml> failed
pathname does not exist
Installation of <SUNWsacom> on zone <zone-1> partially
failed.
*** package <SUNWdtlog> failed to install with fatal errors:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/dtlogin> failed
pathname does not exist
NOTE: When the package <SUNWdtlog> was installed in the global zone,
the file <etc/init.d/dtlogin> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/init.d/dtlogin>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-dtlogin> failed
pathname does not exist
NOTE: When the package <SUNWdtlog> was installed in the global zone,
the file <lib/svc/method/svc-dtlogin> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-dtlogin>.
ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/archive.
pkgadd: ERROR: class action script did not complete successfully
Installation of <SUNWdtlog> on zone <zone-1> failed.
*** package <SUNWnfssr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nfs-server> failed
pathname does not exist
NOTE: When the package <SUNWnfssr> was installed in the global zone,
the file <lib/svc/method/nfs-server> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/nfs-server>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/rquota.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/rquota.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/server.xml> failed
pathname does not exist
Installation of <SUNWnfssr> on zone <zone-1> partially
failed.
*** package <SUNWntpr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/inet/ntp.server> failed
pathname does not exist
NOTE: When the package <SUNWntpr> was installed in the global zone,
the file <etc/inet/ntp.server> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/inet/ntp.server>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/xntp> failed
pathname does not exist
NOTE: When the package <SUNWntpr> was installed in the global zone,
the file <lib/svc/method/xntp> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/xntp>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWntpr/save/pspool/SUNWntpr/reloc/var/svc/manifest/network/ ntp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ntp.xml> failed
pathname does not exist
Installation of <SUNWntpr> on zone <zone-1> partially
failed.
*** package <SUNWftpr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWftpr/save/pspool/SUNWftpr/reloc/var/svc/manifest/network/ ftp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ftp.xml> failed
pathname does not exist
Installation of <SUNWftpr> on zone <zone-1> partially
failed.
*** package <SUNWrcapr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcapr/save/pspool/SUNWrcapr/reloc/var/svc/manifest/system /rcap.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/rcap.xml> failed
pathname does not exist
Installation of <SUNWrcapr> on zone <zone-1> partially
failed.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcmdr/save/pspool/SUNWrcmdr/reloc/var/svc/manifest/networ k/talk.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/comsat.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/finger.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/login.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rexec.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rstat.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rusers.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/spray.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/wall.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/shell.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/talk.xml> failed
pathname does not exist
Installation of <SUNWrcmdr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> ; failed
pathname does not exist
NOTE: When the package <SUNWsmmgr> was installed in the global zone,
the file <etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> was also installed. Af

Hello,
I still get the errors.
# zonecfg -z zone-one
zone-one: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-one> create -b
zonecfg:zone-one> set autoboot=true
zonecfg:zone-one> set zonepath=/export/zone-one
zonecfg:zone-one> add net
zonecfg:zone-one:net> set physical=eri0
zonecfg:zone-one:net> set address=192.18.xx.xxx
zonecfg:zone-one:net> end
zonecfg:zone-one> verify
zonecfg:zone-one> commit
zonecfg:zone-one> exit
# zoneadm -z zone-one verify
# zoneadm -z zone-one install
Preparing to install zone <zone-one>.
Creating list of files to copy from the global zone.
Copying <6080> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1071> packages on the zone.
Initialized <1071> packages on zone.
Zone <zone-one> is initialized.
Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
_DD

Cannot export video clips. Get message: "unable to create video for export"

Cannot export video clips from iPhoto to Finder folder. Export fails with message "unable to create video for export: "
The video clips play correctly within iPhoto.
Software: iPhoto version 9.5 on OSX 10.9
Hardware: Retina Macbook Pro 2.3 i7 8GB

Yes. I have 3,184 video clips in this library. I tested Reveal function by randomly selecting individual video clips and in every case the Reveal in Finder function worked correctly. I also tested this on random selections of groups of video clips and, again, the Reveal function worked correctly in every case.
Some more info that may be relevant:
I have multiple iPhoto libraries. My "main" library is very large (~30,000 files) and is located on an external hard drive (2TB WD) which is connected via USB.
The problem reported here is occuring on that "main" library. I have not opened any other iPhoto library since installing the new release.
While the File>Export function does not work, I have been able to simply copy and paste video clips from iPhoto library to a folder on Mac hard drive. It appears that meta data is copying correctly along with the video content.
I am able to import these copied video clips to iMovie. Meta data is imported along with the video content and I'm able to perform iMovie editing functions on those clips without any problems.
In summary, the File>Export function still fails with the message "unable to create video for export." Copying video clips and pasting them to interim folder seems to be a viable workaround enabling me to extract video clips from iPhoto for import to iMovie. I will run additional tests to see if I can find a pattern to the video files that are being rejected by iPhoto Export function.

Bootcamp windows 7 setup was unable to create a new system partition

I've been trying to load Win 7 sp1 64 for a week. Tried 4 versions, all 64b, made a new USB drive each time, I always get stuck in the same place:
"setup was unable to create a new system partition or locate existing system partition". I've tried everything, read MANY forums.
I read format in set-up many times, but it matters not! HELP!

Restart your machine and do a pram reset (google)
Open disk utility and repair permissions twice, also you should only have 1 partition
Then try boot camp assistant again
If this doesn't work, you'll need to either clean install OSX or have a terminal disk wizard from here try and help

Getting "Unable to create VOLUMES/" error when exporting photos

I am trying to export a number of photos from iPhoto '08 to a USB stick that has been freshly formated with FAT 32. When iPhoto reaches a photo that has a vertical orientation the export stops and throws this error:
"Unable to create VOLUMES/JUMP DRIVE/filename"
These photos were taken with a Canon Powershot SD700IS. The camera has the ability to sense orientation when the picture is taken. It will automatically rotate pictures that were taken while holding the camera on its side. If the picture was taken with a horizontal (normal) orientation the export is successful.
I was able to work around this by opening the offending files in Preview and saving them from there. Obviously this is a time consuming extra step that shouldn't be necessary.
If anyone has any ideas I would greatly appreciate them!
Thanks!
Message was edited by: MTEGuitar

Then you have a managed library.
Go to your Pictures Folder. There you'll see the icon for your iPhoto Library. Right Click on that icon and select 'Show Package Contents' from the resulting menu. A Finder window will open and you'll see your Library internals. Have a look for the /Originals Folder. Inside it will be the folders for your Events. These should include the full sized photos.
If they do, then
Try these in order - from best option on down...
1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library (Right Click -> Show Package Contents) allowing it to overwrite the damaged file.
2. Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums back.
3. If neither of these work then you'll need to create and populate a new library.
To create and populate a new library:
Note this will give you a working library with the same Events and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'
Move the iPhoto Library to the desktop
Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
Go into the iPhoto Library (Right Click -> Show Package Contents) on your desktop and find the Originals folder. From the Originals folder drag the individual Event Folders to the iPhoto Window and it will recreate them in the new library.
When you're sure all is well you can delete the iPhoto Library on your desktop.
In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
Regards
TD

Unable to create a filesystem on an USB-stick

Similar Messages

Maybe you are looking for