Beiträge von blindguy

mdadm --assemble /dev/md127 /dev/sdm /dev/sdo /dev/sdp --verbose --force
mdadm: looking for devices for /dev/md127
mdadm: no RAID superblock on /dev/sdp
mdadm: /dev/sdp has no superblock - assembly aborted

Is there a way to copy the superblock from M or O to P ?

mdadm --examine --scan -v
ARRAY /dev/md/raid01 level=raid5 metadata=1.2 num-devices=3 UUID=0f5cd663:ce55dc39:214f9bf8:2f4fb26e name=zed:raid01
spares=1 devices=/dev/sdm,/dev/sdo
ARRAY /dev/md/raid02 level=raid5 metadata=1.2 num-devices=4 UUID=8ee7fc1c:9dc7207c:cd21a415:b4d6333d name=zed:raid02
devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sda
ARRAY /dev/md/raid04 level=raid5 metadata=1.2 num-devices=3 UUID=fe65fb09:844373b9:2745ddc9:4bad7f79 name=zed:raid04
devices=/dev/sdf,/dev/sde,/dev/sdg
ARRAY /dev/md/raid03 level=raid5 metadata=1.2 num-devices=5 UUID=a8252b01:b3df2b11:b985b9f6:951a2c64 name=zed:raid03
devices=/dev/sdk,/dev/sdi,/dev/sdh,/dev/sdj,/dev/sdl

I'm all messed up in the superblock

mdadm --assemble /dev/md127 /dev/sdm /dev/sdo missing --verbose --force
mdadm: looking for devices for /dev/md127
mdadm: cannot open device missing: No such file or directory
mdadm: missing has no superblock - assembly aborted

No backup, dam dam dam.

After reboot drive letters changed. Now, the drive letters are M, O and P.

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md124 : active raid5 sdj[0] sdl[4] sdk[5] sdh[2] sdi[1]
7813531648 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

md125 : active raid5 sde[0] sdg[3] sdf[4]
2930014208 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md126 : active raid5 sdc[0] sda[3] sdd[2] sdb[1]
8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

md127 : inactive sdm[3] sdo[5](S)
5860531112 blocks super 1.2

unused devices: <none>

When I try to do the zero superblock, I get a strange error:

mdadm --zero-superblock /dev/sdp
mdadm: Unrecognised md component device - /dev/sdp

After it rebuilt, now in the front end it is listed as clean, failed and when I do a mdstat it looks not proper.

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sdo[5](S) sdp[4](F) sdm[3]
5860530176 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/1] [__U]

md124 : active raid5 sdj[0] sdl[4] sdk[5] sdh[2] sdi[1]
7813531648 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

md125 : active raid5 sde[0] sdg[3] sdf[4]
2930014208 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md126 : active raid5 sdc[0] sda[3] sdd[2] sdb[1]
8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

unused devices: <none>

Front End info:

Number Major Minor RaidDevice State
0 0 0 0 removed
1 0 0 1 removed
3 8 192 2 active sync /dev/sdm
4 8 240 - faulty spare /dev/sdp
5 8 224 - spare /dev/sdo

I run OMV as the host and then virtualbox on that host and then a few other OMV instances for testing and other things. Can I use this to access the host OMV RAID arrays directly from the VM's?

Thanks, the raid is in recovery now. Appreciate the assistance.

I have a bit of a problem. I had to replace my motherboard and after I replaced it, one of my arrays is messed up. Well actually, teo of them are messed up but one is resyncing.

i have a three drive array with external usb 3.0 drives - md127. Hoever one of the drives, (currently sdo) is assigned to array md123 and I can't do anythign to fix it.
when I look at the RAID in the web gui I can't even see md 123 but I see it when I do a cat /proc/mdstat.

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]

md123 : inactive sdo[1](S)
2930265556 blocks super 1.2

md124 : active raid5 sdj[0] sdl[4] sdk[5] sdh[2] sdi[1]
7813531648 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

md125 : active raid5 sde[0] sdg[3] sdf[4]
2930014208 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md126 : active raid5 sdc[0] sda[3] sdd[2] sdb[1]
8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
[====>................] resync = 23.1% (676974720/2930265088) finish=295.8min speed=126918K/sec

md127 : active raid5 sdp[4] sdm[3]
5860530176 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [U_U]

unused devices: <none>

I need to somehow remove sdo from md123 and then delete md123 and then readd sdo to the md 127 and rebuild it. I think I can do a mdadm --add /dev/md127 /dev/sdo to add it back in but it wont let me do a mdadm --fail /dev/md123 /dev/sdo or a
mdadm --remove /dev/md123 /dev/sdo so i can't remove it so it won't let me add it.

Any thoughts and suggestions are welcome.

Is anyone using the MegaRAID Storage Manager(MSM) software for LSI card's?

I tried DL'ing it and getting it going but had many problems.

