GNU RAID 1 "Data Volume Failed To Mount"

I'm using a Western Digital My Book Live DUO network drive with 2x2Tb HD's in RAID 1 configuration. The devices uses Linux GNU to manage the RAID array.
At some point after a reboot the UI returns this error:

"Data volume failed to mount Contact tech support"

I have very little linux knowledge, and trying to get the RAID error fixed so I can access and backup my data on another drive.

Here's the info I have managed to pull so far from the drive via SSH:


dmesg

Code:
login as: root
root@192.168.1.55's password:
Linux LTFileServer 2.6.32.11-svn70860 #1 Thu May 17 13:32:51 PDT 2012 ppc
Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.

LTFileServer:~# dmesg
4bffd1800.sata: DMA CFG = 0x00000001
dma_register_interrupt register irq (25)
irq: irq 27 on host /interrupt-controller0 mapped to virtual irq 27
ata4294967295: sata_dwc_port_start: setting burst size in DBTSR: 0x00100010
sata-dwc 4bffd1800.sata: **** GEN II speed rate negotiated
scsi1 : sata-dwc
ata2: SATA max UDMA/133 irq 27
Found: SST 39LF040
4fff80000.nor_flash: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Creating 2 MTD partitions on "4fff80000.nor_flash":
0x000000000000-0x000000020000 : "3genv"
0x000000020000-0x000000080000 : "u-boot"
ndfc 4fff80000.ndfc: failed to get memory
ndfc: probe of 4fff80000.ndfc failed with error -5
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
PPC 4xx OCP EMAC driver, version 3.54
mal0: descriptor-memory = ocm
irq: irq 6 on host /interrupt-controller2 mapped to virtual irq 24
irq: irq 7 on host /interrupt-controller2 mapped to virtual irq 29
irq: irq 3 on host /interrupt-controller2 mapped to virtual irq 31
irq: irq 4 on host /interrupt-controller2 mapped to virtual irq 32
irq: irq 5 on host /interrupt-controller2 mapped to virtual irq 33
irq: irq 8 on host /interrupt-controller2 mapped to virtual irq 34
irq: irq 12 on host /interrupt-controller2 mapped to virtual irq 35
MAL: Enabled Interrupt Coal TxCnt: 1 RxCnt: 8
                            TxTimer: 0 RxTimer: 10000
