Beiträge von Ackriss

Ackriss · 4. September 2016

I fixed it after reading similar posts, that had good help.

What I did:

#: mdadm --stop /dev/md127

#: mdadm --assemble --force --verbose /dev/md127 /dev/sd[dgfebc]

mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sde is identified as a member of /dev/md127, slot 3.
mdadm: /dev/sdf is identified as a member of /dev/md127, slot 5.
mdadm: /dev/sdg is identified as a member of /dev/md127, slot 4.
mdadm: added /dev/sdc to /dev/md127 as 1
mdadm: added /dev/sdd to /dev/md127 as 2
mdadm: added /dev/sde to /dev/md127 as 3
mdadm: added /dev/sdg to /dev/md127 as 4
mdadm: added /dev/sdf to /dev/md127 as 5
mdadm: added /dev/sdb to /dev/md127 as 0
mdadm: /dev/md127 has been started with 6 drives.

Thank you For OMV and a great community.
Kris.

Ackriss · 4. September 2016

Hello all,

My 6 disk x 2TB(WD red) raid 5 is missing after a reboot.

Need a hand fixing it please.
Some info:

Code

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdb[0] sdf[6] sdg[5]
      5860540680 blocks super 1.2

Code

~# blkid
/dev/sdd: UUID="3be1cb4a-e960-b930-43ba-9f20c19a7cb2" LABEL="MediaNAS:Raid101" TYPE="linux_raid_member" UUID_SUB="80ae7ed9-8a12-2c7e-4785-5fe4adcb62d4"
/dev/sdg: UUID="3be1cb4a-e960-b930-43ba-9f20c19a7cb2" LABEL="MediaNAS:Raid101" TYPE="linux_raid_member" UUID_SUB="13350d09-0433-f1a8-cf31-667369cdb743"
/dev/sdh1: LABEL="OMV_Backup" UUID="68049488-6d25-43a8-9309-9c629436b5dd" TYPE="ext4"
/dev/sdf: UUID="3be1cb4a-e960-b930-43ba-9f20c19a7cb2" UUID_SUB="f119658d-e374-08a8-99ac-4aea4ed7d40a" LABEL="MediaNAS:Raid101" TYPE="linux_raid_member"
/dev/sda1: UUID="781d2de1-1513-4dac-888a-f51db9fb30f8" TYPE="ext4"
/dev/sda5: UUID="d8d2d03c-e093-4b74-be04-e479e994b2d5" TYPE="swap"
/dev/sde: UUID="3be1cb4a-e960-b930-43ba-9f20c19a7cb2" UUID_SUB="c4792bf9-0f71-d48c-f4c6-5a59493013a1" LABEL="MediaNAS:Raid101" TYPE="linux_raid_member"
/dev/sdb: UUID="3be1cb4a-e960-b930-43ba-9f20c19a7cb2" UUID_SUB="64a5d707-b857-52a7-b667-627b9e0b78fe" LABEL="MediaNAS:Raid101" TYPE="linux_raid_member"
/dev/sdc: UUID="3be1cb4a-e960-b930-43ba-9f20c19a7cb2" UUID_SUB="893deef5-f89a-4dbc-f604-c7a043409462" LABEL="MediaNAS:Raid101" TYPE="linux_raid_member"

Code

cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md127 metadata=1.2 spares=0 name=MediaNAS:Raid101 UUID=3be1cb4a:e960b930:43ba9f20:c19a7cb2


# instruct the monitoring daemon where to send mail alerts
MAILADDR mailme@verizon.net
MAILFROM root

Alles anzeigen

Code

# fdisk -l


Disk /dev/sda: 80.0 GB, 80025280000 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156299375 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: 0x0006c7fe


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    74969087    37483520   83  Linux
/dev/sda2        74971134    78239743     1634305    5  Extended
/dev/sda5        74971136    78239743     1634304   82  Linux swap / Solaris


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 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, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 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, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdd doesn't contain a valid partition table


Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdf doesn't contain a valid partition table


Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sde doesn't contain a valid partition table


Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdg doesn't contain a valid partition table