Any assistance is appreciated.

That is awesome!! What kind of case is that?

Also, are you using the MegaRAID Storage Manager(MSM) software for the LSI card?

I installed csh so now I get abit further.

It looks like the installed wants to do somethign in /usr/lib64 and I don't have that, I have a /usr/lib. I downloaded the 64bit version, think I should try the 32 bit version?

Checking for any Old Version
./deleteOldVersion.sh: 1: ./deleteOldVersion.sh: rpm: not found
No Old Version Found
Continuing with installation
./RunRPM.sh: 5: [: 0: unexpected operator
File /usr/lib64/libstdc++.so.6 not found
Install the libstdc++ rpm from the OS CD and retry
Refer to MSM readme for more details

I don' t want to hi-jack this thread, so I think I'm going to create a thread in another thread asking for installation notes. Thanks.

davidh2k, I'm trying to figure out how to install the MegaRAID Storage Manager(MSM) it won't let me ./install.csh I get bad interpreter messages. Dyou happen to ahve any notes on how you installed it?

Zitat von davidh2k

Yes. Without it you can't set when it should do the the "scrubbing" how mdadm it names. (3ware/LSI just calls it verify).

I found the Latest MegaRAID Storage Manager (MSM) for Lunix 64 bit, do I also need to install the drivers in the Linux Driver-RH5_SLES10_P20 package?

Also, I'm not aware about this 'scrubbing'. How often should I be doing that?

Are you using the OMV box as your plex client?

If you are not then increasing the CPU on the server will not help stutter unless you are transcoding the content.

Does 720p and 1080p content both stutter?

I was getting stuttering on 1080p content when using a wireless connection. &nbsp;To get 1080p to not stutter I had to use a wired connection.

I got a LSI LSI00244 (9201-16i) and love it. I didn't install any management software, just put it in the MB and it works great. should I install the management software?

Update:

It turns out the SATA ports on the MB were only SATA300!! This forced me to have a MB update.

New MB:
ASRock 970 Performance AM3+ AMD 970 SATA 6Gb/s USB 3.0 ATX AMD Motherboard

I'm now getting the errors for 4 different drives.

Device: /dev/disk/by-id/scsi-SATA_ST31500341AS_9VS1H3R2 [SAT], unable to open device
Device: /dev/disk/by-id/wwn-0x5000c500113169ba [SAT], unable to open device
Device: /dev/disk/by-id/scsi-SATA_ST3500418AS_5VM3QV08 [SAT], unable to open device
Device: /dev/disk/by-id/wwn-0x5000c5001bfdcb62 [SAT], unable to open device

However, when I do the ls -la all of them tell me cannot access/cannot access

root@zed:~# ls -la /dev/disk/by-id/scsi-SATA_ST31500341AS_9VS1H3R2
ls: cannot access /dev/disk/by-id/scsi-SATA_ST31500341AS_9VS1H3R2: c
root@zed:~# ls -la /dev/disk/by-id/wwn-0x5000c500113169ba
ls: cannot access /dev/disk/by-id/wwn-0x5000c500113169ba: No such file or directory
root@zed:~# ls -la /dev/disk/by-id/scsi-SATA_ST3500418AS_5VM3QV08
ls: cannot access /dev/disk/by-id/scsi-SATA_ST3500418AS_5VM3QV08: No such file or directory
root@zed:~# ls -la /dev/disk/by-id/wwn-0x5000c5001bfdcb62
ls: cannot access /dev/disk/by-id/wwn-0x5000c5001bfdcb62: No such file or directory

I think these are old drives that i may have pulled out of the arrays but for some reason they are still erroring out. Any thoughts on how I can stop the messages?

It tells me it can't find that file or directory.

root@zed:~# ls -la /dev/disk/by-id/wwn-0x5000c5001bfdcb62
ls: cannot access /dev/disk/by-id/wwn-0x5000c5001bfdcb62: No such file or directory

I am getting the following error and can't figure out which drive to replace.

The following warning/error was logged by the smartd daemon:
Device: /dev/disk/by-id/wwn-0x5000c5001bfdcb62 [SAT], unable to open device
For details see host's SYSLOG.

I can't figure out which hard drive this is without /dev/sdX or soemthing.
Where is this host syslog file?

Zitat von jhmiller

I have this on my to do list but there has not been much demand for it. It will take quite a lot of work to get it going as there are a lot of variables depending on if user has pro licence or not. If no licence then instead of installing the free version of newznab I would install the other version (fork of newznab) as the free version is too limited to be of any real use.

At least it is on a list somewhere!! I really do appreciate all the hard work everyone does to keep OMV gonig. Thanks for everything!!

I would love a newznab plugin. I thought there was one but I think I just I used the jhmiller script to install it but it would be great to just load the plugin and have it work as well as having a couple of options such as being able to tell it where to store the database (like the Plex plugin).