MAL v2 /plb/mcmal, 1 TX channels, 1 RX channels
RGMII /plb/opb/emac-rgmii@ef601500 initialized with MDIO support
TAH /plb/opb/emac-tah@ef601350 initialized
irq: irq 16 on host /interrupt-controller2 mapped to virtual irq 36
irq: irq 20 on host /interrupt-controller2 mapped to virtual irq 37
/plb/opb/emac-rgmii@ef601500: input 0 in RGMII mode
bcm54610_init: before 0x2c8c, after 0x2c8c
bcm54610_init: before 0x0d41, 0x0200; after 0x0d41, 0x0200
eth0: EMAC-0 /plb/opb/ethernet@ef600c00, MAC 00:90:a9:b7:10:66
eth0: found BCM54610 Gigabit Ethernet PHY (0x01)
Intel(R) Gigabit Ethernet Network Driver - version 1.3.16-k2
Copyright (c) 2007-2009 Intel Corporation.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Fusion MPT base driver 3.04.12
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.12
input: rst_button as /devices/virtual/input/input0
i2c /dev entries driver
irq: irq 2 on host /interrupt-controller0 mapped to virtual irq 38
ibm-iic 4ef600700.i2c: using standard (100 kHz) mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
Registered led device: a3g_led
irq: irq 20 on host /interrupt-controller0 mapped to virtual irq 39
AMCC 4xx PKA v0.1 @0x04_00114000 size 16384 IRQ 39
Initializing PKA...
PKA Driver Successfully Initialized
Reading pvr value = 12c41c82
irq: irq 29 on host /interrupt-controller0 mapped to virtual irq 40
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
Interrupt status = 0x00042020
dev status = 0x03087722
Interrupt status = 0x00042020
dev status = 0x03087722
apm82181-adma: Probing AMCC APM82181 ADMA engines...
ata2.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 1/32)
irq: irq 13 on host /interrupt-controller0 mapped to virtual irq 41
AMCC(R) APM82181 ADMA Engine found [1]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F0300)
apm82181 adma1: allocated 512 descriptor slots
irq: irq 14 on host /interrupt-controller0 mapped to virtual irq 42
AMCC(R) APM82181 ADMA Engine found [2]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
ata1.00: ATA-8: WDC WD20EARX-00PASB0, 27.0CR.7, max UDMA/133
ata1.00: 3907209168 sectors, multi 0: LBA48
ata2.00: configured for UDMA/133
apm82181 adma2: allocated 512 descriptor slots
irq: irq 15 on host /interrupt-controller0 mapped to virtual irq 43
AMCC(R) APM82181 ADMA Engine found [3]: ( capabilities: memcpy )
--------------- dma_async_device_register: 683-------------------------
apm82181 adma3: allocated 512 descriptor slots
oprofile: using timer interrupt.
Macsec proc interface Initiliazed
Registered Macsec Interface
IPv4 over IPv4 tunneling driver
ata1.00: configured for UDMA/133
blk_queue_max_hw_segments: set to minimum 1
scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 27.0 PQ: 0 ANSI: 5
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
sd 0:0:0:0: [sda] 3907209168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: Attached scsi generic sg0 type 0
blk_queue_max_hw_segments: set to minimum 1
scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
NET: Registered protocol family 17
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] 4096-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg1 type 0
 sda:
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
 sdb: sdb1 sdb2 sdb3 sdb4
 sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] Attached SCSI disk
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: invalid raid superblock magic on sdb3
md: sdb3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sdb4
md: sdb4 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda3
md: sda3 does not have a valid v0.90 superblock, not importing!
md: invalid raid superblock magic on sda4
md: sda4 does not have a valid v0.90 superblock, not importing!
md: Scanned 8 and added 4 devices.
md: autorun ...
md: considering sda2 ...
md:  adding sda2 ...
md:  adding sda1 ...
md:  adding sdb2 ...
md:  adding sdb1 ...
md: created md0
md: bind<sdb1>
md: bind<sdb2>
md: bind<sda1>
md: bind<sda2>
md: running: <sda2><sda1><sdb2><sdb1>
md0: WARNING: sda2 appears to be on the same physical disk as sda1.
md0: WARNING: sdb2 appears to be on the same physical disk as sdb1.
True protection against single-disk failure might be compromised.
raid1: raid set md0 active with 4 out of 4 mirrors
md0: detected capacity change from 0 to 2047803392
md: ... autorun DONE.
 md0: unknown partition table
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 9:0.
Freeing unused kernel memory: 448k init
Disable EMAC EMI Fix
eth0: link is up, 1000 FDX, pause enabled
eth0: no IPv6 routers present
md: md2 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 512741376
md: md3 stopped.
md: bind<sdb4>
md: bind<sda4>
raid1: raid set md3 active with 1 out of 2 mirrors
md3: detected capacity change from 0 to 1995774484480
md: recovery of RAID array md3
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 2048k window, over a total of 1948998520 blocks.
md: resuming recovery of md3 from checkpoint.
 md3: unknown partition table
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev md3.
 md2: unknown partition table
Adding 500544k swap on /dev/md2.  Priority:-1 extents:1 across:500544k
ufsd: bad vermagic: kernel tainted.
Disabling lock debugging due to kernel taint
ufsd: module license 'unspecified' taints kernel.
ufsd: driver 8.5 (NTFS4LINUX_U85_014_S[2011-09-15-11:41:06]) LBD=ON with delayalloc with ioctl loaded at d4490000
NTFS read/write support included
Big endian platform
Hfs+/HfsX read/write support included
Built_for__WD_APM_82181_2011-08-09_sec