Disk /dev/sdh: 8004 MB, 8004304896 bytes
19 heads, 5 sectors/track, 164562 cylinders, total 15633408 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: 0x00043331


   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1            2048    15632383     7815168   83  Linux

Alles anzeigen

Thanks

Kris.

Ackriss · 28. Dezember 2015

Zitat von ryecoaaron

Nope. I know my LSI 9211-8i can but my LSI 9260-8i can't.

+1 for a LSI 9211-8i. I bought a Dell Perc H310 on Ebay about a year ago for < 55$(US). The Dell H310 is almost identical to the LSI 9211-8i, and it accepts the LSI IT firmware.

Here's a link to help if you choose. "flash-dell-perc-h310-with-it-firmware"

Ackriss · 24. Oktober 2015

This post HERE helped me fix my mail errors I had.

I think It will help you as well, I hope.

Kris.

Ackriss · 25. November 2012

Well the fault seems to have been a network cable. It's bad or it's picking up interference ... . .. . . :oops:

It is solved now. .

Thanks for the advise.

Ack,

Ackriss · 23. November 2012

What i meant was, Thanks for the tips and keep them coming.

Because I still have no joy waking the OMV box.

Ackriss · 23. November 2012

Yes I can wake other computers on the switch.

"/etc/default/halt" has NETDOWN=no

A switch reboot . . got me to wipe the dust off it. . :lol:

Thanks for the tips.

Ackriss · 23. November 2012

From a xbuntu desktop/terminal I've tried etherwake, powerwake and wakeonlan with various combos of the ip/mac.

From a Win7 box WakeMeOnLan

Thanks

Ackriss · 23. November 2012

I’m trying to get my OMV 0.4.5 box to suspend with autoshutdown and so far no luck could use a bit of advise.

What I have done so far:
Ticked Wake on Lan in the network section of OMV.
Installed Autoshutdown plug-in, and set it up and added “SHUTDOWNCOMMAND="pm-suspend"” to the extra options.

I test at this point and it's not working, looking at the autoshutdown log I see the last entry is a pm-suspend call. So I ssh in to OMV and see if I can manually do a pm-suspend and get a “command not found”

At this point I realize that pm-utils is not installed. So I do so, and any of it dependencies with and “apt-get install pm-utils” and reboot and test.

Ok, now it seems to suspend fine. However wake up is a different matter.

I have a Asus C60M1-I mini-itx. In it's bios the only settings are: Power on by PME “enable/disable” . So I enable it. And retest. And still no luck in the wake up.

I could use some advise at this point.

Some machine info that could help:

Code

# lspci | grep -i 'ethernet'
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09)


# ethtool eth0 | grep -i 'wake-on'
	Supports Wake-on: pumbg
	Wake-on: g


# cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
SBAZ	  S4	 disabled  
PS2K	  S4	 disabled  pnp:00:0a
UAR1	  S4	 disabled  pnp:00:0b
P0PC	  S4	 disabled  pci:0000:00:14.4
UHC1	  S4	 disabled  pci:0000:00:12.0
UHC2	  S4	 disabled  pci:0000:00:12.2
USB3	  S4	 disabled  pci:0000:00:13.0
UHC4	  S4	 disabled  pci:0000:00:13.2
USB5	  S4	 disabled  pci:0000:00:16.0
UHC6	  S4	 disabled  pci:0000:00:16.2
UHC7	  S4	 disabled  pci:0000:00:14.5
PE20	  S4	 disabled  pci:0000:00:15.0
PE21	  S4	 disabled  pci:0000:00:15.1
RLAN	  S4	 disabled  pci:0000:04:00.0
PE22	  S4	 disabled  
PE23	  S4	 disabled  
BR14	  S4	 disabled  pci:0000:00:04.0
PWRB	  S4	*enabled   


# grep 'NETDOWN=' /etc/init.d/halt
NETDOWN=yes


