[Solved]Vmware Player - Blocking File System not fails to load

All the mods load fine, except Vmblock.
this is what i get when i run vmplayer.
make: *** /tmp/modconfig-NtGU4D/vmblock-only: No such file or directory. Stop.
Starting VMware Services:
Virtual machine monitor....
(finishes loading without problems)
i suspect this has to do with the fact that i couldn't patch it following the wiki's guide (vmnet patched fine).
I have the latest vmware player and the current arch linux kernel (3.10.7-1)
The patch doesn't seem to find the file it's meant to patch.
I'd also like to know if i can safely ignore this.
Edit: I suspect i just made a failure during the installation, i reinstalled it and it loaded this time... i think.
Last edited by rabcor (2013-08-23 09:10:09)

andy_v wrote:Make sure you create a 'compiz.desktop' file under /usr/share/applications.
And that fixed it! Don't know how I overlooked that. Thanks!

Similar Messages

Disk Utility can't format my external HD - File System Formatter fails

Hi. I have a Freecom 1.5TB external hardrive that is connected by firewire to my Intel iMac. The drive has worked fine for a year and then suddenly the "error 36 code" appeared and nothing else could be saved to the drive.
Disk Utility told me that it could not repair the disk and that I should format it. At this stage the problems start!
DU fails to format the drive with the error "File System Formatter Failed."
I have read various conversations on this error on these forums and followed the instructions but nothing has worked. I have already
1) Partioned the disk making sure it is "GUID" - then formatted and it still fails
2) Used MS DOS to do it but that also fails.
I have noticed that the SMART status is "not recognised".
Is there anything else that I can do or am I just doing this wrong? I am thinking that I might be able to do something using the start-up disks but I don't know how to do that and don't want to jepardise my iMac whichis otherwise working fine!
Any help appreciated.
Rob

I went crazy last night with the same issue trying to format my Toshiba external drive. I could format as MSDOS but not Mac journaled. I tried the guid partition scheme etc... no luck. Then I read somewhere that Leopard has an issue with the partitioning schemes. I hooked it up to my macbook on Tiger and whalla, formatted no problem. Then I was able to hook it up to Time Machine and let it reformat it on my Snow Leopard version of OSX on the iMac. I'm on OSX 10.6.8.

Boot up - Error Message: "File System not clean"

<blockquote>Locked by Moderator as a duplicate/re-post.
Please continue the discussion in this thread: [tiki-view_forum_thread.php?locale=en-US&comments_parentId=667528&forumId=1]
Thanks - c</blockquote>
== Issue
==
I have another kind of problem with Firefox
== Description
==
At start up displays error message: File System not Clean"
== start up computer
==
== Troubleshooting information
==
WebOfTrust, AdBlock Plus 1.2, Ubuntu Firefox Modifications 0.7, Firefox Universal Uploader (fireuploader) 0.4.1, Foxytunes 4.0.6
== Firefox version
==
3.0.19
== Operating system
==
Linux
== User Agent
==
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.19) Gecko/2010040116 Ubuntu/9.04 (jaunty) Firefox/3.0.19 GTB7.0
== Plugins installed
==
*-The default plugin handles plugin data for mimetypes and extensions that are not specified and facilitates downloading of new plugins.
*The demo print plugin for unix.
*Shockwave Flash 10.0 r45
*DivX Web Player version 1.4.0.233
*The Totem 2.26.1 plugin handles video and audio streams.

http://ubuntuforums.org/

[Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH

Hi,
i followed the instructions here https://wiki.archlinux.org/index.php/VM … n.2FPlayer
while running the modconfig command i get this error.
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
In file included from /tmp/vmware-root/modules/vmnet-only/bridge.c:51:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/bridge.o] Fehler 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfSetup«:
/tmp/vmware-root/modules/vmnet-only/netif.c:149:7: Fehler: »struct net_device« hat kein Element namens »init«
/tmp/vmware-root/modules/vmnet-only/netif.c:150:7: Fehler: »struct net_device« hat kein Element namens »open«
/tmp/vmware-root/modules/vmnet-only/netif.c:151:7: Fehler: »struct net_device« hat kein Element namens »hard_start_xmit«
/tmp/vmware-root/modules/vmnet-only/netif.c:152:7: Fehler: »struct net_device« hat kein Element namens »stop«
/tmp/vmware-root/modules/vmnet-only/netif.c:153:7: Fehler: »struct net_device« hat kein Element namens »get_stats«
/tmp/vmware-root/modules/vmnet-only/netif.c:154:7: Fehler: »struct net_device« hat kein Element namens »set_mac_address«
/tmp/vmware-root/modules/vmnet-only/netif.c:155:7: Fehler: »struct net_device« hat kein Element namens »set_multicast_list«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfNetDeviceToNetIf«:
/tmp/vmware-root/modules/vmnet-only/netif.c:196:14: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIf_Create«:
/tmp/vmware-root/modules/vmnet-only/netif.c:311:4: Fehler: Implizite Deklaration der Funktion »compat_alloc_netdev« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/netif.c:311:8: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/netif.c:316:7: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfReceive«:
/tmp/vmware-root/modules/vmnet-only/netif.c:397:4: Warnung: Übergabe des Arguments 1 von »netif_running« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifOpen«:
/tmp/vmware-root/modules/vmnet-only/netif.c:477:4: Warnung: Übergabe des Arguments 1 von »netif_start_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifClose«:
/tmp/vmware-root/modules/vmnet-only/netif.c:525:4: Warnung: Übergabe des Arguments 1 von »netif_stop_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:236:1: Warnung: Kontrollfluss erreicht Ende von Nicht-void-Funktion [-Wreturn-type]
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Unable to install vmnet
Maybe someone has an idea whats going wrong ?
stubb
Last edited by stubb (2011-12-01 23:45:44)

rm /usr/lib/vmware/modules/source/.patched
fixed it

PSE 6.0 on Mac: File system not supported

Downloaded PSE 6.0 as root on 10.5.6, PPC G5 w/ Mac OS Extended (Case-sensitive Journaled) FS. When I began install, got "file system not supported." Any ideas? Thanks.

Ah, yes, then you're one of the few people who come here who've done that who have a reason. The average person who has trouble resulting from this just randomly chose that option when formatting (lots of people think they won't be able to use capital letters in file names if they don't). Unfortunately, just for future reference, I believe this is a problem with all adobe products. I know it's the same with Photoshop.

When i was partitioning my hard drive i ran out of power (so it closed in the middle of the process). now when i try to partition it says Couldn't modify partition map because file system verification failed.

When i was partitioning my hard drive i ran out of power (so it closed in the middle of the process). now when i try to partition it says Couldn’t modify partition map because file system verification failed.

You'll have to select the entire external hard drive by the hardware name itself and then apply a new partition table to it under the Partition tab of Disk Utility. Erase and format the drive.
GUID for OS X.

Error message "file system formatter failed"

Hi
I just bought a MyBook 1TB external drive to use as a vault for Aperture. It comes formatted FAT32, however, it appears you can't use FAT32 for vaults. So I have tried to reformat it to MacOS extended, and MacOS extended journaled, however it fails after a few seconds with the message "File system formatter failed".
I am using Leopard, iMac20", 2.33ghz intel core 2 duo, 2gbRam. Any ideas , or is there some other third party software I could try?
thanks

Open up Applications / Utilities / Disk Utility.
In the column on the left there will be several lines for each storage device that presents itself to the system as a "disk". The first such line for any drive names the manufacturer and describes the drive hardware. That's the hardware description line.
Now a hard drive might be partitioned into several "logical volumes", each of which looks like a separate disk to the operating system. Each of those will be listed just under the hardware line for each of your drives -- indented a bit.
For drives that support removable media (such as your DVD drive), there will only be a volume line if there is currently media inserted in the drive.
Your main hard drive, the one you boot from, likely is partitioned into only one volume so there will only be one line following the hardware line and it will bear the name of your boot disk -- most likely "Macintosh HD".
Click on the hardware line to see the partitioning information for that particular physical disk drive at the bottom of the window.
Click on one of the volume lines indented below it (e.g., the "Macintosh HD" line) to see how that particular volume is formatted in its particular partition of the physical disk drive.
Partitioning is how the total physical space on the disk drive is divided and organized into one or more logical volumes. Formatting is how a given logical volume is structured for use by the operating system.
For PowerPC based Macs, the "default" partitioning should be Apple Partition Map (APM). For Intel based Macs the "default" partitioning should be GUID.
In either case, the "default" formatting should be Mac OS X Extended (Journaled).
--Bob

Some system rules failed to load.

Hello Every one
i have a problem with my Monitoring ,the alert which i receive continuously in My SCOM 2012 motoring console is..
The System Center Management Health Service 123-31234 running on host xxx-xxxx.Root.net and serving management group with id {0407FB6F-896A-7389-EA01-D60C72ABBD5A} is not healthy. Some system rules failed to load.
I restarted the Service System center Management Service,also delete the folder health service State folder to clear the cache,but still the problem is there.
and i am getting this message in the Event logs of faulty system
Faulting application name: MonitoringHost.exe, version: 7.0.8560.0, time stamp: 0x4f210669
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
Exception code: 0x40000015
Fault offset: 0x00000000000761c9
Faulting process id: 0xc2c
Faulting application start time: 0x01cfb546b794c320
Faulting application path: C:\Program Files\System Center Operations Manager\Agent\MonitoringHost.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCR100.dll
Report Id: 00042e99-213a-11e4-93f9-f4ce46830654
Faulting package full name:
and the event id is 1000
Thank You!

Have you upgraded your SCOM 2012?, please note, manually installed agents will NOT be updated automatically, you need to run the agent roll-up/upgrade by manually logging onto the servers
plz run the below PS to check the updates on your agents
Import-Module operationsmanager
$agents = get-scomagent
$value = $agents[0].HostedHealthService.GetMonitoringProperties() | ? {$_.Name -eq “PatchList”}
$agents | select version, Name, PrimaryManagementServerName, ManuallyInstalled, @{Label=”PatchList”; Expression={$_.hostedhealthservice.getmonitoringpropertyvalue($value)}} | sort primarymanagementservername, manuallyinstalled, version | ft -autosize
Faizan

How to solve "this type of file is not supported, or the required codec is not installed"?

Hi all,
I've just started using a new computer with WIndows 8.1 within the last week and have loaded my Adobe Premiere Elements 11.0 software into it.
In trying to view and edit a video I created on my old computer, I got "Media Pending" and "Media Offline" notices as soon as I began. The source files are located on an external drive with a permanent letter designation. I began the process of reconnecting my Project Assets files with the source files this morning, but have now encountered a new roadblock. Each time I try, I get the message "this type of file is not supported, or the required codec is not installed." It offers no information or options other than to click "OK," which is not very helpful.
All the source files are located in one folder on my external drive. I have been able to reconnect the JPEGs and the mp3 source files but not the AVI video files.
Here are three screenshots. The first is the "Media Offline" message, the second is the message I receive when I try to reconnect my Project Assets to the source files and the third is a screenshot of the codecs installed on the new computer.
Here is my new computer information:
Model: Del Inspiron 3847
Intel Core i5-4460
CPU @ 3.20 GHz 3.20 GHz
RAM 8 GB
System type: 64-bit, x64-based processor
I hope someone can guide me. What do I need to do to solve this problem?
Thank you.
Message was edited by: Janie Christensen Ficara

StreetSongs
Thank your for the information supplied.
But, what are the properties of this .avi file that you seek?
Video Compression
Audio Compression
Frame Size
Frame Rate
Interlaced or Progressive
Pixel Aspect Ratio
Right now of prime interest is the video compression that is being wrapped by that AVI wrapper/container.
AVCHD.avi
MotionJPEG.avi
XviD.avi
DviX.avi
other
There are instances were a particular video compression or a particular container/wrapper format is each supported by Premiere Elements, but
not a combo of those particular two. But, in this instance, I suspect this to be a MotionJPEG video codec issue, but your details will
point us to the actual situation, and we will plan troubleshooting strategy from there.
ATR

[SOLVED] VMware player, network doesn't work

Hi!
I installed VMware player through AUR and it works well. But when I started my vm (Debian 4.0) it asked if I had copied or moved it. I chose "I copied it" because I copied it from my hdd to external hdd. I started my vm but network didn't work. I configured network using vmware-config.pl file like it recommended (vmnet0 as bridged with my wlan0 and vmnet8 as NAT. I also chose to use host-only networking in my vm's (wmaster0)). How did you guys configured your network succesfully?
I just want it to work like on my windows box. It has it's own IP and I can connect to it's IP directly from firefox. Yeah, I run webserver on that vm.
My ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:656 errors:0 dropped:0 overruns:0 frame:0
TX packets:656 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24109 (23.5 Kb) TX bytes:24109 (23.5 Kb)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.22.1 Bcast:172.16.22.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:172.16.43.1 Bcast:172.16.43.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:1B:77:04:D4:D0
inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:77ff:fe04:d4d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22719 errors:0 dropped:0 overruns:0 frame:0
TX packets:14300 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14584732 (13.9 Mb) TX bytes:2004755 (1.9 Mb)
wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-04-D4-D0-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Last edited by Nuck (2008-07-12 18:27:49)

Nuck wrote:
Hi!
I installed VMware player through AUR and it works well. But when I started my vm (Debian 4.0) it asked if I had copied or moved it. I chose "I copied it" because I copied it from my hdd to external hdd. I started my vm but network didn't work. I configured network using vmware-config.pl file like it recommended (vmnet0 as bridged with my wlan0 and vmnet8 as NAT. I also chose to use host-only networking in my vm's (wmaster0)). How did you guys configured your network succesfully?
I just want it to work like on my windows box. It has it's own IP and I can connect to it's IP directly from firefox. Yeah, I run webserver on that vm.
My ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:656 errors:0 dropped:0 overruns:0 frame:0
TX packets:656 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24109 (23.5 Kb) TX bytes:24109 (23.5 Kb)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.22.1 Bcast:172.16.22.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:172.16.43.1 Bcast:172.16.43.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:1B:77:04:D4:D0
inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:77ff:fe04:d4d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22719 errors:0 dropped:0 overruns:0 frame:0
TX packets:14300 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14584732 (13.9 Mb) TX bytes:2004755 (1.9 Mb)
wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-04-D4-D0-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
set the network connection to NAT not BRIDGE (in the settings tab). i never got BRIDGE running, but i also haven't tried too hard.
Last edited by DonVla (2008-07-12 17:01:31)

Store documents in local machine of file system not in sap dms

Hi,
Can i store documents in local machine not in sap Database . Client will not use content server for storing document.
so how to store document in local file system n how to configure ?
please help.
Dipak.

Hello Sir,
When I try to check in in storage as 'VAULT' it send error 'Attempt to set up connection to failed'
attaching screen shot of error
I customize in DC20 for Vault:
For: "Define data carrier type "vault""
Data carr. type = ZD
For: "Define vault"
Data carr.name = ZDC_TEST
Data carr. type= ZD
Desprition = Test
Vault path = \\10.181.210.10\_SAP Practice\SAP DMS\DMS_Data_carrier -> this is the network path.
For: "Define data carrier type "server, front end"
Type (data carr. type) = DC
Description = Frontend test
Path = c:\temp\
For: "Define mount ponts/logical drive"
Data carr. = Default/ZDC
Prefix for access path = c:\temp\
Please tell me if have configured any wrong configuration or need to add any additional configuration
Thanks.
Dipak.

File system check fails "FATAL"

Dear all,
after about three of years of running, one of my Xsan filesystems died. The fsm process stops running after about 2 minutes in running state. A filesystem check with cvfsck -w -v <Name> ends with:
Creating Daten allocation check file.
Stripe Group Daten ( 0) 0xe8def800 blocks.
Building Inode Index Database 91458560 ( 52%).
Fatal: rf_relblk write failed - Input/output error
Building Inode Index Database 91459584 ( 52%).
Fatal: Cannot insert inotab for [0x32a9e378800]! -No such file or directory
Fatal: Cannot build inode tracking tree - Input/output error.
I cannot see any misbehaviour of the hardware itself. RAID Admin is green everywhere.
The filesystem size is about 17 TB and the data is quite important. Is there any way to proceed without re-formatting?
Some more information I found in the log files:
[0923 16:26:42] 0xa000ed88 (debug) FSS 'Experiments' REGISTERED -> DYING, next e
vent in 60s
[0923 16:26:43] 0x1802e00 INFO Disk rescan found 10 disks
[0923 16:26:43] 0xa000ed88 INFO NSS: Active FSS 'Experiments[0]' at 192.168.100.
10:49275 (pid 354) - dropped.
[0923 16:26:45] 0x1801600 ERR Portmapper: FSS 'Experiments' (pid 354) exited on
signal 4
[0923 16:26:45] 0x1801600 ERR FSS 'Experiments' appears unstable (2 failures in
60 minutes or less), halting restarts
[0923 16:26:45] 0x1801600 (debug) FSS 'Experiments' DYING -> STOPPED (corefile l
imit exceeded)
Any hint is really appreciated.
Best regards,
Torsten

Thanks for the hint. Well, the cvfsck -j command succeeded rather quickly. But the -w afterwards fails again:
Super Block information.
FS Created On : Wed Aug 31 13:24:34 2005
Inode Version : '2.3'
File System Status : Clean
Allocated Inodes : 173699072
Free Inodes : 37814385
FL Blocks : 9309
Next Inode Chunk : 0x2c05d400
Windows Security Indx Inode : 0x4
Windows Security Data Inode : 0x5
Quota Database Inode : 0x6
ID Database Inode : 0xb
Client Write Opens Inode : 0x7
Creating Daten allocation check file.
Stripe Group Daten ( 0) 0xe8def800 blocks.
Building Inode Index Database 91363328 ( 52%).
Fatal: Cannot insert inotab for [0x8261a053f400]! -No such file or directory
Fatal: Cannot build inode tracking tree - Input/output error.
Is there anything else I can do?
Thanks,
Torsten

[SOLVED] VMWare Player won't install

Hello,
I have a problem installing VMWare player on arch. (disclaimer: I have RTFM *and* searched and googled hehe)
I'm trying to install VMware-Player-2.5.1-126130.x86_64.bundle on the following machine:
Linux 2.6.29-ARCH #1 SMP PREEMPT x86_64 AMD Phenom(tm) 9850 Quad-Core Processor AuthenticAMD GNU/Linux
I was following the guide here: http://wiki.archlinux.org/index.php/Installing_VMware
and somewhat here: http://forums.fedoraforum.org/showthread.php?p=1126993
My problem is though when i run /usr/bin/vmplayer it complains that
Unable to build kernel module
See log file /tmp/vmware-root/setup-12218.log for details
and wont do anything else. I've basicly followed the guide I listed above in its steps so I'm a little lost now.
Any advice would be greatly appriciated as its for a university assigment im rapidly running out of time on heheh.
Regards,
Mike.
Last edited by DrMikeDuke (2009-04-05 16:50:59)

Thanks for your help so far, awesome!
I got it to work but a little differently since it still wouldnt patch for me
Anyhow Il post my solution here since i know I always hate visiting a
SOLVED thread only to find noone said HOW
So I move my file from binary to binary old
(mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old)
then i go to my source directory
(cd /usr/lib/vmware/modules/source)
i untar everything in sight (:P)
[root@TOMATO source]# ls
vmblock-only vmci.tar vmnet-only vmppuser.tar
vmblock.tar vmmon-only vmnet.tar vmware-workstation-2.6.29-v2.patch
vmci-only vmmon.tar vmppuser-only vsock.tar
then I used the scripts from here http://communities.vmware.com//thread/203231
Finally I run step 6). vmware-modconfig --console --install-all
And done!:D

File system not accesible when downloading adobe CS5

I am trying to download my adobe standard CS5 software on my new computer. While using download manager as suggested by the program, i get an error message saying that there is a problem with entering the computers file system. I should check whether the file system is accesible or not. How do I solve this?

Hi Hokus Pokus
Please download CS5 Trails from below link : http://prodesigntools.com/adobe-cs5-5-direct-download-links.html
Follow the instructions to Start your Download ...
Use your Serial Key to Activate them ....

File system not clean after hibernate or suspend

Hello everyone,
I followed the arch wiki to set-up pm-utils (https://wiki.archlinux.org/index.php/Pm-utils). I included the recover=[swap drive] in my grub configuration. Whenever, I run either pm-hibernate or pm-suspend, however, I am greeted with less than kind messages on reboot.
Checking File Systems
.....(first couple are fine)
Reiserfs
Filesystem is NOT clean
Replaying journal: Trans replayed: mountid 47, transid 2301, desc 4815, len 25, commit 4841, next trans offset 4824
.... (repeat nearly identical messages 17 times)
Replaying journals: Done
Reiserfs journal: '/dev/sda6' in blocks [18..8211]: 18 tranactions replayed
Somethins is going wrong when the disk is suspending and the filesystem is not liking it. Does anyone know what may be causing this and have any suggestions on what to do?
Thank you very much.
Last edited by Tripsun (2011-01-22 06:51:34)

Tripsun wrote:Is it possible that this error is due to the fact that I am using reiserfs for my /var partition? The current setup of my partition is /boot, /, /home, /usr, /tmp all using ext3; /var using reiserfs; and swap. Would the issue maybe be resolved if I switch /var to something like ext4 or JFS?
ReiserFS has nothing to do with your problem (I also have /var/ on reiser and suspend works fine).
Your {pm-suspend,messages,kernel}.log would be helpful here...

[Solved]Vmware Player - Blocking File System not fails to load

Similar Messages

Maybe you are looking for