Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - m3freak

Pages: 1 [2] 3 4 ... 9
16
Users / Re: md RAID 1 not being auto mounted
« on: March 17, 2012, 09:11:27 pm »
Does no one know how I can fix this?  I've tried researching the issue myself: I've come up empty handed.

17
Users / md RAID 1 not being auto mounted
« on: March 17, 2012, 12:54:25 am »
I had created a RAID 1 md device via LinuxMCE's admin interface, but it never behaved correctly when the core was rebooted.  Since I had already put data on it, I decided to stop the device, and then removed it from the interface.

I manually assembled the md device from the two 1 TB drives and put the config in /etc/mdadm/mdadm.conf:

Code: [Select]
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a8280191:5f65eba2:bd9f1658:0a1d2015

I rebooted the core.  This time the raid device came up correctly.  LinuxMCE detected the raid and added it to the RAID list in the web interface with the status set to OK.

The problem is LinuxMCE has marked the two drives as REMOVED - wtf?!  I think this is the reason why the raid device isn't being auto mounted and why I'm not seeing the "new storage added" on my MD's onscreen orbiter.

The kernel says the device and the raid members are ok:

Code: [Select]
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb[0] sdc[1]
      976761472 blocks [2/2] [UU]
     
unused devices: <none>

Code: [Select]
/dev/md0:
        Version : 00.90
  Creation Time : Wed Feb  8 14:06:21 2012
     Raid Level : raid1
     Array Size : 976761472 (931.51 GiB 1000.20 GB)
  Used Dev Size : 976761472 (931.51 GiB 1000.20 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Mar 16 19:49:29 2012
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : a8280191:5f65eba2:bd9f1658:0a1d2015 (local to host dcerouter)
         Events : 0.30190

    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc

How can I fix this?  Should I do some meddling in the DB?

18
Users / Re: Onkyo TX-SR876 A/V receiver - need a custom template
« on: March 17, 2012, 12:44:19 am »
Is this a network based unit? If so, I just created a template some weeks ago and checked it in that works very well for my Onkyo. I haven't seen if has been merged into the main yet, though.

The one up from the 876 was the network unit.  From what I remember, the one up from the 876 was the top of line, and the only diff was the network feature plus a few things that took advantage of the network capability.  Otherwise, it was the same.

What model is your template catered for?

19
Users / Re: Onkyo TX-SR876 A/V receiver - need a custom template
« on: March 10, 2012, 01:28:25 pm »
Missing functions and many of the existing ones are not working correctly, unfortunately.

Thanks for the advice. I'll get started on the new template.  Oh, one more question: does the name matter?  I was going to go wtih "Onkyo TX-SR875", and then just use that for my 876.

20
Users / Onkyo TX-SR876 A/V receiver - need a custom template
« on: March 10, 2012, 02:47:15 am »
I didn't see a template for my Onkyo receiver, a TX-SR876.  The generic template for Onkyo/Integra A/V receivers doesn't work well for mine, not to mention not all of the inputs/ouputs are included.

I have a document describing the serial commands for a TX-SR875. I want to use it to build a new device template for my receiver since the 876 isn't all that different.  How should I go about it?  Am I supposed to copy an existing template or start new?  If I'm copying, how do I actually do that?  I poked around for a while and didn't see anything obvious on how to copy the existing Onkyo/Integra template.

21
Users / Re: RAID 1 created via admin GUI behaving unexpectedly
« on: February 29, 2012, 07:19:53 pm »
Is md RAID in LinuxMCE unreliable?

22
Users / Re: RAID 1 created via admin GUI behaving unexpectedly
« on: February 24, 2012, 07:32:09 pm »
Soooo...no one has encountered this in 10.04?  Should I just recreate the RAID? 

23
Users / RAID 1 created via admin GUI behaving unexpectedly
« on: February 22, 2012, 05:44:14 pm »
I used LinuxMCE's admin interface to create a RAID 1 set out of two 1 TB drives: /dev/sdb1 and /dev/sdc1.

After LinuxMCE created the array, /dev/md0, formatted the drive and synchronized the array, I rebooted the core.  After the reboot, /dev/md0 was nowhere to be seen.  Instead, I saw /dev/md_d1.  In addition, LinuxMCE's admin page for RAID reported the array as having failed.

I stopped /dev/md_d1, and assembled /dev/md0.  /dev/md1 was back online with no errors or other issues.  The data on it was accessible again at the same location LinuxMCE had set up after auto detecting it the first time around.

I tried another reboot with the same results.

After fixing it by hand again, I took a peek at mdadm.conf and found it didn't have an entry for the array.  Why?  :: cries ::

One additional piece of info: even though the array is active and synchronized, LinuxMCE's admin page is reporting only /dev/sdb1 to be present.  If I look at the "Advanced" details for the array, the "No of disks" field has "1".

Something obviously didn't go right during the creation.  How can I fix this?

24
Users / Re: Media Director no longer boots
« on: February 22, 2012, 05:27:02 pm »
Does that make sense?

Yup, that makes perfect sense.  Actually, that's a really neat feature.  I could pop a 2.5" HD in my Jetway, install Fedora + XBMC, and use that for my media needs just in the family room. When I need to use LinuxMCE, I could hit that button you described and have it boot up as a MD instead. Hmmm. 

I do like LinuxMCE and it's media integration is neat, but the presentation makes the media components hard to use.

25
Users / Re: Media Director no longer boots
« on: February 22, 2012, 06:46:09 am »
I fixed the kernel line and now the MD is booting successfully. If it happens again, I'll know where to look.

Thanks for the help!

26
Users / Re: New LMCE splash screen/logo!
« on: February 21, 2012, 09:56:03 pm »
Any feedback is much appreciated.

Looks excellent to me!  I'm sure others will agree.

Since the media part of LinuxMCE has never been up to par with the automation end of things, maybe it's time to just drop it and instead incorporate another app for the media end of things.  Yes, I'm talking about XBMC.

27
Users / Re: Media Director no longer boots
« on: February 21, 2012, 06:04:45 pm »

Try looking at this thread http://forum.linuxmce.org/index.php/topic,7842.0.html

It could be either this exact error, or perhaps digging from here could lead you in the proper direction. I would assume from your description that it could be from this corrupted line in /tftpboot/pxeboot.cfg/01-<md-mac-address>

That's the ticket: the pxe config file is hosed and I didn't even notice it.  Here's what mine looks like:

Code: [Select]
DEFAULT Pluto
LABEL Pluto
LOCALBOOT 0 #ERNEL 44/vmlinuz
APPEND initrd=44/initrd.img ramdisk=10240 rw root=/dev/nfs boot=nfs nfsroot=192.168.80.1:/usr/pluto/diskless/44,intr,nolock,udp,rsize=32768,wsize=32768,retrans=10,timeo=50 quiet splash video=uvesafb:mode_option=1024x768-24,mtrr=3,scroll=ywrap vmalloc=256m

If I had looked at it more carefully, I would have noticed the malformed "kernel" line.  Fail.

 I'll fix the fubar line and test out the MD boot tonight - I'm pretty sure it'll boot properly.

Do you know why this happened?  The thread you steered me to is from 2009!!!

28
Users / Media Director no longer boots
« on: February 20, 2012, 03:56:42 pm »
My lone MD stopped booting a few days ago.  It still gets an IP, but when it comes to downloading the initrd and kernel, it bombs out.  Well, the actual order of fail is:

1. tries to download the kernel image that was built for it (can't)
2. then it moves on to the default (no go)
3. finally tries a local boot, but since there's no local install, the PXE boot stops.

I haven't done anything to the MD config itself.  I did however update the core.  Maybe the update did something.

I can see the tftp request on the core in /var/log/syslog.  The core answers properly (I think).  

What could be wrong?

29
Users / Re: Asterisk hacked
« on: February 20, 2012, 03:51:27 pm »
I have the same, so how can we catagorize or solve this problem?

I've been working with Asterisk for over 7 years, but I haven't done an actual dial plan config for 5!  I don't know how many of the old ways to lock down the system would still work.  I think I still remember enough to understand the various options so I'm not worried about having an insecure setup (whenever I get to it).

What I used to run was solid.  I remember seeing attempts at cracking the PBX. My dial plan was built in such a way it prevented random people from gaining access to long distance.

I think joining the Asterisk mail list might be a good option.  Failing that, research, research, and study until you drop.  It'll be the only to understand how Asterisk is configured and how to change it.

Question: does LinuxMCE use plain old Asterisk, or a bunch of different apps that help administrating an Asterisk system easier?  I haven't looked into LinuxMCE's telephony feature set, at all.

30
Users / Re: Asterisk hacked
« on: February 20, 2012, 04:59:50 am »
This little lesson has taught me that what is installed default in lmce is a real security nightmare...

It's the reason why I refused to make LinuxMCE my home network's gateway/firewall.  LMCE is a big beast and I don't know enough about it to trust it.

Pages: 1 [2] 3 4 ... 9