Re: [RDD] God, I hate systemd

[Christian Pointner]

Hi,

Am 03.12.2015 um 21:06 schrieb Rob Landry:
> On Thu, 3 Dec 2015, equinox wrote:
> 
>> sudo systemctl set-default multi-user.target
> 
> That worked, but after installing security updates an rebooting, I found
> it had reset itself to graphical.target.
> 
hmmm. interesting i never hat that issue... probably a bug in
Debian. As a workaround you can also specify the default target using a
kernel command line parameter: systemd.unit=multi-user.target

Just add this to the variable GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub and update the grub config using:

# sudo update-grub

The system should then always boot into the multi-user target.

regards
 christian
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell broadcast appliance installer 2.6.5.1 seems to be allergic to 3TB disk drives???

[Christian Pointner]

Hi,

Am 14.10.2015 um 12:36 schrieb Rick Thomas:
> Thanks, Christian…
> 
> Your reply is very helpful!
> 
glad to hear.

> Is it possible to run parted (or anything else capable of creating a GPT 
> partition table) while in the installer?  In Debian I know that hiting 
> -F2 gets me a text shell console.  But I’m new to CentOS and the 
> Anaconda installer — does it have a similar feature?
> 
Sorry i don't really know the installer because i never used it.

> Alternatively, I guess I could do the installation with the 3TB disks but 
> using only 2T on each, then after the installation is over and it’s booted 
> into the installed system, I can manually re-partition the disks using parted 
> and a GPT table.
> 
> Do you think that would work?  Can you think of any “gotchas” I’m likely to 
> hit?
> 
If you use the disks only for /var/snd data store this will definitely
work. But in that case i would leave the drives untouched by the
installer and create the raid later.
In case you also want other partitions for example of the system to
reside on the same drives this will make problems because you can either
use gpt or dos partition tables per drive but not both at the same time.
It still can work though... here would be the steps to do this:

 - create a DOS partition table on both disks and install the system on
   the RAID created by the installer - leave the vast majority of the
   disk unpartioned -> ther is no point in creating a partition which
   you will through away later
 - log into the new system and use the following command to remove on
   of the drives from the raid:

# mdadm /dev/md0 --fail /dev/sda1
# mdadm /dev/md0 --remove /dev/sda1

 - use parted to create a gpt on /dev/sda and create 1 small (~32MB)
   partion and set the flag bios_grub on it. Create another partition
   for the system and one for /var/snd and set the raid flag on both of
   them. The system partition must have the same size of the system
   partition on the other drive which is still use - you can check this
   with: # parted /dev/sdb -- unit s print

   # parted /dev/sda
   > mklabel gpt
   > mkpart
  > name = 
  > fstype = 
  > start = 2048s (should be the default)
  > end = +32M
   > set 1 bios_grub on
   > mkpart
  > name = 
  > fstype = 
  > start = use default aka just hit enter
  > end = +
   > set 2 raid on
   > mkpart
  > name = 
  > fstype = 
  > start = use default aka just hit enter
  > end = -1
   > set 3 raid on
   > quit

 -  now you need to re-add the new system partition to the system raid

# mdadam /dev/md0 --add /dev/sda2

 -  create the raid for /var/snd

# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sda3

 -  wait for the system raid to resync:

# while sleep 1; do clear; cat /proc/mdstat; done

 - remove the other system disk from the raid:

# mdadm /dev/md0 --fail /dev/sdb1
# mdadm /dev/md0 --remove /dev/sdb1

 - now use parted and create the complete same setup for sdb as sda

# parted /dev/sdb
.

 - add /dev/sdb partitions to both raids:

# mdadm /dev/md0 --add /dev/sdb2
# mdadm /dev/md1 --add /dev/sdb3

 - reinstall/reconfigure grub

# grub-install /dev/sda
# grub-install /dev/sdb
# update-grub

 - before you reboot you should at least wait for the system raid to
resync.

 - reboot

Now you can create a filesystem on /dev/md1 or a LVM or wathever you
want... actually the reboot is not really necessary but as you had to
redo the bootloader setup it's nice to see whether the system still boots.

regards
 christian
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell broadcast appliance installer 2.6.5.1 seems to be allergic to 3TB disk drives???

[Christian Pointner]

Hi,

Am 14.10.2015 um 08:17 schrieb Rick Thomas:
> 
> I’m trying to install the Rivendell broadcast appliance on a machine with a 
> set of 3TB disks that I plan to use as a RAID set for /var/snd.
> 
> But whenever I tell the installer to use one of the 3TB disks as a “Raid 
> Partition”, it creates a 2TB partition and 1TB of free space.  The free space 
> can’t be used for anything — if I try to create a partition with it, I get 
> error messages about “max address”.
> 
> Anybody ever seen this?  If you have, how did you work around it?
> 
Sorry no easy solution but an very likely explanation why the installer
does this:  Dos Partition labels have a limit of 2TB. For drives bigger
than that you would need to create a GPT. Manually this can be done
using parted [1].
Once the partitions are created you can mark the partitions for RAID
using the following command:

sudo parted /dev/sda -- set raid 1 on
sudo parted /dev/sdb -- set raid 1 on

This assumes you have two drives with one partition each which should be
used as raid.

regards
 christian

http://www.cyberciti.biz/tips/fdisk-unable-to-create-partition-greater-2tb.html
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell broadcast appliance installer 2.6.5.1 seems to be allergic to 3TB disk drives???

