FSArchiver not supporting EXT4 partition?

Hi i have just recently been getting errors on my systems using fsarchiver. 
It claims the filesystem is not supported
[======DISK======] [=============NAME==============] [====SIZE====] [MAJ] [MIN]
[sda ] [SAMSUNG HD204UI ] [ 1.82 TB] [ 8] [ 0]
[sdb ] [ELSKY MSATA 16GB ] [ 14.91 GB] [ 8] [ 16]
[=====DEVICE=====] [==FILESYS==] [======LABEL======] [====SIZE====] [MAJ] [MIN]
[sda1 ] [LVM2_member] [<unknown> ] [ 1.82 TB] [ 8] [ 1]
[sdb1 ] [ext4 ] [OS ] [ 14.91 GB] [ 8] [ 17]
[dm-0 ] [ext4 ] [hd1 ] [ 1.82 TB] [254] [ 0]
fsarchiver savefs -v -A -j2 -o -z6 ~/backup.fsa /dev/sdb1
Im trying to backup /dev/sdb1 and it shows this error
oper_save.c#947,filesystem_mount_partition(): filesystem of partition [/dev/sdb1] is not supported by fsarchiver
I am running arch linux, all up to date and have recently updated to systemd and grub2.  Kernel is 3.5.6-1.
I have some other machines with slightly older kernels and on the on initv system and seems to work fine
Is anyone else having these issues?
I would appreciate any insight into a solution.  Thankyou
Last edited by craigdabbs (2012-10-15 10:11:02)