svc: failed to register lockdv1 RPC service (errno 97).
md: cannot remove active disk sda1 from md0 ...
md: cannot remove active disk sda2 from md0 ...
md: cannot remove active disk sdb1 from md0 ...
md: cannot remove active disk sdb2 from md0 ...
Calling led_set_blink with value x
usbco  registered new interface driver usbfs
usbco  registered new interface driver hub
usbco  registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
dwc_otg: version 2.60a 22-NOV-2006
dwc_otg: Shared Tx FIFO mode
dwc_otg: Using DMA mode
dwc_otg dwc_otg.0: DWC OTG Controller
dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1
dwc_otg dwc_otg.0: irq 28, io mem 0x00000000
dwc_otg: Init: Port Power? op_state=1
dwc_otg: Init: Power Port (0)
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DWC OTG Controller
usb usb1: Manufacturer: Linux 2.6.32.11-svn70860 dwc_otg_hcd
usb usb1: SerialNumber: dwc_otg.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
md: md3: recovery done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda4
 disk 1, wo:0, o:1, dev:sdb4
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
usb 1-1: new high speed USB device using dwc_otg and address 2
usb 1-1: New USB device found, idVendor=0781, idProduct=5581
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: Ultra
usb 1-1: Manufacturer: SanDisk
usb 1-1: SerialNumber: 4C530123091014123423
usb 1-1: configuration #1 chosen from 1 choice
usbco  registered new interface driver libusual
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbco  registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:0:0: [sdc] 62566488 512-byte logical blocks: (32.0 GB/29.8 GiB)
usb-storage: device scan complete
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
md: cannot remove active disk sda1 from md0 ...
md: cannot remove active disk sda2 from md0 ...
md: cannot remove active disk sdb1 from md0 ...
md: cannot remove active disk sdb2 from md0 ...
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
Calling led_set_blink with value x
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
LTFileServer:~#
LTFileServer:~#

mount

