LinuxMCE Forums
General => Installation issues => Topic started by: S4Howie on March 03, 2016, 09:43:41 pm
-
I created a raid array in my System. But if i take a look at the Webadmin Raid Section it tells me the Raid is Damaged.
I think everything is correct all drives are there,all are formated and partionated.
Here is fdisk -l:
dcerouter_1047678:~# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
81 heads, 63 sectors/track, 191411 cylinders, total 976773168 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: 0xd545b967
Device Boot Start End Blocks Id System
/dev/sda1 2048 976773167 488385560 83 Linux
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
81 heads, 63 sectors/track, 191411 cylinders, total 976773168 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: 0x663227a6
Device Boot Start End Blocks Id System
/dev/sdb1 2048 976773167 488385560 83 Linux
Disk /dev/md127: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders, total 1953542144 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0xc1649732
Device Boot Start End Blocks Id System
/dev/md127p1 2048 1953542143 976770048 83 Linux
Disk /dev/sdc: 124.2 GB, 124218507264 bytes
255 heads, 63 sectors/track, 15102 cylinders, total 242614272 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: 0x00000001
Device Boot Start End Blocks Id System
/dev/sdc1 * 63 219303314 109651626 83 Linux
/dev/sdc2 219303315 242613629 11655157+ 82 Linux swap / Solaris
My Sytem is:
/sda is 1 Raid Disk
/sdb is 2 Raid Disk
/md127 is the raid
/sdc is the systemdisk(not in raid)
Mdadm detail tells me:
dcerouter_1047678:~# mdadm --detail /dev/md127
mdadm: excess program on PROGRAM line: /usr/pluto/bin/monitoring_RAID.sh - ignored
/dev/md127:
Version : 1.2
Creation Time : Thu Mar 3 20:07:05 2016
Raid Level : raid0
Array Size : 976771072 (931.52 GiB 1000.21 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Thu Mar 3 20:07:05 2016
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 512K
Name : dcerouter:0 (local to host dcerouter)
UUID : 212d1c96:296dc5ec:a9969cfb:8db856e7
Events : 0
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
But if i take a look in the Webadmin it tells me Raid is Damaged.39 CORE Storage Software Raid 0 /dev/md127p1 2 931.52GiB DAMAGED
What is wrong?
Howie
-
Hi Howie, it's a bug in the webadmin iirc there is an issue for it in gitlab. We'd welcome patches to fix it up. I'd do it myself but I don't have a raid array in my core.
J.
-
Hi phenigma,thank you for the information of the bug. I think im far away from knowing all to help with patches in near future. I know just the Linux Basics and Google is my best friend here too,i dont have knowledge of any writing. I am imperessed of myself how far i have even come with 14.04. You guys made a fantastic job.Thank you
Howie
-
What does the following command return for you:
mdadm --detail /dev/md127 | grep "State :" |cut -d":" -f2
You might also want to look at /usr/pluto/bin/monitoring_RAID.sh - That is the script that decides what state a RAID is in for LinuxMCE
-
I can not test this atm, i realized the cpu and memory of my old PC i was running the Core is way to slow to handle all my MDs in a decent way.I waited for hours just to regen 1 Orbiter. But it was my testing Object anyway. I have a other Core running which is way faster,i want to install 14.04 on a USB Stick there to have the internal HDD just been busy with TV Recoding and no System Load.So far i have the system running on the internal HDD an i see some little stucks from time to time when i watch Live TV in 2 or 3 MDs.BTW its just a green Seagate.5300UpM.
Im going to buy 1 other PC soon,a decent machine which can handle what i need fast.In there im going to install a Raid again.Until than this project is sleeping.
Howie
-
Don't install on USB. USB is great for reading files from or for transporting media, but putting the root disk onto USB will bring your system to a crawl, especially due to LinuxMCE's use of MySQL.
-
What do you mean with bringing the system to a crawl?
Do you mean the system makes to many reads and writes on the USB that the Stick will be damaged very soon?Or do you mean the USB port will be in a to heavy load all the time?
I installed it for testing yet on USB,and it running fine so far.I choosed a 64bg 130MB/s access rate Stick,i installed 14/04 first and did a net install over it.In my Bios i choosed to handle the stick as USB-HDD and it is first in Boot,so i could also install the MBR just on the Stick,Grub is installed nice there.I can now switch between HDD and USB Boot just by changing the first Boot device in Bios.And because of the 2 seperate Installs and MBRs it always chooses the right one as default.Very nice.
Im curious about how long that will live on a USB Stick.
Howie
-
The speed of the system will be a problem. Things will be fine as long as you only have a small media collection and using it mainly for automation purposes. And it is not about having the media collection on the stick, but because of the MySQL database on it.
-
Because of the speed i wantto buy a faster machine anyway soon. But for now i im impressed how good it works from a USB Stick.I have just LinuxMCE installed there,while Mythtv records now to the internal HDD.So no problem having 2 recodings and watching Live TV at the same time.
For now my Mediadatabase isnt that big so it might work for some time.My Media is stored on a Windows Server and shared per Samba,the USB stick will not been used for storing any Media.
Howie
-
As I said: It is not storing the media on the stick, it is the mysql database on the stick. Great, if it does work for you. If you experience some problems down the road, you know where to look.