Beiträge von harpo3223

Thank You all in advance for your time and contribution to my request your help si truly appreciated.

I can only put the system into sleep or Suspend mode successfully only once without a clean reboot.
I am able to Shut down, Reboot without any problems.

What happens: It goes into sleep mode just fine I can then wake it up via Ethernet wake-up command. However I can only put it to sleep just once unless I reboot or shut down.

If I try to put back to sleep without a reboot or shutdown I get the following error:

Error #4001:
exception 'OMVException' in /usr/share/openmediavault/engined/rpc/system.inc:213
Stack trace:
#0 [internal function]: OMVRpcServiceSystem->standby(NULL, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('standby', NULL, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('System', 'standby', NULL, Array, 1)
#4 {main}

I have all bios setting as per the Manual correctly set no overclocking (Default Settings)

------------------------

OMV Version 1.18 (Kralizec)
Linux Kernel 3.2.0-4-amd64

My Hardware (Not Overclocked)

Intel core2 quad CPU Q6700 @ 2.66Ghz
Asus P5KC
8 Gig Memory
8 Drive Adaptec ATA card in PCIexpress Slot (None a Hardware Raid Card)

ryecoaaron

I did as instructed and here is what happened.
Ok I had no luck with plugin directly into the Motherboard, However after I plugged everything back into it original way:
4 Western Digitals on ch1 and 4 Hitachi on ch0 it started working again.
I did however substituted one of the WD for a Seagate then put back the original WD and presto it work!
I do not really know what made it work but it works now and I am now in process of backing up everything just in case.

Thanks I will work on it this evening (PST) will get back with results ...

ryecoaaron,

after checking my motherboard it only has 4 sata plugs and I have 5 drives 1 with OMV plus 4 WD green drives in raid5.

ryecoaaron

I will go ahead and remove the card plug the WD green drives to the mother board I will assume they have to be in the same order as on the card when I plug them into the motherboard correct.
Further more does it matter that they were set up on the card and not on the mother board. I also have another card Promise brand again none hardware Raid should I also try that? or just stick with the board for now?
Will I have to do anything with the command line when I boot or should it just pick up on it own?

i will await your response thanks...

Thanks David
for your explanation

So do you think I will be able to recover from the existing 2 drives and if so is it as easy as just replacing the drives and rebooting? or will I have to do some kind of command from the command line.
by the way which was the other drive that had the error? I am aware of sdh which one was the other.

Thank You for sharing your knowledge.

I have 2 spare drives same size but are Seagates will i be able to recover from the two existing good drives?

When I ran some testing earlier (yesterday) I was able to run the other Hitachi good drives on Both Ch0 and CH1 of Adaptec Card (not a hard Raid card) and they ran fine. Now as far as a backports kernel I do not even know what that means.
Sorry! you got me stomped there. Are the errors coming form - sdh?

ryecoaaron

Forgive me but how can I get you that data you need ( dmesg?)

Davidh2k thanks for your input and help

Unintentionally I have heard about The "lack of TLER on the greens" but I am ashamed to admit I don't truly know what that means.
or if there is a fix and if so hopefully some what easy for a LINUX newbie.

here you go..

root@OMV:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active (auto-read-only) raid5 sdi[1] sdh[3] sdf[2]
5860538880 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]

unused devices: <none>
root@OMV:~#

I ran the command as requested here is the output
Am I right to assume one of my drives are bad?

Last login: Sun Apr 6 15:59:59 2014 from 192.168.1.22
root@OMV:~# mdadm --assemble --run --force /dev/md0 /dev/sd[fghi]
mdadm: forcing event count in /dev/sdi(1) from 1035808 upto 1035850
mdadm: /dev/md0 has been started with 3 drives (out of 4).
root@OMV:~#

Forgive me ryecoaaron I should of had said that I have a total of 8 drives on adaptec card none hardware raid the first set of 4 Drives on Ch0 which I have intentional removed it from Raid10 and the disks have been cleared this is why they show this way they are Hitachi drives

The raid5 is the second set of 4 drives is where I am having problems, these are western digital Green and are on Ch1. Should I disconnect the Hitachi drives to avoid confusion since those do work find and I can see them when I place them in raid form?

connector are fine on all 8 drives the Hitachi drives are not formatted or partitioned.

My apologies please advice if you would like me to disconnect the Hitachi drives.

With the command blkid this is what I get

root@OMV:~# blkid
/dev/sda1: UUID="cfe08dc0-a0a2-4281-8e5a-fb5668928dbf" TYPE="ext4"
/dev/sda5: UUID="9c96be74-c8db-41d2-b5ca-0dc8e1fa199d" TYPE="swap"
/dev/sdf: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
/dev/sdg: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
/dev/sdh: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
/dev/sdi: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
root@OMV:~#

Thanks for your quick reply here is what I get

root@OMV:~# fdisk -l

Disk /dev/sda: 40.0 GB, 40000000000 bytes
255 heads, 63 sectors/track, 4863 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: 0x00072afa

Device Boot Start End Blocks Id System
/dev/sda1 * 1 4660 37428224 83 Linux
/dev/sda2 4660 4863 1631233 5 Extended
/dev/sda5 4660 4863 1631232 82 Linux swap / Solaris

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdb doesn't contain a valid partition table

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdc doesn't contain a valid partition table

Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdd doesn't contain a valid partition table

Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sde doesn't contain a valid partition table

Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdf doesn't contain a valid partition table

Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdg doesn't contain a valid partition table

Disk /dev/sdh: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdh doesn't contain a valid partition table

Disk /dev/sdi: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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/sdi doesn't contain a valid partition table
root@OMV:~#

The Storage Folders shows as follows:

Disk show up in Physical Disk area however no raid is visible in Raid Management all blank. The Filesystems shows as follows - device n/a, Mounted Yes, and Status missing.
All was working find then started acting up 3days ago and finally just stopped working Today. File folders show up in windows explorer but can not access files. I have tried searching but some of the prior post do not match my situation
if this topic has been answered somewhere else a link would be appreciated.

When I run the following command I get:
root@OMV:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
root@OMV:~#

Hi Tekkbebe, My systems seem to check out fine as per memtest but time will tell.

I am as puzzled because I do not recall doing any OMV updates or add-ons and the Original Titled problem on this thread just statred to happen. I agree that things don't just happen. Thus why I emphasize I don't recall doing any updates etc.. However there was a total of 4 users this happened to at the same time (that is strange). Now 2nd problem towards the end of this thread, which was also documented in combination with on the following Thread:

(plugins update fail Postby renovatio » Mon 18. Nov 2013, 10:28 Plugin error) http://forums.openmediavault.org/viewtopic.php?f=3&t=3100

Was caused I believe by spelling errors or not recalling the exact command in the suggested instructions throughout this thread while trying to solve the original problem. This is why I did a recap as noted on the past 2 or 3 threads above to hopefully warn others.

In closing Thank you for your time and all the help if anything changes I will update you in case the problem is deeper than just my machine.

[ERROR RESOLVED] Note: Read Carefully there are two errors in this thread, I am not sure if they may be similar, However my problem and error have been resolved and everything is now working fine. "NO MORE ERRORS FOR ME"

My Plugin error was as noted below and now has been resolved.

--------------error-----------------------------
Failed to execute command 'export LANG=C;sudo dpkg-query --list 'openmediavault-*'':

Error #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C;sudo dpkg-query --list 'openmediavault-*'': ' in /var/www/openmediavault/rpc/plugin.inc:186
Stack trace:
#0 [internal function]: PluginRpc->getList(Array)
#1 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('Plugin', 'getList', Array)
#3 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
#4 {main}

------------------Solution-----------------------------------------

The Following Directory was named as follows: /var/lib/dpkg/update
and should be named: /var/lib/dpkg/updates