Code:
LTFileServer:~# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime,barrier=1)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=5M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=5M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
tmpfs on /tmp type tmpfs (rw,size=100M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/DataVolume/cache on /CacheVolume type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/sdc1 on /var/media/Ultra type vfat (rw,utf8,errors=continue,fmask=013,dmask=002,uid=99,gid=1000)
LTFileServer:~#
LTFileServer:~#

parted -l

Code:
LTFileServer:~# parted -l
Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system     Name     Flags
 3      15.7MB  528MB   513MB   linux-swap(v1)  primary  raid
 1      528MB   2576MB  2048MB  ext3            primary  raid
 2      2576MB  4624MB  2048MB  ext3            primary  raid
 4      4624MB  2000GB  1996GB                  primary  raid


Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system     Name     Flags
 3      15.7MB  528MB   513MB   linux-swap(v1)  primary  raid
 1      528MB   2576MB  2048MB  ext3            primary  raid
 2      2576MB  4624MB  2048MB  ext3            primary  raid
 4      4624MB  2000GB  1996GB                  primary  raid


Model: SanDisk Ultra (scsi)
Disk /dev/sdc: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      11.2MB  32.0GB  32.0GB  primary  fat32        lba


Model: Unknown (unknown)
Disk /dev/md0: 2048MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2048MB  2048MB  ext3


Model: Unknown (unknown)
Disk /dev/md2: 513MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system     Flags
 1      0.00B  513MB  513MB  linux-swap(v1)


Error: /dev/md3: unrecognised disk label

LTFileServer:~#
LTFileServer:~#
LTFileServer:~#

From what I have managed to put together by reading left and right the RAID 1 is md0 made from sda and sdb (Hard drives)
And the problem seems to be something on the superblock being corrupted. but if I try to use fsck command to attempt to fix it it...

Code:
LTFileServer:~# fsck /dev/md0
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/md0 is mounted.

WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Do you really want to continue (y/n)? no

check aborted.
LTFileServer:~#

All help and advise is really welcome.


Similar Content



Which Disk Is Ata1.00?

Hi! I have a failing disk and the kernel messages are the following:
Code:
Απρ 01 15:07:02 Arch kernel: ata1: lost interrupt (Status 0x50)
Απρ 01 15:07:03 Arch kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Απρ 01 15:07:03 Arch kernel: ata1.00: failed command: WRITE DMA
Απρ 01 15:07:03 Arch kernel: ata1.00: cmd ca/00:08:20:32:6a/00:00:00:00:00/e4 tag 0 dma 4096 out
                                         res 40/00:00:4b:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Απρ 01 15:07:03 Arch kernel: ata1.00: status: { DRDY }
Απρ 01 15:07:03 Arch kernel: ata1: soft resetting link
Απρ 01 15:07:03 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:07:03 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:07:03 Arch kernel: ata1.00: configured for UDMA/133
Απρ 01 15:07:03 Arch kernel: ata1.01: configured for UDMA/133
Απρ 01 15:07:03 Arch kernel: ata1: EH complete
Απρ 01 15:09:19 Arch kernel: ata1: lost interrupt (Status 0x50)
Απρ 01 15:09:20 Arch kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Απρ 01 15:09:20 Arch kernel: ata1.00: failed command: READ DMA EXT
Απρ 01 15:09:20 Arch kernel: ata1.00: cmd 25/00:20:e8:b2:fd/00:00:18:00:00/e0 tag 0 dma 16384 in
                                         res 40/00:00:4b:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Απρ 01 15:09:20 Arch kernel: ata1.00: status: { DRDY }
Απρ 01 15:09:20 Arch kernel: ata1: soft resetting link
Απρ 01 15:09:20 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:09:20 Arch kernel: ata1.00: LPM support broken, forcing max_power
Απρ 01 15:09:20 Arch kernel: ata1.00: configured for UDMA/133
Απρ 01 15:09:20 Arch kernel: ata1.01: configured for UDMA/133
Απρ 01 15:09:20 Arch kernel: ata1: EH complete

I have 2 disks: sda, sdb. Which disk is it referring to?

Thanks a lot

Xubuntu MBR Partioning Question

I was wondering if I can repair my current partitioning setup using gparted, or if I should just reload Xubuntu. Basically I screwed up by making the primary partition only 256M, and made a massive extended logical partition for everything else, and did not leave swap space. I am doing this on an older PC with MBR, dual processor, 2G RAM each processor, 160GB hard drive space. It is single boot, no Windows. I would like the partioning to be as follows, leaving empty disk space for other Linux flavors:

/ 13GB ext4
/home 50GB ext4
swap 8GB swap

sudo parted /dev/sda print all
Code:
Model: ATA ST3160812AS (scsi)
Disk /dev/sda: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type      File system  Flags
 1      1049kB  256MB  255MB  primary   ext2         boot
 2      257MB   160GB  160GB  extended
 5      257MB   160GB  160GB  logical
                                                                       
Error: /dev/mapper/xubuntu--vg-swap_1: unrecognised disk label

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/xubuntu--vg-root: 158GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  158GB  158GB  ext4
                                                                          
Error: /dev/mapper/sda5_crypt: unrecognised disk label

df -hT
Code:
Filesystem                   Type      Size  Used Avail Use Mounted on
/dev/mapper/xubuntu--vg-root ext4      145G  6.5G  131G   5% /
none                         tmpfs     4.0K     0  4.0K   0% /sys/fs/cgroup
udev                         devtmpfs  989M  4.0K  989M   1% /dev
tmpfs                        tmpfs     201M  1.1M  200M   1% /run
none                         tmpfs     5.0M     0  5.0M   0% /run/lock
none                         tmpfs    1003M   88K 1003M   1% /run/shm
none                         tmpfs     100M   24K  100M   1% /run/user
/dev/sda1                    ext2      236M  120M  104M  54% /boot
/home/mbrk/.Private          ecryptfs  145G  6.5G  131G   5% /home/mbrk

Get RAID1 And LVM Back After Re Installating The OS

Hi All,
I had installed Cent OS 6.6 on sda. The RAID1 and LVM setup was on sdb and sdc. To practice well on recovering RAID and LVM after the OS reinstallation, I just reinstalled the OS. During first re installation of OS, I had selected all the mount points including RAID/LVM partitions as same as how those where mounted before the reinstallation, but the format was selected to only /, /others, /var. And after booting /dev/md0 and LVM partitions were set to active automatically and everything was mounted properly. Also there was no any data loss in the RAID/LVM partitions. So I could made sure that everything will be perfect if we carefully select the mount points during OS reinstallation by making sure the formating partitions.

Now I thouht of reinstalling OS once again but this time didn't select mount points for RAID/LVM partitions during OS reinstallation, thought for manual setup after the installation. So just selected /, /others, /var partitions to format. When it booted, I ran "cat /proc/mdstat" but it was taken /dev/md127(read only) instead of /dev/md0.
Code:
# cat /proc/mdstat 
Personalities : [raid1] 
md127 : active (auto-read-only) raid1 sdc[1] sdb[0]
      52396032 blocks super 1.2 [2/2] [UU]
      
unused devices: <none>

So now I just wanted to stop and restart this RAID array as /dev/md0. But I am not able to stop as it is giving following error.
Code:
# mdadm --stop --force /dev/md127
mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group?

I made sure that no one RAID/LVM partitions are mounted.
Code:
# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        15G  3.5G   11G  26% /
tmpfs           376M     0  376M   0% /dev/shm
/dev/sda2       4.7G  9.8M  4.5G   1% /others
/dev/sda3       2.9G  133M  2.6G   5% /var

But LVM is active
Code:
# pvdisplay 
  --- Physical volume ---
  PV Name               /dev/md127
  VG Name               data
  PV Size               49.97 GiB / not usable 4.00 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              12791
  Free PE               5111
  Allocated PE          7680
  PV UUID               IJ2br8-SWHW-cf1d-89Fr-EEw9-IJME-1BpfSj
   
# vgdisplay 
  --- Volume group ---
  VG Name               data
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  19
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               49.96 GiB
  PE Size               4.00 MiB
  Total PE              12791
  Alloc PE / Size       7680 / 30.00 GiB
  Free  PE / Size       5111 / 19.96 GiB
  VG UUID               982ay8-ljWY-kiPB-JY7F-pIu2-87uN-iplPEQ
   
# lvdisplay 
  --- Logical volume ---
  LV Path                /dev/data/home
  LV Name                home
  VG Name                data
  LV UUID                OAQp25-Q1TH-rekd-b3n2-mOkC-Zgyt-3fX2If
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                10.00 GiB
  Current LE             2560
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
   
  --- Logical volume ---
  LV Path                /dev/data/backup
  LV Name                backup
  VG Name                data
  LV UUID                Uq6rhX-AvPN-GaNe-zevB-k3iB-Uz0m-TssjCg
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

As LVM is active on /dev/md127 it is not allowing to stop /dev/md127 raid array. So as I am fresher in RAID/LVM, expecting your kind help to make LVM inactive without any data loss and restart the RAID array as /dev/md0 and then re activate the LVM setup.
Expecting your kind reply, Thanks.

LVM Mount Via USB

My father passed away about 6 months ago and I'm just getting around to going threw all 18 hard drives... I have been using Ubuntu 14.04 for over a year now and while I'm not a pro I can handle most things.

One drive has LVM on it. I have attached it via a USB2.0 to SATA cable. I followed the instructions he http://linuxers.org/howto/how-mount-...rtitions-linux

Code:
michael [ ~ ]$ sudo fdisk -l
[sudo] password for michael: 

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x38431b10

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048  1464322047   732160000    7  HPFS/NTFS/exFAT
/dev/sda2      1464322048  2930272255   732975104    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000656a3

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048    33560575    16779264   82  Linux swap / Solaris
/dev/sdb2   *    33560576    75505663    20972544   83  Linux
/dev/sdb3        75505664   500117503   212305920   83  Linux

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000da346

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      499711      248832   83  Linux
/dev/sdc2          501758  1465147391   732322817    5  Extended
/dev/sdc5          501760  1465147391   732322816   8e  Linux LVM
michael [ ~ ]$ sudo pvs
  PV         VG         Fmt  Attr PSize   PFree
  /dev/sdc5  ubuntu1-vg lvm2 a--  698.39g    0 
michael [ ~ ]$ sudo lvdisplay /dev/ubuntu1-vg
  --- Logical volume ---
  LV Path                /dev/ubuntu1-vg/root
  LV Name                root
  VG Name                ubuntu1-vg
  LV UUID                StErnb-Mtop-NaEy-faw4-wNk0-bY5I-6ARBmI
  LV Write Access        read/write
  LV Creation host, time ubuntu1, 2014-08-12 18:45:21 +0900
  LV Status              NOT available
  LV Size                694.39 GiB
  Current LE             177765
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
   
  --- Logical volume ---
  LV Path                /dev/ubuntu1-vg/swap_1
  LV Name                swap_1
  VG Name                ubuntu1-vg
  LV UUID                62DxMC-qLAo-6cU9-kA5H-kNoL-7B4t-1ZCQcK
  LV Write Access        read/write
  LV Creation host, time ubuntu1, 2014-08-12 18:45:21 +0900
  LV Status              NOT available
  LV Size                4.00 GiB
  Current LE             1024
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
   
michael [ ~ ]$ mount /dev/ubuntu1-vg/root /mnt
mount: only root can do that
michael [ ~ ]$ sudo mount /dev/ubuntu1-vg/root /mnt
mount: special device /dev/ubuntu1-vg/root does not exist

So where did I go wrong?

Extended Partition Error On Boot

Did you find any way to get out with this error ? I've got the same with an extended partition...
Code:
# fdisk /dev/sda

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/sda: 55,9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00015c35

Device     Boot    Start       End  Sectors  Size Id Type
/dev/sda1  *        2048  19531775 19529728  9,3G 83 Linux
/dev/sda2       19533822 117229567 97695746 46,6G  5 Extended
/dev/sda5       19533824  23558143  4024320  1,9G 82 Linux swap / Solaris
/dev/sda6       23560192 117229567 93669376 44,7G 83 Linux

Code:
# dmesg|less
[   84.343741] EXT4-fs (sda2): unable to read superblock
[   84.348074] EXT4-fs (sda2): unable to read superblock
[   84.352391] EXT4-fs (sda2): unable to read superblock
[   84.357159] XFS (sda2): Invalid superblock magic number
[   84.373676] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   84.373891] FAT-fs (sda2): bogus logical sector size 65535
[   84.373897] FAT-fs (sda2): Can't find a valid FAT filesystem
[   84.378220] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   84.378444] FAT-fs (sda2): bogus logical sector size 65535
[   84.378449] FAT-fs (sda2): Can't find a valid FAT filesystem
[   84.386262] ntfs: (device sda2): is_boot_sector_ntfs(): Invalid boot sector checksum.
[   84.386270] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot sector is invalid.
[   84.386275] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[   84.386279] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume.
[   84.390737] MINIX-fs: unable to read superblock
[   84.395176] attempt to access beyond end of device
[   84.395185] sda2: rw=16, want=3, limit=2
[   84.395191] hfsplus: unable to find HFS+ superblock
[   84.404204] qnx4: no qnx4 filesystem (no root dir).
[   84.408959] You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[   84.417367] hfs: can't find a HFS filesystem on dev sda2

