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.


Topics - S4Howie

Pages: [1]
1
Installation issues / update problems/mistakes made(solved)
« on: March 09, 2017, 05:10:55 am »
In a nighly crazyness i acidently applied the LTS security updates on 1 MD.It told me Warning i should apply security updates to my hardware stack to get LTS support.But now this MD is somekind of broken. If i want to boot up it loads the vmlinuz but then it
stoping and telling me Could not find ramdisk image;   XX/initrd.img

If i look into the tftp folder the symlinks are there for initrd.img. I tried to copy the symlinks from a folder of another MD then the broken MD boots up but its then updating itself again and rebooting and then again telling Could not find ramdisk image;   XX/initrd.img

so i went into LinuxMCE admin to MD Section and rebuild the image. The rebuild MD boots up but its then updating itself again and rebooting and then again telling Could not find ramdisk image;   XX/initrd.img

I even deleted the MD,setup a new with all new Device names. It boots up applying itself updates reboots and same again Could not find ramdisk image;   XX/initrd.img.

Is there a way to get it back normal?Why even after delete and new setup it seems to apply the security updates?How can i stop that now?And just let it do the normal updates when i setup a new 1 or rebuild the image?I hope there is a way.

Thanks so far

2
Installation issues / Problem with switching OS on MD
« on: February 18, 2017, 12:38:42 am »
I have 1 MD using with an internal HDD and Windows 10 on it,so far it was never a problem to switch between the MD or Windows 10. The MD is configurated to boot over Network and when its up and running,you hit the Start as OS on Harddrive Button in Orbiter Power Section and the MD restarts but the PXE Bootfile it gets from the Core then lets it jump over Network Boot and boots up from Harddrive the Windows 10. If u want to switch back u hit the Boot as MD Button in an Orbiter.Then restart your Windows and the MD comes back again cause now the PXE Bootfile let it boot over Network again. But here is the problem the MD stays in 1 Mode until u switch and in some of the last updates i cant tell which one exact im sry the Boot up as MD Button is not shown anymore in all Orbiters at my setup 14.04 latest updates.
Can someone help,would be nice to have my MD boot up again,it is the 1 im using most in my living room and now its stuck in Windows10 mode.

Thanks Howie

3
Installation issues / 14.04 Raid Array Damaged
« 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


4
Installation issues / HaltMD/WakeMD 14.04
« on: February 28, 2016, 05:25:54 pm »
In my setup, i want my MDs not to be started when i reboot my Core. So i unchecked the enable wakeMD script in boot up.It is still unchecked after a boot up.I did that on the Core and Core/Hyprid.There are no hooks anymore set Enable Wake MD.But my MDs still booting up on a reboot.
If i check again on the webadmin still no hook but more down it tells me the wakeMD scripts still enabled. How to disable then?

I also recognized my MDs get not shutdown signal when i reboot my Core. But i can say they dont crash,they reload as soon as my Core is back up,and whole system is running fine.

Howie

5
Since update a332f49a my Core reloads as soon as i want to play an Internet Radio Station.Exeactly in that moment when i choose a channel and the window with attributes should be shown forces a reload of my Core.No matter if chosen from MD or Orbiter reload is forced everytime.I did delete all stations and reboot the core added the stations back via auto function depending on region but reload is still forced.I can confim anything worked well bevor update a332f49a.

Howie

6
Installation issues / [SOLVED]14.04 MythTV problems,All Tuners busy
« on: February 10, 2016, 05:55:54 pm »
Hi all,i am huge Fan of LinuxMCE since several years,i worked long time now with 7.10 cause i could grap a Firre Chief Remote in Europe some years ago and just fell in love with with it.

But now since the time of Smartphones and Pad´s,i decided to go with newer LinuxMCE version. I tested a lot in the last days with several version out there,i am impressed what you guys did the last years,many really good improvments i recognized so far. I need to say a BIG Thank You for all the work you done here Developers!!

Ok more to the point:
I ended up trying 14.04 until now,cause here i manged to get most things work i want to work.I am still testing hard and will try to help you further in next time as much as i can.
I have 14.04 installed over the Net,with Kubuntu 14.04.03 preinstalled and updated,after that i updated LinuxMCE aswell.So i am at Version 2.0.0.47.201601312359+296fdcd3 atm.

My WinTV Nexus-S DVB-S Card was recognized from LinuxMCE by pnp,but i had to copy the prober firmware files into /lib/firmware cause MythTV could not get a lock,it was seen but couldnt be open.After that i reboot,went back to MythTV setup and Card could be opened.So i setup the Video Sources and Input Connection and did a Channel Search,everything went fine all channels there,lock on all Transponders,no problems.

But here is the problem now,when i start to watch a channel MythTV Frontend Opens up and tries to Tune in but immidently tells me: All Tuners are currently Busy! it repeats and repeats and after serveral tries it want to reload the Backend,but a reset isnt helping much further in my case.
If i take a look at the Status page from Mythweb i can see 1 Encoder on the core currently not recording.So everything looks like prober installed,i could search for channels aswell in the setup.
I tried several things like deleting all the TV Tuners in MythTv Setup,and put them back in,i recognized sometimes LinuxMCE installs a Encoder again and shows up 2 or more after a reboot.So i deleted all Encoders again and just did a reboot and the encoder was installed again in MythTV.I just need to setup the LNB and it could work. But again in the Frontend i just receive All Tuners are Busy. I also tried several different IP for the Frontend to connect like 127.0.0.1/localhost/internal,external IP but the error still stays.

My Nexus Card worked well in all LinuxMCE releases up to 10.04,im still using it in a other install under 10.04 so the hardware is alive.

Can anyone help me further what causes the All Tuners busy error?

Thank you so far,
Howie

Pages: [1]