I've been doing a little bit of digging. I'm a bit rusty on the skills, but here's what I've discovered so far...
This is where it's crapping out: oper_save.c#947
res=generic_get_mntinfo(devinfo->devpath, &readwrite, curmntdir, sizeof(curmntdir), optbuf, sizeof(optbuf), fsbuf, sizeof(fsbuf));
if (res==0) // partition is already mounted
devinfo->mountedbyfsa=false;
//snprintf(partmnt, PATH_MAX, "%s", curmntdir); // return the mount point to main savefs function
msgprintf(MSG_DEBUG1, "generic_get_mntinfo(%s): mnt=[%s], opt=[%s], fs=[%s], rw=[%d]\n", devinfo->devpath, curmntdir, optbuf, fsbuf, readwrite);
if (readwrite==1 && g_options.allowsaverw==0)
errprintf("partition [%s] is mounted read/write. please mount it read-only \n"
"and then try again. you can do \"mount -o remount,ro %s\". you can \n"
"also run fsarchiver with option '-A' if you know what you are doing.\n",
devinfo->devpath, devinfo->devpath);
return -1;
if (generic_get_fstype(fsbuf, &devinfo->fstype)!=0)
if (strcmp(fsbuf, "fuseblk")==0)
errprintf("partition [%s] is using a fuse based filesystem (probably ntfs-3g). Unmount it and try again\n", devinfo->devpath);
else
errprintf("filesystem of partition [%s] is not supported by fsarchiver: filesystem=[%s]\n", devinfo->devpath, fsbuf);
return -1;
Specifically:  if (generic_get_fstype(fsbuf, &devinfo->fstype)!=0).
The called function doesn't find a match for the filesystem name.
Here's the code of that function from filesys.c:
// return the index of a filesystem in the filesystem table
58 int generic_get_fstype(char *fsname, int *fstype)
59 {
60 int i;
61
62 for (i=0; filesys[i].name; i++)
63 {
64 if (strcmp(filesys[i].name, fsname)==0)
65 { *fstype=i;
66 return 0;
67 }
68 }
69 *fstype=-1;
70 return -1;
So I guess the filesystem is either being reported incorrectly or in a format that fsarchiver can't make sense of? Something to do with the way the filesystem is mounted when using systemd versus the way fsarchiver looks for the mounted devices.
filesys.c's generic_get_mntinfo
int generic_get_mntinfo(char *devname, int *readwrite, char *mntbuf, int maxmntbuf, char *optbuf, int maxoptbuf, char *fsbuf, int maxfsbuf)
char col_fs[FSA_MAX_FSNAMELEN];
int devisroot=false;
struct stat64 devstat;
struct stat64 rootstat;
char delims[]=" \t\n";
struct utsname suname;
char col_dev[128];
char col_mnt[128];
char col_opt[128];
char line[1024];
char temp[2048];
char *saveptr;
char *result;
int res;
FILE *f;
int i;
// init
res=uname(&suname);
*readwrite=-1; // unknown
memset(mntbuf, 0, sizeof(mntbuf));
memset(optbuf, 0, sizeof(optbuf));
// 1. workaround for systems not having the "/dev/root" node entry.
// There are systems showing "/dev/root" in "/proc/mounts" instead
// of the actual root partition such as "/dev/sda1".
// The consequence is that fsarchiver won't be able to realize
// that the device it is archiving (such as "/dev/sda1") is the
// same as "/dev/root" and that it is actually mounted. This
// function would then say that the "/dev/sda1" device is not mounted
// and fsarchiver would try to mount it and mount() fails with EBUSY
if (stat64(devname, &devstat)==0 && stat64("/", &rootstat)==0 && (devstat.st_rdev==rootstat.st_dev))
devisroot=true;
msgprintf(MSG_VERB1, "device [%s] is the root device\n", devname);
// 2. check device in "/proc/mounts" (typical case)
if ((f=fopen("/proc/mounts","rb"))==NULL)
{ sysprintf("Cannot open /proc/mounts\n");
return 1;
while(!feof(f))
if (stream_readline(f, line, 1024)>1)
result=strtok_r(line, delims, &saveptr);
col_dev[0]=col_mnt[0]=col_fs[0]=col_opt[0]=0;
for(i=0; result != NULL && i<=3; i++)
switch (i) // only the second word is a mount-point
case 0:
snprintf(col_dev, sizeof(col_dev), "%s", result);
break;
case 1:
snprintf(col_mnt, sizeof(col_mnt), "%s", result);
break;
case 2:
snprintf(col_fs, sizeof(col_fs), "%s", result);
break;
case 3:
snprintf(col_opt, sizeof(col_opt), "%s", result);
break;
result = strtok_r(NULL, delims, &saveptr);
if ((devisroot==true) && (strcmp(col_mnt, "/")==0) && (strcmp(col_fs, "rootfs")!=0))
snprintf(col_dev, sizeof(col_dev), "%s", devname);
msgprintf(MSG_DEBUG1, "mount entry: col_dev=[%s] col_mnt=[%s] col_fs=[%s] col_opt=[%s]\n", col_dev, col_mnt, col_fs, col_opt);
if (devcmp(col_dev, devname)==0)
if (generic_get_spacestats(col_dev, col_mnt, temp, sizeof(temp))==0)
msgprintf(MSG_DEBUG1, "found mount entry for device=[%s]: mnt=[%s] fs=[%s] opt=[%s]\n", devname, col_mnt, col_fs, col_opt);
*readwrite=generic_get_fsrwstatus(col_opt);
snprintf(mntbuf, maxmntbuf, "%s", col_mnt);
snprintf(optbuf, maxoptbuf, "%s", col_opt);
snprintf(fsbuf, maxfsbuf, "%s", col_fs);
fclose(f);
return 0;
fclose(f);
return -1;
Last edited by slickvguy (2012-10-30 05:54:56)

Similar Messages

  • Database support for partition

    Hi all,
    what are the databases that support the partition. mine is MSSQL. will it not support for partition? Is that the reason the partition option is diabled.
    regards
    kiran

    Hi Kiran,
    Yes.SAP does not support MS-SQL as of now. As of now only ORACLE, INFORMIX support partitioning.
    Check this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
    Bye
    Dinesh

  • HT204053 hi i want to use find my mac but i got this massage (some configurations, such as software or hardware RAID,do not support a recovery partition and can't be used with find my mac)

    hi i want to use find my mac but i got this massage (some configurations, such as software or hardware RAID,do not support a recovery partition and can't be used with find my mac)

    hi i want to use find my mac but i got this massage (some configurations, such as software or hardware RAID,do not support a recovery partition and can't be used with find my mac)

  • Some configurations such as a software or hardware RAID do not support a recovery partition and can't be used with Find My Mac.

    I'm getting the following error message when attempting to invoke "Find My Mac"
    Some configurations such as a software or hardware RAID do not support a recovery partition and can't be used with Find My Mac.

    You have no recovery partition. This is a normal condition if your boot volume is a software RAID, or if you modified the partition table after running Boot Camp Assistant to create a Windows partition. Otherwise, you need to reinstall OS X in order to add a recovery partition.
    If you don't have a current backup, you need to back up before you do anything else.
    You have several options for reinstalling.
    1. If you have access to a local, unencrypted Time Machine backup volume, and if that volume has a backup of a Mac (not necessarily this one) that was running the same major version of OS X and did have a Recovery partition, then you can boot from the Time Machine volume into Recovery by holding down the option key at the startup chime. Encrypted Time Machine volumes are not bootable, nor are network backups.
    2. If your Mac shipped with OS X 10.7 or later preinstalled, or if it's one of the computers that can be upgraded to use OS X Internet Recovery, you may be able to netboot from an Apple server by holding down the key combination option-R  at the startup chime. Release the keys when you see a spinning globe.
     Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication. 
    3. Use Recovery Disk Assistant (RDA) on another Mac running the same major version of OS X as yours to create a bootable USB device. Boot your Mac from the device by holding down the option key at startup.Warning: All existing data on the USB device will be erased when you use RDA.
    Once you've booted into Recovery, the OS X Utilities screen will appear. Follow the prompts to reinstall OS X. You don't need to erase the boot volume, and you won't need your backup unless something goes wrong. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.
    If none of the above choices is open to you, then you'll have to start over from an OS X 10.6.8 installation. There's no need to overwrite your existing boot volume; you can use an external drive. Install 10.6 from the DVD you originally used to upgrade, or that came with the machine. Run Software Update and install all available updates. Log into the App Store with the Apple ID you used to buy 10.7 or later, and download the installer. When you run it, be sure to choose the right drive to install on.

  • Error: The Boot Camp partition "/dev/disk0s3" used by Hard Disk 1 is not supported.

    I installed Lion a couple of weeks ago, and had Parallels 5 installed, but it would no longer run.  Unfortunately, I spent the money to upgrade to Parallels 6 prior to seeing the advice to get Lion to run with 5.  Oh well.  But now, it won't run with 6 either.  What to do?
    Here;s the error again:
    The Boot Camp partition "/dev/disk0s3" used by Hard Disk 1 is not supported.

    You should be able to do this using the Boot Camp Assistant app. There is an option to "Restore the startup disk to a single volume". That should eliminate the Boot Camp partition without harming your Mac OS partition. Even so, make sure you back up your Mac OS X partition data before you do this, just to be safe.
    Lance

  • I installed the window 7 os in to my mac book pro. after that the partition is not supported and then the folder with question mark flashing on my screen. plaese helf me what to do next to resume the mac os x?

    i installed the window 7 ultimate OS in to my mac book pro. after that the partition is not supported and then the folder with question mark flashing on my screen. plaese helf me what to do next to resume mac mac os x?

    Assuming that you tried to install Win 7 in bootcamp.
    Power on the machine and press and hold the "option" key when you hear the bong sound.
    Select the Macintosh HD icon and press "return" or just click on the icon.
    Once booted into OS X go to System Preferences and select the Startup Disk icon and configure startup to use the Macintosh HD.

  • How do you repair the EFI systems partitions when you mac tells you that the live file system is not supported?

    how do you repair the EFI systems partitions when you mac tells you that the live file system is not supported?

    I don't have good news. You will need to repartition and reformat the hard drive in order to determine if the drive is still OK or if it needs to be replaced. If your computer is a 2011 model or later do the following:
    Install Mavericks, Lion/Mountain Lion Using Internet Recovery
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Internet Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
    Partition and Format the hard drive:
    Select Disk Utility from the main menu and click on the Continue button.
    After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion. Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Install button. Be sure to select the correct drive to use if you have more than one.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    This should restore the version of OS X originally pre-installed on the computer.
    If your computer is pre-2011 model, then locate the original installer discs that came with the computer. Then do this:
    Clean Install of Snow Leopard
    Be sure to make a backup first because the following procedure will erase
    the drive and everything on it.
         1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
             with your computer.  Insert the disc into the optical drive and restart the computer.
             After the chime press and hold down the  "C" key.  Release the key when you see
             a small spinning gear appear below the dark gray Apple logo.
         2. After the installer loads select your language and click on the Continue
             button. When the menu bar appears select Disk Utility from the Utilities menu.
             After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
             size.)  Click on the Partition tab in the DU main window.  Set the number of
             partitions to one (1) from the Partitions drop down menu, click on Options button
             and select GUID, click on OK, then set the format type to MacOS Extended
             (Journaled, if supported), then click on the Apply button.
         3. When the formatting has completed quit DU and return to the installer.  Proceed
             with the OS X installation and follow the directions included with the installer.
         4. When the installation has completed your computer will Restart into the Setup
             Assistant. Be sure you configure your initial admin account with the exact same
             username and password that you used on your old drive. After you finish Setup
             Assistant will complete the installation after which you will be running a fresh
             install of OS X.  You can now begin the update process by opening Software
             Update and installing all recommended updates to bring your installation current.
    Download and install Mac OS X 10.6.8 Update Combo v1.1. You can now download a version of OS X from which to upgrade from your Purchases page in the App Store.

  • CIMC 2.0.x and FlexFlash partitions for SCU, HUU, Drivers not supported?

    Hello all,
    We are fairly new to UCS, but are hooked for sure.  We started purchasing B series blades, chassises, and FI's at first, and now are in the process of deploying C-Series Servers.  Very cool stuff, then does Cisco takes some of it away, maybe?    
    We just purchased a C240, and noticed the FlexFlash card.  After initial reading we see that you can have a Server Configuration Utility (SCU), Host Update Utility (HUU), and Drivers Partitions on the FlexFlash.  Along with a 4th HyperVisor (HV) partition, which started this journey for us as we are going to install ESXi onto the FlexFlash.  
    But by the time we got to reading about and managing FlexFlash, we had already upgraded the CIMC & Bios to 2.0(1)b.  We only see the one large ~16GB HV partition, and with SCU 4.0 there isn't much you can do about that.  After reading the release notes for CIMC 2.0, we read:
    Starting with this version, the SD storage device is available to Cisco IMC as a single hypervisor (HV) partition configuration. Prior versions had four virtual USB drives.
    So does this mean that after CIMC 2.0, SCU, HUU, and Driver Partitions are unsupported on FlexFlash?  Or is there a process to get these utilities back on FlexFlash?  Because the documentation does not really make it clear one way or the other.  It would seem to be a nice feature, but i would also understand why the reasons not to support it.  As I'm sure the HUU updates just as fast as firmware.  
    Thanks for your time and support,
    Nick

    This is very confusing. Just received our first c-class server (220m3) with sd card preinstalled, and reading the online docs about the scu and huu partitions. Great feature! Could not see the partitions in CIMC and believed the sd-card was empty and needed to be initialized.
    Followed the flexflash docs to get the card up and running:
    http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/unified-computing/whitepaper_C11-718938.pdf
    Having spent one entire day getting the SD card to work as documented.
    Now, after reading this thread, I'm even more confused (and a little frustrated) - and would really like at least the scu to be bootable from the card.
    The experiences here are:
    1. Booting downloaded iso image SCU via kvm (virtual image)
    2. Configure network - dhcp does not work.. (tried earlier SCU, there dhcp does work.. but no update-icon...). Configures manually then.
    3. After network is configured, either manually or dhcp - the Update flexflash icon disappeares..
    Hitting the Update flexflash icon (after new reboot, without configuring network), a window appear with empty content. DOH.
    Booting all day trying different cisco manuals and approaches to get this to work, waiting for the long boot process each time.
    I would recommend that the cisco documents online are revised so we don't need to run through loops and endless cisco-pdf-redirections for nothing.
    Cheers,
    Martin

  • ".. recovery disks do not support this computer.." and I deleted my recovery partition

    So I dutiful created Recovery Disks, a set of 4 DVDs. I than resized my Windows 7 partition and deleted the Recovery Partition; to make room for Ubuntu. I want to recover my laptop to original install using the Recovery Disk set.
    My laptop boots from the Recovery Disk and reports:
    "The system recovery disks do not support this computer. You are not able to restore this system with these disks."
    My system is stock:
    HP Pavilion dv4 Notebook PC
    BIOS F.0C - 3/30/2010
    This will teach me not to buy original Windows OS CDs!
    Ideas?

    I don`t know if this will help you ,but if you have had your system board replaced your original recovery disks won`t work as they look for the serial number ex factory,as i had a similar problem,and ended up getting new disks from hp with my new serial number from the bios.Hope this helps.

  • Cannot get brand new hard drive to work. Disk utility states operation not supported when I try to erase or partition?

    Without any success, I cannot get my hard drive to work in disk utilities. I am able to see the disk in the upper left hand column, but when trying to initiliaze the software always reads operation not supported. Any ideas?

    You probably have too new a hard disk.  Contact the hard disk manufacturer and ask what jumper setting is needed to drop to 1.5 Gbps SATA speed.
    Either that, or return the disk, and go to http://www.macsales.com/
    They can be sure to equip you with a proper hard disk.
    Note formatting is key as well:
    http://discussions.apple.com/docs/DOC-3003

  • Grub not reading my partitions

    Hi all,
    I'm trying to install Arch Linux alongside my Windows 7 partition.  Using gparted I created two partitions, one for the ext4 filesystem and the other for the swap.  In the installation, when I arrived to preparing the hard drive, I chose "Manually Configure block devices, filesystems and mountpoints".  I selected the partitions I needed and went along. 
    My partition table (using sudo fdisk -l)
    Device Boot Start End Blocks Id System
    /dev/sdb1 1 13757 110503071 7 HPFS/NTFS
    /dev/sdb2 * 13758 15539 14313915 83 Linux
    /dev/sdb3 15540 15669 1044225 82 Linux swap / Solaris
    /dev/sdb4 15670 30401 118334790 7 HPFS/NTFS
    sdb1 is my Windows 7 partition, sdb2 is Arch installation parition, sdb3 is swap, and sdb4 is a data partition for Windows.
    Then I installed Grub to /dev/sdb, following the documentation advice and not installing to sdb#.
    When I came to reboot, the Grub menu loaded but when I hit Arch Linux or Arch Linux Fallback, I get this error:
    "root (hd1,1)
    error 22: No such partition"
    I don't get it, root (hd1,1) means sdb2, right?
    Here's the contents of my menu.lst grub file:
    # (0) Arch Linux
    title Arch Linux
    root (hd1,1)
    kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/12bc8088-7ccd-4449-88e1-9e848862f9f8 ro
    initrd /boot/kernel26.img
    # (1) Arch Linux
    title Arch Linux Fallback
    root (hd1,1)
    kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/12bc8088-7ccd-4449-88e1-9e848862f9f8 ro
    initrd /boot/kernel26-fallback.img
    # (2) Windows
    #title Windows
    #rootnoverify (hd0,0)
    #makeactive
    #chainloader +1
    (windows is commented out for now)
    And this is the contents of my fstab file:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    UUID=12bc8088-7ccd-4449-88e1-9e848862f9f8 / ext4 defaults 0 1
    UUID=c559a08d-2440-4149-95cb-928202048338 swap swap defaults 0 0
    I reinstalled Arch yesterday using UUID to see if I'd still get the error, and yes, I did still get it.  I should say that the Arch partition (sdb2) has the boot flag on it...might have something to do with it, I dunno.
    Anyone know anything about this?  I read through the documentation and I couldn't find anything that helped me out apart from arranging the order of the partition table with fdisk. 
    Thanks,
    Mike
    Last edited by kelinu (2011-03-12 12:30:14)

    cory.schwartz wrote:I am still suprised you were able to boot it, however, because grub(1) does not support booting from ext4 filesystems.
    http://kernelnewbies.org/Ext4#head-6344 … d2237f2910
    Luckily, the arch package of grub includes the ext4 patch https://wiki.archlinux.org/index.php/Ext4#Prerequisites

  • I just upgraded to Lion 10.7.2 and it says that it will not support Power PC programs so my 2008 version of Mac Office and Intuit Quickbooks are blanked out.  I need these programs.  How do I proceed?

    I just upgraded to Lion 10.7.2 and it says that it will not support Power PC programs and has blanked out my 2008 version of MS Office for Mac and Intuit's Quickbooks.  How do I proceed to get these programs back?

    Upgrade to newer versions compatible with Lion or downgrade to Snow Leopard:
    Downgrade Lion to Snow Leopard
    1.  Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Quit DU and return to the installer. Install Snow Leopard.
    This will erase the whole drive so be sure to backup your files if you don't have a backup already. If you have performed a TM backup using Lion be aware that you cannot restore from that backup in Snow Leopard (see below.) I suggest you make a separate backup using Carbon Copy Cloner 3.4.1.
    If you have Snow Leopard Time Machine backups, do a full system restore per #14 in Time Machine - Frequently Asked Questions.  If you have subsequent backups from Lion, you can restore newer items selectively, via the "Star Wars" display, per #15 there, but be careful; some Snow Leopard apps may not work with the Lion files.

  • Not supported hardware to boot from disk

    Hi everybody
    I have a problem by installing windows vista ultimate on my mac pro. All four disk bays contain the same harddrive (Samsung HD501LJ). Bay 1+2 are configured in a RAID0 array,. Bay3 is a native disk for windows and bay4 is used for the new timemachine feature under Mac OS X Leopard.
    I have partitioned the drive with "Mac OS X Extended (Journaled)" and set up a second parition with boot camp assistent for windows vista (MS-DOS; 32GB).
    In the windows installation wizard, the partition was recognized as "Drive 3, Parition 2 - BOOTCAMP). To boot from this disk, windows vista needs NTFS formatting, so I have run the "Format" Wizard, which was successful.
    After this step, the setup returns the following error:
    "This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computers's BIOS menu."
    "Windows is unable to find a system volume that meets its criteria for installation."
    Anybody an idea, what's going wrong here?

    Thanks for you reply.
    I have also tried to install windows vista on a single partition/harddrive. Bootcamp fromats the drive with FAT32, the vista installer do the rest and format the drive with NTFS. The result is the same. Diskspace is now 450gb (hole disk)
    Could it be, that the raid0 array for my os x 10.5 make troubles? The drive on which I want to install windows, is not in this raid0 array!
    Or do I have to install 64bit-os-version for my mac pro? (xeon 64bit cpus)

  • You can't open the application "System Preferences.app" because it is not supported on this type of Mac

    All of the sudden my System Preferences in Mavericks has stopped working and I get the error message:
    You can't open the application "System Preferences.app" because it is not supported on this type of Mac.
    It was working fine before this, and I have run Permissions Repair, restarted to another partition and run Diskwarrior and TechTool Pro, but none of those has helped. Anyone have any ideas why this happened, and what I can do to fix it?

    See this entire thread
    https://discussions.apple.com/message/4241006#4241006

  • NFS not supported in ORACLE VM???

    Hi All,
    I have installed Oracle VM server 2.2 and on top of that I have created 2 vms using OVM template (template is : OVM_EL5U2_X86_64_PVM_4GB) . Now I want to create one shared partition between these two created VMs, I am using simple "nfs" in mount command, it will not give any error but it also not mounted.
    What is the reason? Does VM template not supported nfs filesystem or what?
    Any suggestion if I want to share any partition between those created VMs?
    Thanks...

    Hi,
    if you just want to share a device between 2 guests running on the same server (or in the same serverpool with the same storage), why not simply add a shared disk?
    This can be done via. OVM manager, or you can simple add the shared images with the w! flag in the vm.cfg:
    disk = ['file:/var/ovs/mount/9EAC332154064688B8D112132DA91A1A/running_pool/vm1/System.img,xvda,w',
    'file:/var/ovs/mount/43ABF76E65B24586A4330413C93B51EF/sharedDisk/shared1.img,xvdb,w!',
    However if you absolutely need an NFS share (from the OVS server), be aware that a standard OVS Server has the firewall enabled...
    Disable it via:
    # system-config-securitylevel
    And start the NFS service + do the export:
    # service nfs start
    # exportfs *:/path
    Regards
    Sebastian

Maybe you are looking for