Trouble With Fdisk

I got this configuration.

fdisk -l

Disk /dev/sda: 493.9 GB, 493921239040 bytes
255 heads, 63 sectors/track, 60049 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002ac38

Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 32636 261630976 8e Linux LVM

Disk /dev/mapper/vg_gazduire-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_gazduire-lv_swap: 5100 MB, 5100273664 bytes
255 heads, 63 sectors/track, 620 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_gazduire-lv_home: 209.1 GB, 209119608832 bytes
255 heads, 63 sectors/track, 25424 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


df -h

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_gazduire-lv_root
50G 21G 27G 44% /
tmpfs 2.4G 0 2.4G 0% /dev/shm
/dev/sda1 485M 161M 299M 35% /boot
/dev/mapper/vg_gazduire-lv_home
192G 17G 166G 9% /home
/usr/tmpDSK 2.0G 981M 955M 51% /tmp


I want to increase the /dev/sda1 with aproximativ 200 gb who remains ! My plans a i want to make /dev/sda3 and i want to put in
vg_gazduire!

VG Name vg_gazduire
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 249.51 GiB
PE Size 4.00 MiB
Total PE 63874
Alloc PE / Size 63874 / 249.51 GiB
Free PE / Size 0 / 0



When i type fdisk /dev/sda3 the system give me Unable to open /dev/sda3!