[Christian Pointner]

Hi again,

Sorry my answer has some errors - i really should have checked before
hitting send...

Am 14.10.2015 um 10:14 schrieb Christian Pointner:
> Am 14.10.2015 um 08:17 schrieb Rick Thomas:
>>
>> I’m trying to install the Rivendell broadcast appliance on a machine with a 
>> set of 3TB disks that I plan to use as a RAID set for /var/snd.
>>
>> But whenever I tell the installer to use one of the 3TB disks as a “Raid 
>> Partition”, it creates a 2TB partition and 1TB of free space.  The free 
>> space can’t be used for anything — if I try to create a partition with it, I 
>> get error messages about “max address”.
>>
>> Anybody ever seen this?  If you have, how did you work around it?
>>
> Sorry no easy solution but an very likely explanation why the installer
> does this:  Dos Partition labels have a limit of 2TB. For drives bigger
> than that you would need to create a GPT. Manually this can be done
> using parted [1].

The article behind the link is quite old and says that on Debian/Ubuntu
you need to rebuild your kernel - forget that. Debian/Ubuntu supports
GPT since several releases.

> Once the partitions are created you can mark the partitions for RAID
> using the following command:
> 
> sudo parted /dev/sda -- set raid 1 on
> sudo parted /dev/sdb -- set raid 1 on

This is also wrong. The correct command would be:

sudo parted /dev/sda -- set 1 raid on
sudo parted /dev/sdb -- set 1 raid on

the '1' means the partition number if you have more than one partition
this is likely a higher number...
You can see which partitions exist on your drive using the following
command:

sudo parted /dev/sda print

mfg
 christian

[1]
http://www.cyberciti.biz/tips/fdisk-unable-to-create-partition-greater-2tb.html
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] OT XLR Pi Hat

[Christian Pointner]

Hi

Am 17.09.2015 um 16:23 schrieb Wayne Merricks:
> I've been contacted by the IQAudio Pi HAT guys (iqaudio.co.uk).  They're
> looking into the potential of having a balanced XLR output board for the
> Pi.  I know what we would use it for (1U rack mount receiver, Internal
> monitoring/network speakers, potentially some sort of IP Phone
> interface, maybe even a one output Rivendell box with GPIO support).
> 
Sounds great!

> The questions they've asked me is what would you want from such an addon:
> 
>   * Balanced Audio via..?
>   o XLR (may not fit into a 1U height restriction)
>   o Mini XLR

I would prefer XLR or RJ45 for the Audio - definitely not Mini XLR

>   o 3.5mm stereo/balanced Jacks

If it hase RCA plugs i would prefer 6.3mm jacks as most other devices
and patchpanels have these as well.

>   o Header pins

would be ok if they also produce/sell  small breakout boards with XLR

>   * Access to GPIO Pins?

definitely

>   * Access to USB?

not sure about that. For most purposes i wouldn't use it because the USB
Port instability of the Raspi is legendary...

>   * Access to Network?

sure

>   * Anything else they haven't thought of?
> 
balanced inputs!  not sure if this works with the Raspberry but there
should be an I2S interface on the board somewhere...

It would also be ok to have seperate input and output boards because
most of the time i would need only one but not both on the same raspi.

> And now the awkward question, what price range would you be prepared to
> pay for something like this?
> 
something between 80 and 100 Euros would be ok for me/us.

regards
 christian
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Has anyone tried the Juli@ XTe is the PCIe audio card yet?

[Christian Pointner]

Hi,

Am 04.08.2015 um 21:02 schrieb Bill Putney:
 It looks pretty cool and the price is attractive (~$200). Has balanced
 analog IO and S/PDIF digital in and out. Says it is Compatible with
 Linux (ALSA) for what that's worth.
 
We use this card in one of our machines. It runs just fine under Debian
Wheezy. We don't use it for Rivendell but i don't think that there will
be a problem with that.

regards
 christian

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Web service test harnesses [WAS: Oh, this is weird: can't import audio]

[Christian Pointner]

Hi,

Am 2015-06-12 um 22:41 schrieb Rob Landry:
 On Fri, 12 Jun 2015, Christian Pointner wrote:
 Same for debian, you just need to add something like:

 snip
 . /lib/lsb/init-functions
 /snip
 
 At the beginning of your old initscript and everything will work as
 expected.
 
 Which script? Do you mean /etc/init.d/rivendell?
 
Yes.

regards
 christian
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Web service test harnesses [WAS: Oh, this is weird: can't import audio]

[Christian Pointner]

Hi,

Am 2015-06-12 um 17:43 schrieb Frederick Gleason:
 On Jun 12, 2015, at 11:16 43, Rob Landry 41001...@interpring.com wrote:
 Debian 8 won't start the Rivendell daemons at boot; it runs something called 
 systemd that seems to want to start everything at the same time instead of 
 in their proper order. 
 
This is a little too simplistic and not what systemd really does.

 This same ‘systemd’ misery is now included with RHEL 7 as well.  It 
 originated from Apple, where it has been part of OS X/Darwin for some time.  
 Mercifully though, on RHEL 7 the legacy service(8) commands still work (they 
 are merely wrappers that redirect to the appropriate systemctl(8) commands).
 
Same for debian, you just need to add something like:

snip
. /lib/lsb/init-functions
/snip

At the beginning of your old initscript and everything will work as
expected.

regards
 christian
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev