Failed reresh filesystem on openfiler
I have nfs on openfiler 2.99 with OVM 3.0.2 and i cant refresh file system. I got next error message:
ob Construction Phase
begin()
Appended operation 'FileSystem refresh' to object '56fb1e82-1db9-4cee-a360-7c94fbbb11ac (nfs:/mnt/volgrp1/ofs/stgp)'.
commit()
Completed Step: COMMIT
Objects and Operations
Object (IN_USE): [NetworkFileSystem] 56fb1e82-1db9-4cee-a360-7c94fbbb11ac (nfs:/mnt/volgrp1/ofs/stgp)
Operation: FileSystem refresh
Object (IN_USE): [NetworkFileServer] 0004fb0000090000a84c9f160f156b70 (nfsstg)
Object (IN_USE): [Server] 4b:16:45:2a:1d:d0:e5:41:e3:32:00:1c:25:6a:0b:f5 (ovmsrv)
Job Running Phase at 12:31 on Fri, Dec 9, 2011
Job Participants: [4b:16:45:2a:1d:d0:e5:41:e3:32:00:1c:25:6a:0b:f5 (ovmsrv)]
Actioner
Starting operation 'FileSystem refresh' on object '56fb1e82-1db9-4cee-a360-7c94fbbb11ac (nfs:/mnt/volgrp1/ofs/stgp)'
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_mount] failed for storage server [0004fb0000090000a84c9f160f156b70] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011] OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
at com.oracle.ovm.mgr.action.StoragePluginAction.processException(StoragePluginAction.java:1287)
at com.oracle.ovm.mgr.action.StoragePluginAction.mountFileSystem(StoragePluginAction.java:1098)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverNfsFileSystem(FileSystemRefresh.java:114)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:78)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:223)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
at com.oracle.ovm.mgr.action.StoragePluginAction.mountFileSystem(StoragePluginAction.java:1094)
... 17 more
Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:752)
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
... 20 more
FailedOperationCleanup
Starting failed operation 'FileSystem refresh' cleanup on object 'nfs:/mnt/volgrp1/ofs/stgp'
Complete rollback operation 'FileSystem refresh' completed with direction=nfs:/mnt/volgrp1/ofs/stgp
Rollbacker
Objects To Be Rolled Back
Object (IN_USE): [NetworkFileSystem] 56fb1e82-1db9-4cee-a360-7c94fbbb11ac (nfs:/mnt/volgrp1/ofs/stgp)
Object (IN_USE): [NetworkFileServer] 0004fb0000090000a84c9f160f156b70 (nfsstg)
Object (IN_USE): [Server] 4b:16:45:2a:1d:d0:e5:41:e3:32:00:1c:25:6a:0b:f5 (ovmsrv)
Completed Step: ROLLBACK
Job failed commit (internal) due to OVMAPI_B000E Storage plugin command [storage_plugin_mount] failed for storage server [0004fb0000090000a84c9f160f156b70] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011] OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_mount] failed for storage server [0004fb0000090000a84c9f160f156b70] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011] OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
at com.oracle.ovm.mgr.action.StoragePluginAction.processException(StoragePluginAction.java:1287)
at com.oracle.ovm.mgr.action.StoragePluginAction.mountFileSystem(StoragePluginAction.java:1098)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverNfsFileSystem(FileSystemRefresh.java:114)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:78)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
at sun.reflect.GeneratedMethodAccessor1036.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:223)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_mount to server: ovmsrv failed. OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
Fri Dec 09 12:35:39 CET 2011
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
at com.oracle.ovm.mgr.action.StoragePluginAction.mountFileSystem(StoragePluginAction.java:1094)
... 17 more
Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: storage_plugin_mount, Status: oracle.generic.NFSPlugin.GenericNFSPlugin /OVS/Repositories/56fb1e82-1db9-4cee-a360-7c94fbbb11ac []
Fri Dec 09 12:35:39 CET 2011
at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:752)
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
... 20 more
End of Job
[root@ovmsrv ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 3.0G 576M 2.2G 21% /
/dev/sda1 101M 37M 59M 39% /boot
tmpfs 288M 6.5M 281M 3% /dev/shm
none 283M 40K 283M 1% /var/lib/xenstored
192.168.12.145:/mnt/volgrp1/ofs/stgp
11G 156M 11G 2% /ovs_mount_tempdDb0ZT
[root@ovmsrv ~]# cd /ovs_mount_tempdDb0ZT/
[root@ovmsrv ovs_mount_tempdDb0ZT]# ls
Restart/reboot does not help.
on the openfiler i have two disk, iscsi type attached to OVM. But i cannot use them for repository creation - drop down list with physical disks is empty.
please any ideas ?
thank you advance.
Ondrej
Edited by: user10708485 on Dec 9, 2011 3:41 AM
I find the problem. I just add a folder named userfiles and its subfolders (according to website of fckeditor) to the application directory.
Similar Messages
-
Filesystem check failed, but filesystems are clean
Im running custom kernel and this might be related to it, but Im on my wits' end here and looking for pointers.
The problem is, Im getting filesystem check failed every time I boot my system. And it gives no apparent reason
for it to happen. I have fsck'd my partitions many times and they are clean. My hwclock is in time and rc.conf is set
to 'localtime'. The problem didn't occurs on the previous kernel (2.6.18) I had, so I've been using its running config to
compile the new one (2.6.23). The thing is, the previous kernel works fine, no filesystem check failed in boot. Only
difference between those two is I had to enable HOTPLUG in the newer kernel to get udev working, otherwise it would
complain about failing netlink socket in initscript.
As a temporary solution, I commented out the filesystem check from the rc.sysinit and it boots further. This time
it fails to mount my /boot/ and /home/ directory and fails to activate my swap. Effectively only root is mounted, but
after logging in, "mount -a" works without any problems and I can use my system normally.
I have compiled all(?) the needed modules to the kernel, so initramfs shouldn't be needed, but I've tried it anyway, no
luck there. The system is build with 2009.08 core install disc, no packages updated as far as I recall.
fstab:
#none /dev/pts devpts defaults 0 0
#none /dev/shm tmpfs defaults 0 0
/dev/hdb /media/cdrom 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
/dev/disk/by-uuid/728c65f2-a84f-401f-9899-17020758b829 /boot ext3 defaults 0 1
/dev/disk/by-uuid/2767f772-203a-4fe9-ac4d-7c8754abc4c8 swap swap defaults 0 0
/dev/disk/by-uuid/b0b958c4-5f24-414a-8826-6df956f0815b / reiserfs defaults 0 1
/dev/disk/by-uuid/e83b7114-86fe-4e8f-9e95-0d92b8e50d1a /home reiserfs defaults 0 1
dmesg:
Linux version 2.6.23-xbox (root@xbox) (gcc version 4.1.2) #3 Sat Oct 2 14:20:54 EEST 2010
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000003c00000 (usable)
BIOS-e820: 0000000003c00000 - 0000000004000000 (reserved)
60MB LOWMEM available.
Entering add_active_range(0, 0, 15360) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 15360
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 15360
On node 0 totalpages: 15360
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 88 pages used for memmap
Normal zone: 11176 pages, LIFO batch:1
Movable zone: 0 pages used for memmap
DMI not present or invalid.
Allocating PCI resources starting at 10000000 (gap: 04000000:fc000000)
Built 1 zonelists in Zone order. Total pages: 15240
Kernel command line: root=/dev/hda3 devfs=mount kbd-reset xbox=hdd
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 256 (order: 8, 1024 bytes)
Detected 733.370 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 57652k/61440k available (1764k kernel code, 3380k reserved, 470k data, 136k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffffb000 - 0xfffff000 ( 16 kB)
vmalloc : 0xc4800000 - 0xffff9000 ( 951 MB)
lowmem : 0xc0000000 - 0xc3c00000 ( 60 MB)
.init : 0xc0332000 - 0xc0354000 ( 136 kB)
.data : 0xc02b90ae - 0xc032ea60 ( 470 kB)
.text : 0xc0100000 - 0xc02b90ae (1764 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1467.98 BogoMIPS (lpj=2935965)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000 00000000
Compat vDSO mapped to ffffe000.
CPU: Intel Celeron (Coppermine) stepping 0a
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: Using configuration type 1
Setting up standard PCI resources
SCSI subsystem initialized
libata version 2.21 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Cannot allocate resource region 7 of bridge 0000:00:08.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:08.0
PCI: Cannot allocate resource region 9 of bridge 0000:00:08.0
PCI: Bridge: 0000:00:08.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Failed to allocate mem resource #2:80000@f8000000 for 0000:01:00.0
PCI: Failed to allocate mem resource #6:10000@f8000000 for 0000:01:00.0
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: fd000000-fdffffff
PREFETCH window: f0000000-f7ffffff
PCI: Setting latency timer of device 0000:00:08.0 to 64
NET: Registered protocol family 2
Time: tsc clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 325k freed
Enabling Xbox eject problem workaround.
fuse init (API version 7.8)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
xboxfb: nVidia device/chipset 10DE02A0
xboxfb: Detected 64MB of system RAM
xboxfb: Using 4M framebuffer memory
i2c-xbox.o version 0.0.1
i2c-xbox.o: Found nVidia XBOX nForce SMBus controller.
i2c-xbox.o: SMBus bus detected and initialized
xbox-tv-i2c: Using 'SMBus adapter at c000'!
xboxfb: Setting TV mode from EEPROM (NTSC)
xboxfb: detected conexant encoder
xboxfb: Setting cable type from AVIP ID: HDTV (Component video)
xboxfb: RIVA MTRR set to ON
Console: switching to colour frame buffer device 80x30
xboxfb: PCI nVidia NV20 framebuffer ver 0.9.5b-xbox (XboxGeForce3, 4MB @ 0xF3C00000)
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.102
[drm] Initialized drm 1.1.0 20060810
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
PCI: Setting latency timer of device 0000:00:04.0 to 64
eth0: forcedeth.c: subsystem: 00000:0000 bound to 0000:00:04.0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE: IDE controller at PCI slot 0000:00:09.0
NFORCE: chipset revision 212
NFORCE: not 100% native mode: will probe irqs later
NFORCE: 0000:00:09.0 (rev d4) UDMA100 controller
ide0: BM-DMA at 0xff60-0xff67, BIOS settings: hda:DMA, hdb:DMA
Probing IDE interface ide0...
hda: WDC WD2500JB-00FUA0, ATA DISK drive
hdb: PHILIPS XBOX DVD DRIVE, ATAPI CD/DVD-ROM drive
hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
hda: selected mode 0x42
hdb: selected mode 0x42
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 512KiB
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(33)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4
hdb: ATAPI DVD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:02.0: irq 1, io mem 0xfed00000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
PCI: Setting latency timer of device 0000:00:03.0 to 64
ohci_hcd 0000:00:03.0: OHCI Host Controller
ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:03.0: irq 9, io mem 0xfed08000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
usb 1-3: new low speed USB device using ohci_hcd and address 2
usb 1-3: configuration #1 chosen from 1 choice
input: DELL DELL USB Keyboard as /devices/pci0000:00/0000:00:02.0/usb1/1-3/1-3:1.0/input/input0
usbcore: registered new interface driver usbkbd
drivers/hid/usbhid/usbkbd.c: :USB HID Boot Protocol keyboard driver
usbcore: registered new interface driver usbmouse
drivers/hid/usbhid/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
TCP cubic registered
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 136k freed
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
NET: Registered protocol family 1
spurious 8259A interrupt: IRQ7.
udev: starting version 141
df -h after "mount -a":
Filesystem Size Used Avail Use% Mounted on
/dev/disk/by-uuid/b0b958c4-5f24-414a-8826-6df956f0815b
7.4G 2.1G 5.3G 29% /
/dev/hda1 99M 11M 83M 12% /boot
/dev/hda4 226G 39M 226G 1% /home
Ok, something is definately wrong there, only root is by-uuid
blkid:
/dev/hda3: UUID="b0b958c4-5f24-414a-8826-6df956f0815b" TYPE="reiserfs"
/dev/hda2: TYPE="swap" UUID="2767f772-203a-4fe9-ac4d-7c8754abc4c8"
/dev/hda4: UUID="e83b7114-86fe-4e8f-9e95-0d92b8e50d1a" TYPE="reiserfs"
/dev/hda1: UUID="728c65f2-a84f-401f-9899-17020758b829" SEC_TYPE="ext2" TYPE="ext3"
Should I try newer udev? Can I even use the latest with 2.6.23?Mounting Local Filesystems fails
Mount: Special device /dev/disk/by-uuid/728c65f2-a84f-401f-9899-17020758b829 does not exist
Mount: Special device /dev/disk/by-uuid/e83b7114-86fe-4e8f-9e95-0d92b8e50d1a does not exist
so does Activating swap.
still, ls -la /dev/disk/by-uuid/ gives me:
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 2767f772-203a-4fe9-ac4d-7c8754abc4c8 -> ../../hda2
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 728c65f2-a84f-401f-9899-17020758b829 -> ../../hda1
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 b0b958c4-5f24-414a-8826-6df956f0815b -> ../../hda3
lrwxrwxrwx 1 root root 10 2010-10-02 22:45 e83b7114-86fe-4e8f-9e95-0d92b8e50d1a -> ../../hda4
should I have /boot and /home in /dev?
Full system upgrade gave me the same issue. Even after udev downgrade (udev-142 is the latest I can use with 2.6.23).
Edit:
Changed my fstab back from by-uuid to hdaX, didn't help. Strangely all hdaX are in /dev/ after boot, but the symlinks are missing.
Last edited by TelaKeppi (2010-10-02 21:22:53) -
2nd try and installation still fails at filesystem check PLEASE HELP
This is my second install of Arch.....and it failed again. It said it could not locate the super block for /root. I used the by-label naming scheme and had a /boot, swap, /root and /home directory. /root and /home were both ext4, /boot was ext2. For some reason when checking file systems it could not locate the superblock on /dev/disk/by-label/root. When i tried to use the by-label to replace the superblock it could not be found so i had to use /dev/sda3 (which was /root) I tired several different superblocks (located with systemrescuecd-testdisk) with no success. obviously i am doing something wrong and i would really like to fix it....when i try to access /etc/fstab it says permission denied....i was going to try and rename them by uuid but if i cant get in here i dont know how i would. i already got the uuid for each partition its just a matter of assigning it in fstab now i think.......i really dont wanna give up on arch so please help me out.
JoeKer1086 wrote:This is my second install of Arch.....and it failed again. It said it could not locate the super block for /root. I used the by-label naming scheme and had a /boot, swap, /root and /home directory. /root and /home were both ext4, /boot was ext2. For some reason when checking file systems it could not locate the superblock on /dev/disk/by-label/root. When i tried to use the by-label to replace the superblock it could not be found so i had to use /dev/sda3 (which was /root) I tired several different superblocks (located with systemrescuecd-testdisk) with no success. obviously i am doing something wrong and i would really like to fix it....when i try to access /etc/fstab it says permission denied....i was going to try and rename them by uuid but if i cant get in here i dont know how i would. i already got the uuid for each partition its just a matter of assigning it in fstab now i think.......i really dont wanna give up on arch so please help me out.
...Wait a sec. i am not going to make fan of you.but i must ask this for sure..
you know? "/" (pronounce root) is not /root. you need / . Did you make / ? if you dont have / you cant set /root as a system. i dont know what is the matter of superblock by the post (no enough info). well, i am asking where is the / because you didnt mention this at all. maybe you created / and call it /root?
try it more simple. you only need / and swap partition to install(after you finish installation you can make rest of partitions if you have space)
the point of Arch installation is you better finish it as simple as you can, then setup others after you boot from Archlinux.
Arch installer is far from perfect. (just it is enough to complete installation) -
I think I may have a virus on my MacBook laptop, ran disk utility, "filesystem verify failed." Help!
I'm running a MacBook laptop and thought I might have a virus b/c i was browsing online a couple of days ago when i clicked on a link that appeared to automatically start downloading a file. I tried to stop it from downloading by clicking "cancel" in the downloads box that came up, but it compleatly downloaded before i could hit cancel. No programs automatically opened and started runnning (that i could see), but I've noticed slow browsing since then.
I ran the disk utility, "verify disk," to see if there were any problems. It came back with this error message: "First aid failed: Disk Utility stopped verifying "Macintosh HD" because the following error was encountered:
Filesystem verify or repair failed"
The text is black inside the verifying history box until the last three lines, which say in red:
"Invalid node structure
Volume check failed
Error: Filesystem verify or repair failed."
Does this mean I have a virus? Are there other things I can do to confirm that I do or do not have a virus? How do I fix this problem?
I'm running Mac OS X 10.5.8.
Many thanks for your advice/comments in advance.Probably because the directory on the disk is corrupt.
The error "invalid node structure" is one that will take either DiskWarrior or a reformat to fix.
It has not to with any malware.
Allan -
[SOLVED] Filesystem check failed on LVM partition...
My server experienced a power outage last night, and I noticed today that it wasn't booting correctly. Apparently, the storage partition, /dev/mapper/VolGroup00-lvolstorage fails the filesystem check. The first time I booted into it, I ran a manual check and answered (y) to the questions. Now when booting, it quickly displays a bunch of numbers and that scrolls for a little while (goes too fast to understand what they are...). Then it says:
####Filesystem Check Failed####
Please repair manually, blah blah blah
I'm not really sure what to do. Running fsck does the whole numbers scrolling across the screen thing again, finally asking if I want to clone multiply-claimed blocks... =/ I don't want to answer yes anymore until I get someone's input. <_<
EDIT: It said before that there are 81 inodes containing multiply-claimed blocks... Then it said a certain large file (inode #20) has 27818 multiply-claimed blocks shared with 24 other files, and it then lists other files.
Last edited by XtrmGmr99 (2010-05-21 14:14:25)It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.
-
Using fsck on internal slave bus and "Filesystem verify or repair failed"
Hello-
I had to move quite a few files today and in the blink of the eye, I lost my internal 200gig drive on the slave bus. Disk Utility sees the disk but will not mount the volume, giving the error "Invalid B-tree node size: 2010-08-08 22:24:33 -0500: Volume check failed. Filesystem verify or repair failed." Stellar Phoenix sees all the files but I can hardly afford $99 at the moment.
Can I reboot in Safe Mode and access the slave drive through fsck? Or is fsck -fy only for the startup drive?
Thank You.
RickUnfortunately, fsck cannot repair that error any more than Disk Utility. You need Disk Warrior to repair the drive assuming it's even repairable.
-
Western Digital 1TB Hard D "Error: Filesystem verify or repair failed."
I've had this external Western Digital hard drive for a year, it stopped working, tried to repair in disc utility, repair/verify failed
"Error: Filesystem verify or repair failed."
thats all i get!
now what do i do?If you have the data backed up, try using Disk Utility's Erase tab to reformat it. Then restore the data from backup.
If you have no backups, you might have good luck with DiskWarrior. It costs about $100.
If neither of those help, it sounds like the drive is dead. -
External Hard Disk Error - Error filesystem verify or repair failed
Hi
I can't seem to mount my WD external hard disk. Run Disk Utility and these are the error messages:
Invalid node structure
Invalid node structure
Catalog file entry not found for extent
Volume check failed
Error: Filesystem verify or repair failed
Does anyone know what is wrong and how do I fix this problem? Is it a hard disk failure? Will I be able to recover my data? Thanks!
_These are are hard disk specs:_
Manufacturer: WD
Model: 0x1103
GUID: 0x90A90464263DC1
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
My Book Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x1028
Product Revision Level: 1028
Sub-units:
My Book SBP-LUN:
Capacity: 931.51 GB
Removable Media: Yes
BSD Name: disk1
Mac OS 9 Drivers: No
Partition Map Type: APM (Apple Partition Map)
S.M.A.R.T. status: Not Supported
My Book Device Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x1028
Product Revision Level:
Sub-units:
My Book Device SBP-LUN:You will need Disk Warrior to fix the problem if Disk Utility cannot. However, to fix with DU you need to do this:
Repairing the Hard Drive and Permissions
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, Leopard or Snow Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X. -
Filesystem verify or repair failed
Guys i also have the same problem, i try to insert my hard drive and it says "the disk inserted is not readeabe by this computer" but when I open disk utility to repair it says "First Aid failed, Error: filesystem verify or repair failed". I am very frustrated, my work is due next week and most of it is in the drive. Please help. :-(
Hello,
You must repair the HD, if Disk Utility or fsck should fail to repair it, your best bet is DiskWarrior from Alsoft, you'll need the CD to boot from if you don't have another boot drive...
http://www.alsoft.com/DiskWarrior/
Your best bet is DiskWarrior, you need the CD/DVD though.
http://www.alsoft.com/DiskWarrior/
But others that may work…
Drive Genius…
http://www.prosofteng.com/products/drive_genius.php
TechTool Pro…
http://www.micromat.com/index.php?option=com_content&task=view&id=31&Itemid=83 -
Invalid key length, disk repair fails
i am getting this disk error after macbookpro locks up, repeatable.
invalid key length
volume check failed
error: filesystem verify or repair failed.
this is the boot volume of the macbookpro running os 10.5.6. been running well for months, used everyday all day, then this am the finder and all other apps lock up, no application crash, just all hanging one after another. hard reset gets system back but it recurs in short order.
i ran diskutil from the software restore dvdrom, three times. same results (error text above) each time. only option barring other solutions is to reinstall the system and restore data from a time machine bu.
never seen this before. any ideas?
thanks.thanks for hint on diskwarrior. i am running it but it is encountering quite a pile, i've never seen a problem like this. the sys log on the system that's running dw is full of:
App: disk14s2: Read I/O error for block range 324751 to 324751
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: Disk sector 324751 is bad. (JSC)
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: disk14s2: Read I/O error for block range 324752 to 324752
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: Disk sector 324752 is bad. (JSC)
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: disk14s2: Read I/O error for block range 324753 to 324753
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: Disk sector 324753 is bad. (JSC)
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: disk14s2: Read I/O error for block range 324754 to 324754
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: Disk sector 324754 is bad. (JSC)
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: disk14s2: Read I/O error for block range 324755 to 324755
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: Disk sector 324755 is bad. (JSC)
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: disk14s2: Read I/O error for block range 324756 to 324756
Jan 27 00:49:29 server [0x0-0xba4ba4].com.alsoft.diskwarrior[9656]: DiskWarrior App: Disk sector
this does not bode well. i have no idea what has caused this disk to totally dump on me. almost feels like a virus -- it was such a sudden and complete meltdown with no precursor whatsoever. i am running dw on it in target mode but seems like i might have to frag it. crazy.
thanks for further thoughts if anyone has any.
Message was edited by: dtich -
I had to boot from the install disc today, and in trying to verify the disk I get this message:
Invalid node structure, Volume check failed, Error: Filesystem verify or repair failed. What should I do?
The reason I'm trying to boot from the disc is because my computer stopped booting up a few days ago -- it gets to the apple logo and a loading bar, then shuts off.Where is your install package that shipped with your Mac when new?
Always better to run Disk First Aid repair via Disk Utility when booted from your install disc with using fsck as an alternate only when your install package is not available.
If there is a directory issue with your boot volume that Disk First Aid repair or fsck cannot successfully repair after running it several times, the problem is substantial and your options at that point are using a more substantial disk repair utility such as DiskWarrior (with no guarantee but DW has been known to work miracles) or backup all data and reformat the hard drive with the install package that shipped with your Mac and then re-install OS X and all applications.
Hopefully you maintain a regular backup and updated your backup recently and if not, now is a good time to start for this very important reason and for other good reasons.
You can can also check the S.M.A.R.T. status of the drive via Disk Utility when booted from your Tiger install disc.
http://www.thexlab.com/faqs/repairprocess.html
http://www.thexlab.com/faqs/durepairfns.html -
Main drive Verify & Repair failed
I've got a problem. I was using Drive Genius to Defrag my Main drive. The application crashed in the middle of its run. The drive would then not mount on the desktop. I ran Disk Utility and received the following:"Volume check Failed----Volume: Filesystem Verify or Repair Failed. I rebooted using my backup. On boot-up a dialog box informed me that for a limited time the main drive would mount and to backup the drive. Disk Utility would not let me backup the drive. I tried to copy some critical files, from the main drive to the backup. I tried to reboot nothing. I did boot from the Install DVD, ran Disk utility. Got the same Verify/Repair failed message from both main & backup drive. Is there any thing I can try to recover my applications & data files??????????
Mr Beavis wrote:
I've got a problem. I was using Drive Genius to Defrag my Main drive. The application crashed in the middle of its run. The drive would then not mount on the desktop. I ran Disk Utility and received the following:"Volume check Failed----Volume: Filesystem Verify or Repair Failed. I rebooted using my backup. On boot-up a dialog box informed me that for a limited time the main drive would mount and to backup the drive. Disk Utility would not let me backup the drive. I tried to copy some critical files, from the main drive to the backup. I tried to reboot nothing. I did boot from the Install DVD, ran Disk utility. Got the same Verify/Repair failed message from both main & backup drive. Is there any thing I can try to recover my applications & data files??????????
First, I would never use a defrag app on any of my Apple HDs. No need for it and as you see, lots of potential problems.
Your HD may have been bad before defragging, which is why it failed (doesn't it first run it's own DU to check the HD???) but that's why we have TimeMachine.
I am sure that the defrag program warns to backup before defragging. If not, it's not worth keeping.
So you first need to boot into the Leopard DVD and reformat and partition your drive and then run DU to check if it is intact. If you still have HD errors, you need a new drive.
Whatever the outcome, after booting into the Leopard DVD, you will see in the Utilities menu a restore option, which will allow you to recover your system previous to the disaster, and start again. -
[SOLVED] Netbooting with PXE, TFTP and NFS / Numerous errors
Greetings all, hope you can help me out.
Been given a task by my company of making a network bootable ICA client (with X and Firefox, with the Citrix ICA client installed) as small as possible to minimize network traffic (as 440 workstations would be downloading the end-product simultaneously, so it'd beat ten bells of proverbial out of the core and edge switches for a little while). I discovered two options. One being to integrate everything in side a cloop image directly inside the INITRD. I have stacks of working INITRDs with their matched kernels yet being my first dabble in to extracting the INITRD, my faffing with CPIO has resulted in me nuking my base layout (Thank god for snapshotting in VMware Workstation!) 4 times, and either getting "Premature end of file" or a copius amount of lines stating "cpio: Malformed Number: <strange characters>" finally ending with "Premature end of file". As a result I went in search of another option, which would be booting off an NFS share. I followed the guide:
http://wiki.archlinux.org/index.php/Dis … t_NFS_root
...in order to set up a network booted install of Arch and hit a few snags along the way, probably a result of using multiple operating systems for the TFTP and NFS server as opposed to using what the guide recommends, but I'm not sure as these seem solvable, although I don't know how right now.
The set up:
DHCP is provided by a Microsoft Windows Server 2003 VM (AD Integrated) on 172.16.10.17 on a box called "Rex".
TFTP is provided by another Windows Server 2003 VM by "TFTPd32" which is a free download. This is located on 172.16.10.158 on a box called "Terra".
The NFS store is provided by OpenFiler 2.3 which is a specialized version of rPath Linux designed specifically for turning boxes in to dedicated NAS stores. This is located on 172.16.10.6, and is called "frcnet-nas-1".
The problem:
DHCP is correctly configured with a Boot Host Name (Which is 172.16.10.158) and a boot file name of "pxelinux.0". This is confirmed as working.
Client gets the kernel and INITRD from TFTP and boots up fine until it hits "Waiting for devices to settle..." by which point it echos out "Root device /dev/nfs doesn't exist, attempting to create it...", which it seems to do so fine. It then passes control over to kinit and echos "INIT: version 2.86 booting" and the archlinux header, and immediately after that it prints:
mount: only root can do that
mount: only root can do that
mount: only root can do that
/bin/mknod: '/dev/null': File exists
/bin/mknod: '/dev/zero': File exists
/bin/mknod: '/dev/console': File exists
/bin/mkdir: cannot create directory '/dev/pts': File exists
/bin/mkdir: cannot create directory '/dev/shm': File exists
/bin/grep: /proc/cmdline: No such file or directory
/etc/rc.sysinit: line 72: /proc/sys/kernel/hotplug: No such file or directory
:: Using static /dev filesystem [DONE]
:: Mounting Root Read-only [FAIL]
:: Checking Filesystems [BUSY]
/bin/grep: /proc/cmdline: No such file or directory
:: Mounting Local Filesystems
mount: only root can do that
mount: only root can do that
mount: only root can do that
[DONE]
:: Activating Swap [DONE]
:: Configuring System Clock [DONE]
:: Removing Leftover Files [DONE]
:: Setting Hostname: myhost [DONE]
:: Updating Module Dependencies [DONE]
:: Setting Locale: en_US.utf8 [DONE]
:: Setting Consoles to UTF-8 mode[BUSY]
/etc/rc.sysinit: line 362: /dev/vc/0: No such file or directory
/etc/rc.sysinit: line 363: /dev/vc/0: No such file or directory
/etc/rc.sysinit: line 362: /dev/vc/1: No such file or directory
/etc/rc.sysinit: line 363: /dev/vc/1: No such file or directory
... all the way down to vc/63 ...
:: Loading Keyboard Map: us [DONE]
INIT: Entering runlevel: 3
:: Starting Syslog-NG [DONE]
Error opening file for reading; filename='/proc/kmsg', error='No such file or directory (2)'
Error initializing source driver; source='src'
:: Starting Network...
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
eth0: dhcpcd 4.0.3 starting
eth0: broadcasting inform for 172.16.10.154
eth0: received approval for 172.16.10.154
eth0: write_lease: Permission denied
:: Mounting Network Filesystems
mount: only root can do that
[FAIL]
:: Starting Cron Daemon [DONE]
...and, nothing after that, it just stops. Kernel doesn't panic, and hitting ctrl+alt+delete does what you'd expect, a clean shutdown minus a few errors about filesystems not being mounted. It seems /proc isn't getting mounted because init apparently doesn't have the appropriate permissions, and /proc not being mounted causes a whole string of other issues. Thing is, proc gets created at boot time as it contains kernel specific information about the system and the kernel's capabilities, right? Why can't it create it? How come init doesn't have the same privileges as root as it usually would, and how would I go about fixing it?
I admit, while I'm fairly competent in Linux, this one has me stumped. Anyone have any ideas?
Last edited by PinkFloydYoshi (2008-11-22 12:29:01)The idea behind the Windows DHCP and TFTP is that we'd be using an existing server and a NetApp box with NFS license to serve everything off. I would have loved to make a new server which is completely Linux, but my boss, nor the other technician have ever used Linux so if I left for any reason, they'd be stuck if ever they ran in to trouble, which is why I've struggled to get Linux to penetrate our all Windows infrastructure.
During my hunting around on Google I found a lot of information on making my own initrd, and a lot of it using all manner of switches. I can make them fine, but I figure that I would need to look at extracting the current working one first, adding X, Firefox and the ICA client to it, then compressing it again. Cloop came about when I was looking at DSL's internals. The smaller the initrd, the better, so utilizing this could possibly be a plus too.
The reason I'm doing this with Archlinux is that I know Arch's internals quite well (and pacman is just wonderous, which is more than I can say for yum), so if I run in to a small problem I'm more likely to fix it without consulting Google. Fair enough though, the NFS booting method is giving me issues I never thought were possible. Ahh, sods law strikes again.
Addendum: I've noticed something which struck me as odd. Files in the NFS share are somehow owned by 96:scanner instead of root:root. Upon attempting changing, it's telling me "Operation Not Permitted". Further prodding has led me to believe it's an Openfiler thing where GID/UID 96 on the OpenFiler box is "ofgroup"/"ofguest". Chowning / to root:root puts NFS boot right ahead and gives me a prompt, however I cannot log in as root. I've also discovered that chrooting in to the base from my Arch workstation and creating a directory makes the directory owned by ofgroup:ofguest again, so it's an Openfiler thing after all this time. Prodding further.
Addendum two: For anyone using Openfiler out there, when you allow guest access to the NFS share, be sure to set the Anonymous GID and Anonymous UID to 0. By default it's 96 and as a result when trying to boot you get the errors I experienced. This is insecure and you should use some sort of network/host/ip range restriction. Because the root filesystem has 96:96 as the owner of everything after you install the base layout using pacman (and any changes you make afterward) init and root no longer have the appropriate permissions, user 96:96 (which is "scanner" in Archlinux) has the permissions instead and init, in order to complete boot would need to be "scanner" in order to boot completely.
Solution is to set Anon GID and Anon UID to 0, chown the entire diskless root filesystem to root, then use a linux desktop to mount the diskless root filesystem, mount /proc, /sys and mount bind /dev, then chroot in to the diskless root filesystem. At this point to clear up any problems with bad passwords, use passwd to change your password. Exit the chroot environment then unmount the diskless proc, sys and dev. Boot up via the network and use your chosen password to log in as root. At this point, start clearing up permissions from the en masse filesystem chown and you should then have a usable diskless root.
I'll experiment further and clear up some of the remaining permission errors that occured during boot and report on my progress in fixing it. Didn't like the idea of chowning the entire share as root. :S
Last edited by PinkFloydYoshi (2008-11-21 19:28:15) -
Time Machine external hard drive not recognized
I connected an Iomega Ultramax 500GB Hard Drive to my imac to set up time machine. It has worked well for years but now has disappeared and time machine no longer backs up to the hard drive. The drive is recognized in the system profiler and I have tried Repair Disk with the Disk Utility but get the message:
Invalid record count
Volume check failed
Error: Filesystem verify or repair failed.
Can someone give me some guidance? Thanks!If you don't have backups, and the drive doesn't work, you may have lost all the data. There are ways to try to recover data from a failed drive, but I have no experience with that and can't help. If the data is valuable to you, your best chance is to send the drive to a data-recovery service such as DriveSavers, but that will be very expensive.
-
Open-vm-tools/official vmware tools not installing.
I'm trying to install the latest offical vmware tools (16/9/2013) and open-vm-tools but both seem to always fail. I tried some of the patches listed on the wiki, but nothing got me anywhere. The big thing I'm trying to accomplish is to be able to use vmhgfs but, I'd like to have all the tools if possible. Here is what I did.
Open Vm Tools
#[root@localhost] - [14-01-01 18:09:33] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools open-vm-tools-dkms
resolving dependencies...
looking for inter-conflicts...
Packages (2): open-vm-tools-5:2013.09.16-5 open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 8.21 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [#####################################################################################################################] 100%
(2/2) checking package integrity [#####################################################################################################################] 100%
(2/2) loading package files [#####################################################################################################################] 100%
(2/2) checking for file conflicts [#####################################################################################################################] 100%
(2/2) checking available disk space [#####################################################################################################################] 100%
(1/2) installing open-vm-tools [#####################################################################################################################] 100%
>>>
>>> You can mount VMware Shared Folders via:
>>> mount -t vmhgfs .host:/ /mnt/hgfs
>>>
>>> or by adding this line to /etc/fstab:
>>> .host:/ /mnt/hgfs vmhgfs defaults 0 0
>>>
Optional dependencies for open-vm-tools
gtkmm [installed]
libnotify [installed]
libxtst [installed]
fuse [installed]
libsm [installed]
open-vm-tools-modules: for linux kernel
open-vm-tools-dkms: for linux-lts and other kernels [pending]
netctl: suspend-resume network state [installed]
networkmanager: suspend-resume network state
(2/2) installing open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
>>> Enabling vmxnet driver in /usr/lib/modprobe.d/open-vm-tools-modules.conf
>>> (this will disable pcnet32 driver)
>>>
>>> If vmxnet driver doesn't handle your NIC, you have to manually
>>> disable loading of pcnet32 driver
>>>
#[root@localhost] - [14-01-01 18:09:47] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools-modules
warning: open-vm-tools-dkms-5:2013.09.16-5 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 5.57 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#####################################################################################################################] 100%
(1/1) checking package integrity [#####################################################################################################################] 100%
(1/1) loading package files [#####################################################################################################################] 100%
(1/1) checking for file conflicts [#####################################################################################################################] 100%
(1/1) checking available disk space [#####################################################################################################################] 100%
(1/1) reinstalling open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
#[root@localhost] - [14-01-01 18:10:14] - [/home/toxicarrow/Documents/firewall] - [R:0]
dkms install -m open-vm-tools -v 2013.04.16 -k $(uname -r)
Error! Could not find module source directory.
Directory: /usr/src/open-vm-tools-2013.04.16 does not exist.
#[root@localhost] - [14-01-01 18:13:14] - [/home/toxicarrow/Documents/firewall] - [R:2]
dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.12.6-1-ARCH VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmblock; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmci; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmhgfs; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmsync; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmxnet; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vsock........
Error! Build of vmblock.ko failed for: 3.12.6-1-ARCH (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
#[root@localhost] - [14-01-01 18:13:45] - [/home/toxicarrow/Documents/firewall] - [R:7]
Official Tools
Before patches
#[root@localhost] - [14-01-02 2:40:49] - [/home/toxicarrow/vmware/vmware-tools-distrib] - [R:32]
./vmware-install.pl
A previous installation of VMware Tools has been detected.
The previous installation was made by the tar installer (version 4).
Keeping the tar4 installer database format.
You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version. Do you wish to continue?
(yes/no) [yes]
Uninstalling the tar installation of VMware Tools.
Stopping services for VMware Tools
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
The removal of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc/init.d]
What is the directory that contains the init scripts?
[/etc/init.d]
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/bin/gcc".
The path "/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.12.6-1-ARCH/build/include".
The path "/lib/modules/3.12.6-1-ARCH/build/include" appears to be a valid path
to the 3.12.6-1-ARCH kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/driverLog.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-lyoMIO/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/util.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
make: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
make: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/message.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/request.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/link.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/module.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/file.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/super.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/page.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
VMware User Agent: done
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
After patches
#[root@localhost] - [14-01-02 2:44:39] - [/home/toxicarrow/vmware] - [R:0]
git clone https://github.com/rasa/vmware-tools-patches.git
Cloning into 'vmware-tools-patches'...
remote: Reusing existing pack: 134, done.
remote: Total 134 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (134/134), 22.06 KiB | 0 bytes/s, done.
Resolving deltas: 100% (74/74), done.
Checking connectivity... done.
#[root@localhost] - [14-01-02 2:44:55] - [/home/toxicarrow/vmware] - [R:0]
ls
= VMwareTools-9.6.1-1378637.tar.gz manifest.txt* run_upgrader.sh vmware-tools-distrib/ vmware-tools-patches/ vmware-tools-upgrader-32* vmware-tools-upgrader-64*
#[root@localhost] - [14-01-02 2:44:57] - [/home/toxicarrow/vmware] - [R:0]
cp VMwareTools-9.6.1-1378637.tar.gz vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:13] - [/home/toxicarrow/vmware] - [R:0]
cd vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:17] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
ls
LICENSE VMwareTools-9.6.1-1378637.tar.gz patch-module.sh* patches/ untar-and-patch-and-compile.sh*
README.md download-patches.sh* patch-modules.sh* untar-all-and-patch.sh* untar-and-patch.sh*
#[root@localhost] - [14-01-02 2:45:18] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
./untar-and-patch-and-compile.sh
=== Patching ./VMwareTools-9.6.1-1378637.tar.gz ...
--- Applying vmci/vmware9.k3.8rc4.patch ...
patching file linux/driver.c
Hunk #1 FAILED at 124.
Hunk #2 FAILED at 1750.
Hunk #3 FAILED at 1978.
3 out of 3 hunks FAILED -- saving rejects to file linux/driver.c.rej
--- Applying vmhgfs/vmhgfs-uid-gid-kernel-3.12-tools-9.6.1.patch ...
patching file file.c
patching file filesystem.c
patching file fsutil.c
patching file inode.c
Hunk #1 succeeded at 514 (offset -3 lines).
Hunk #2 succeeded at 617 (offset -3 lines).
Hunk #3 succeeded at 1216 (offset -3 lines).
patching file shared/compat_cred.h
--- Applying vmhgfs/vmhgfs-d_count-kernel-3.11-tools-9.6.0.patch ...
patching file inode.c
Hunk #1 succeeded at 31 with fuzz 1.
Hunk #2 FAILED at 1893.
Hunk #3 FAILED at 1946.
2 out of 3 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmhgfs/vmware9.compat_mm.patch ...
patching file shared/compat_mm.h
Hunk #1 FAILED at 91.
Hunk #2 FAILED at 100.
2 out of 2 hunks FAILED -- saving rejects to file shared/compat_mm.h.rej
--- Applying vmhgfs/patch_inode.c.patch ...
patching file inode.c
Hunk #1 FAILED at 1798.
Hunk #2 FAILED at 1818.
2 out of 2 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmblock/vmblock.3.11.patch ...
patching file linux/file.c
--- Applying vmblock/vmblock.3.10.patch ...
patching file linux/control.c
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc/init.d]
What is the directory that contains the init scripts?
[/etc/init.d]
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
make: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/driverLog.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-HrsGw6/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/util.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
make: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/driverLog.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
make: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/message.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/request.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/link.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/module.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/file.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/super.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/page.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
#[root@localhost] - [14-01-02 2:46:53] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
Any idea what I should be doing?I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
Did you make any progress ??
Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
Makefile:120: recipe for target 'vmblock.ko' failed
Last edited by crankshaft (2014-01-10 11:32:32)
Maybe you are looking for
-
Single Sign On -- Enterprise portal and BI JAVA
Hi, I need to watch reports BI J2ee from an EP 7.00. I have configured the single sign On but it works just for ABAP BI Stack. This is what I have done for SSO JAVA: Importing the BI JAVA Certificate to the SAP NetWeaver 2004s Portal (SAP EP 7.0)
-
ADF Server Domain Requirement on Oracle WLS 11g
Hi All.... I am new to ADF I would like to know if it is necessary to create an ADF server domain, or perform ADF specific configuration on WLS in order to deploy and run ADF web Apps on Oracle Weblogic Server 11g? Or can ADF web apps be deployed dir
-
I'm stuck in a loop. iMovie says it is looking for a certain movie file; says it can't be found and will not play properly and then begins to search again. I can't seem to bypass this and just open iMovie so I can work on something else. I don't n
-
Upgrade from trial xi pro to full - asks what "i currently own " but trial not in list?
have the trial xi pro adobe but want to upgrade now, how do i do this and what do i currently own in the drop down list?
-
Photoshop crashes when batching images
Received an Event 1000 application error with the following event logs Exception code: 0xc0000005 Fault offset: 0x0000000000441382 Faulting process id: 0x1500 Faulting application start time: 0x01d0839d172b4dba Faulting application path: C:\Program F