Could anyone tell me the solution?

Trying To Dd A Server With LVM To Another Ext HD, Then To Another Server

I have Linux enterprise server 11 sp3 with 3 250 GB WD blue drives in a raid 5 configuration.

Server “A” (external drive not plugged in):
Code:
Disk /dev/sda: 499.0 GB, 499021512704 bytes
255 heads, 63 sectors/track, 60669 cylinders, total 974651392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00059fd2

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1028095      513024   83  Linux
/dev/sda2         1028096    21993471    10482688   82  Linux swap / Solaris
/dev/sda3        21993472   974651391   476328960   8e  Linux LVM

Disk /dev/mapper/VG_SYSTEM-ROOT: 487.8 GB, 487755612160 bytes
255 heads, 63 sectors/track, 59299 cylinders, total 952647680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/VG_SYSTEM-ROOT doesn't contain a valid partition table

I am trying to clone this machine to another server, both servers are Dell Poweredge 1900, with 3 – 250 WD drives (the only difference is the ‘B’ server has WD Cavier drives), pretty much identical machines, same processor and ram. I have a 2TB ext hard drive that I am using to store the output of DD. I have booted from the CD to a rescue system, then mounted my 2TB ext and did the following:
Code:
    # dd if=/dev/sda conv=sync,noerror bs=64k | gzip –c | split –a3 –b 2G –verbose - /mnt/exthd/

This gives me the following files on my external hard drive:
Code:
    
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:00 aaa
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:31 aab
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:53 aac
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:05 aad
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:10 aae
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:17 aaf
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:24 aag
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:31 aah
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:37 aai
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:43 aaj
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:50 aak
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:56 aal
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:02 aam
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:06 aan
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:12 aao
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:32 aap
-rwxr-xr-x 1 root root  324998512 Jan 10 23:35 aaq

Now, I boot to the rescue system on server ‘B’ with the external drive plugged in, and run fdisk:
Code:
Disk /dev/sda: 498.8 GB, 498753077248 bytes
255 heads, 63 sectors/track, 60636 cylinders, total 974127104 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00059fd2

   Device Boot      Start         End      Blocks   Id  System

Disk /dev/sdb: 2000.4 GB, 2000398933504 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00015a3d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  3907028991  1953513472    c  W95 FAT32 (LBA)

Notice sda is only 498.8GB where on server ’A’, it was 499.0. when I try to restore my files from the DD, I get an out of space error. To restore, I use the following:
Code:
    # cat /mnt/exthd/aa* | gunzip –c | dd of=/dev/sda
    
dd: writing to ‘/dev/sda’:  No space left on device
974127105+0 records in
974127104+0 records out
498753077248 bytes (499 GB) copied, 37067.3 s, 13.5MB/s

My guess, is that although the drives are the same capacity (3 – 250GB in RAID 5 array), the number of cylinders is different because it is a different model, and that is where it is running out of space, although I wouldn’t think it would.

Please correct me if I am wrong as I am a newbie, but if I do “# dd if=/dev/sda” that will take all the partitions with it? Such as sda1, sda2, sda3 correct?

Nfsd Not Starting At Boot

Hello,
I can't get nfsd start at boot on openwrt linux.

I followed this guide:
http://wiki.openwrt.org/doc/howto/nfs.server

but when I turn the computer on:

Code:
root@OpenWrt:~# showmount -e localhost
clnt_create: RPC: Program not registered

Code:
root@OpenWrt:~# dmesg | tail
[   22.252000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   24.228000] eth1: link UP - 100/full - flow control off
[   24.244000] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   30.124000] svc: failed to register nfsdv3 RPC service (errno 5).
[   31.588000] device eth1 entered promiscuous mode
[   31.596000] br-lan: port 1(eth1) entered forwarding state
[   31.600000] br-lan: port 1(eth1) entered forwarding state
[   31.652000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   31.684000] eth1: link UP - 100/full - flow control off
[   33.604000] br-lan: port 1(eth1) entered forwarding state

but if I do
Code:
root@OpenWrt:~# /etc/init.d/nfsd start
root@OpenWrt:~# showmount -e localhost
Export list for localhost:
/mnt/3tb *

so it works well, but I look at dmesg
Code:
root@OpenWrt:~# dmesg | tail
[   24.228000] eth1: link UP - 100/full - flow control off
[   24.244000] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   30.124000] svc: failed to register nfsdv3 RPC service (errno 5).
[   31.588000] device eth1 entered promiscuous mode
[   31.596000] br-lan: port 1(eth1) entered forwarding state
[   31.600000] br-lan: port 1(eth1) entered forwarding state
[   31.652000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   31.684000] eth1: link UP - 100/full - flow control off
[   33.604000] br-lan: port 1(eth1) entered forwarding state
[16642.280000] svc: failed to register lockdv1 RPC service (errno 124).

I tried several times
Code:
root@OpenWrt:~# /etc/init.d/portmap enable
root@OpenWrt:~# /etc/init.d/nfsd  enable

and reboot but, again, I have to start nfsd manually after every reboot.

What am I doing wrong? On Attitude Adjustment I never had any issue.

Please help!

PhpVirtualBox Cannot Connect To 127.0.0.1:18083

I am using phpVirtualBox, and everything is working perfectly. Then something changes, and I get the following error:
Code:
Could not connect to host (http://127.0.0.1:18083/)

I reboot the physical machine, or execute /etc/init.d/vboxweb-service restart, and then everything works for a while.

According to http://sourceforge.net/p/phpvirtualb...onnect-to-host, there are three reasons why this will happen.
Quote:
This indicates that phpVirtualBox could not connect to the vboxwebsrv server. Either the location setting in config.php is wrong, vboxwebsrv is not running on the VirtualBox host, or SELinux is blocking access to vboxwebsrv. If you have SELinux enabled
As shown below, it is not reason 2 or 3.

Code:
[root@devserver ~]# service vboxweb-service status
Checking for VBox Web Service ...running
[root@devserver ~]# service vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.
[root@devserver ~]# service vboxautostart-service status
Usage: /etc/init.d/vboxautostart-service {start|stop}
[root@devserver ~]# service  vboxballoonctrl-service status
Checking for VBox watchdog service ...not running
[root@devserver ~]# sestatus
SELinux status:                 enabled
SELinuxfs mount:                /selinux
Current mode:                   permissive
Mode from config file:          permissive
Policy version:                 24
Policy from config file:        targeted
[root@devserver ~]#

Thus it must be that the location setting in config.php is wrong. config.php has the following default settings, and I left them as is.

Code:
/* SOAP URL of vboxwebsrv (not phpVirtualBox's URL) */
var $location = 'http://127.0.0.1:18083/';
...
// Host / ip to use for console connections
#var $consoleHost = '192.168.1.40';

According to http://sourceforge.net/p/phpvirtualb...-configuration, "If VirtualBox and phpVirtualBox are on the same physical host, you may leave the $location setting alone". VirtualBox and phpVirtualBox are definitely on the same physical machine.

Please provide recommendations.

Resize LVM Partitions

UPDATED:
I installed a Deb 7 Srv w LVM w following partitions:
The end product should become a mail server (Citadel) and in time also a Web server.
Code:
 df -hT 
Filesystem                Type      Size  Used Avail Use% Mounted on
rootfs                    rootfs    322M  141M  165M  46% /
udev                      devtmpfs   10M     0   10M   0% /dev
tmpfs                     tmpfs     100M  260K  100M   1% /run
/dev/mapper/deb--srv-root ext4      322M  141M  165M  46% /
tmpfs                     tmpfs     5,0M     0  5,0M   0% /run/lock
tmpfs                     tmpfs     200M     0  200M   0% /run/shm
/dev/sda1                 ext2      228M   18M  199M   9% /boot
/dev/mapper/deb--srv-home ext4      233G  188M  221G   1% /home
/dev/mapper/deb--srv-tmp  ext4      368M   11M  339M   3% /tmp
/dev/mapper/deb--srv-usr  ext4      8,3G  481M  7,4G   6% /usr
/dev/mapper/deb--srv-var  ext4      2,8G  236M  2,4G   9% /var

 fdisk -l 
Disk /dev/sda: 268.4 GB, 268435456000 bytes
255 heads, 63 sectors/track, 32635 cylinders, total 524288000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00064033

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      499711      248832   83  Linux
/dev/sda2          501758   524285951   261892097    5  Extended
/dev/sda5          501760   524285951   261892096   8e  Linux LVM

Disk /dev/mapper/deb--srv-root: 348 MB, 348127232 bytes
255 heads, 63 sectors/track, 42 cylinders, total 679936 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/deb--srv-root doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-swap_1: 2143 MB, 2143289344 bytes
255 heads, 63 sectors/track, 260 cylinders, total 4186112 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/deb--srv-swap_1 doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-usr: 8996 MB, 8996782080 bytes
255 heads, 63 sectors/track, 1093 cylinders, total 17571840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/deb--srv-usr doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-var: 2998 MB, 2998927360 bytes
255 heads, 63 sectors/track, 364 cylinders, total 5857280 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/deb--srv-var doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-tmp: 398 MB, 398458880 bytes
255 heads, 63 sectors/track, 48 cylinders, total 778240 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/deb--srv-tmp doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-home: 253.3 GB, 253289824256 bytes
255 heads, 63 sectors/track, 30794 cylinders, total 494706688 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/deb--srv-home doesn't contain a valid partition table

 pvs 
PV         VG      Fmt  Attr PSize   PFree
/dev/sda5  deb-srv lvm2 a--  249,76g    0

 lvs 
LV     VG      Attr     LSize   Pool Origin Data%  Move Log Copy%  Convert
home   deb-srv -wi-ao-- 235,89g
root   deb-srv -wi-ao-- 332,00m
swap_1 deb-srv -wi-ao--   2,00g
tmp    deb-srv -wi-ao-- 380,00m
usr    deb-srv -wi-ao--   8,38g
var    deb-srv -wi-ao--   2,79g

Now i want to _shrink_ the HOME partition so I can expand my VAR partition. Looked for guides but haven't found any site useful so far

I tried to find a way to do it when I installed it but it didn't seem to offer me this at this time even I looked around for a while.

How do I do this shrinking of HOME and extending of VAR partition??
please be fairly specific as Im not a pro yet