# grep 'ethtool' /etc/network/interfaces
    pre-down ethtool -s $IFACE wol g

Alles anzeigen

Thanks.
Ack

Ackriss · 31. Juli 2012

Hello all.
I figured it out.

The options in the text box "Extra options" where separated with a CR LF. replacing the CR LF with a TAB for a whitespace seems to work.

Thanks for the pointers.

Ack.

Ackriss · 30. Juli 2012

Much thanks,

Bash

#!/bin/bash
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
FLAG="6"
SLEEP="180"
RANGE="2..254"
CHECKCLOCKACTIVE="false"
UPHOURS="6..20"
NSOCKETNUMBERS=""
SYSLOG="true"
VERBOSE="true"
FAKE="false"
NW_INTENSESEARCH=
TEMPPROCNAMES="in.tftpd"^M
LOADPROCNAMES="smbd,nfsd,transmission-daemon,mt-daapd"

Alles anzeigen

thats the file. I see the errant "^M" .

Logic tell me to edit it out. However the file clearly reads "# WARNING: Do not edit this file, your changes will be lost."

Advise please.

Thanks.
Ack.

Ackriss · 30. Juli 2012

Hello all.
I’m having some setup errors that I cannot fix myself and could use some advice please.
In the log file I’m seeing :

Code

openmediavault /etc/init.d/autoshutdown: Autoshutdown-script starting ...
openmediavault logger: autoshutdown[27841]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
openmediavault logger: autoshutdown[27841]: INFO: ' X Version: 0.3.3.3'
openmediavault logger: autoshutdown[27841]: INFO: ' Initialize logging to local6'
openmediavault logger: autoshutdown[27841]: INFO: ' /etc/shutdown.conf loaded'
openmediavault logger: autoshutdown[27841]: INFO: ' ------------------------------------------------------'
openmediavault logger: autoshutdown[27841]: INFO: ' Checking config'
openmediavault logger: autoshutdown[27841]: INFO: ' NETSTATWORD not set in the config. The check for connections, like SSH (Port 22) will not work on the CLI until you set NETSTATWORD'
openmediavault logger: autoshutdown[27841]: INFO: ' If you run this sript at systemstart with init.d it will work as expected'
openmediavault logger: autoshutdown[27841]: INFO: ' Read the README for further Infos'
openmediavault logger: autoshutdown[27841]: WARN: ' Invalid parameter list format: TEMPPROCNAMES [tproc1,tproc2,tproc3,...]'
openmediavault logger: autoshutdown[27841]: WARN: ' You set it to 'in.tftpd#015', which is not a correct syntax.'
openmediavault logger: autoshutdown[27841]: WARN: ' exiting ...'

Alles anzeigen

And I Guess this is telling me that I have “'in.tftpd#015'” listed as a configuration option?

However in the web interface it is set as TEMPPROCNAMES="in.tftpd"in extra options.

I can leave the extra option TEMPPROCNAMES blank and still would get the warning:

Code

openmediavault logger: autoshutdown[27841]: WARN: ' You set it to '#015', which is not a correct syntax.'

I have looked at the config files in etc/ autoshutdown.* and I do not see the “'#015'” anywhere. So I do not know where its finding that '#015' in the warning.
I’m doing something wrong?

Thanks,
Ack.

Beiträge von Ackriss

Recovery help please

Recovery help please

HW Raid Contoller use Software Raid

It's can't send email notification when I use 465 port and enabled ssl/tls.

[RESOLVED] Trying to get Wol/suspend + autoshutdown working

[RESOLVED] Trying to get Wol/suspend + autoshutdown working

[RESOLVED] Trying to get Wol/suspend + autoshutdown working

[RESOLVED] Trying to get Wol/suspend + autoshutdown working

[RESOLVED] Trying to get Wol/suspend + autoshutdown working

Autoshutdown-Plugin

Autoshutdown-Plugin

Autoshutdown-Plugin