Re: [RDD] Rivendell on CentOS 7
I don’t know if it’s available on CentOS, but the “mate” (pronounced “mahtay” as in “yerba mate”) desktop, which is available in Debian, is a fork of GNOME that attempts to reproduce the GNOME 2 user interface and still be compatible with newer systemd based init systems. I use it on several systems as my first choice GUI. Rick On Oct 14, 2015, at 2:37 PM, Frederick Gleason wrote: > On Oct 14, 2015, at 16:37 18, Rob Landry <41001...@interpring.com> wrote: > >> I find mention of a beta Appliance on Centos 7, but no mention of Rivendell >> 3.0. I fear I've missed a post. > > No Rivendell 3 at the moment. There is a (presently somewhat stalled) BA3, > for which I am currently evaluating alternative desktops (as I’ve come to the > conclusion that GNOME 3 is a complete and utter basket case). I’ve been > using it for a couple of months now as my default environment and it > *doesn’t* get any better. Quite the opposite actually. > > Stay tuned… > > Cheers! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell on CentOS 7
Ahhh… Sorry! I misinterpreted the “3” in > Broadcast Appliance 3 (based on CentOS 7) plays nice with UEFI and is > currently in final beta testing. If you'd like to try it, it's available at: > > http://www.paravelsystems.com/appliance/broadcast_appliance-DVD-3.7.0.BETA02-x86_64.iso Glad to hear you are working on a CentOS-7 version. Please keep us informed of your progress. Sorry for the noise! Rick On Oct 14, 2015, at 2:37 PM, Frederick Gleason wrote: > On Oct 14, 2015, at 16:37 18, Rob Landry <41001...@interpring.com> wrote: > >> I find mention of a beta Appliance on Centos 7, but no mention of Rivendell >> 3.0. I fear I've missed a post. > > No Rivendell 3 at the moment. There is a (presently somewhat stalled) BA3, > for which I am currently evaluating alternative desktops (as I’ve come to the > conclusion that GNOME 3 is a complete and utter basket case). I’ve been > using it for a couple of months now as my default environment and it > *doesn’t* get any better. Quite the opposite actually. > > Stay tuned… ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Rivendell to Optimod for RDS
Anyone talking to an Orban Optimod via telnet to put now and next info into tthe Optimod's RDS system? Do you have to use a script to resend the info more often that Rivendell sens it? all the best, drew -- http://nakedghosts.blogspot.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] GPIO Permissions
I wrote this for Debian 6 as a source install a few years ago but it still applies: http://rivendell.tryphon.org/wiki/Debian_6_GPIO_MC_PCIDIO24 On 2015-10-14 18:51, Cowboy wrote: On Wednesday 14 October 2015 01:33:42 pm Michael Barnes wrote: I check /dev/gpio0 and find the permissions only for root. By "only for root" I suspect you mean owner only, and it's owned by root ? Or do you mean owner and group root ? I suspect a udev rule, or something along those lines. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell on CentOS 7
On Oct 14, 2015, at 16:37 18, Rob Landry <41001...@interpring.com> wrote: > I find mention of a beta Appliance on Centos 7, but no mention of Rivendell > 3.0. I fear I've missed a post. No Rivendell 3 at the moment. There is a (presently somewhat stalled) BA3, for which I am currently evaluating alternative desktops (as I’ve come to the conclusion that GNOME 3 is a complete and utter basket case). I’ve been using it for a couple of months now as my default environment and it *doesn’t* get any better. Quite the opposite actually. Stay tuned… Cheers! |--| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |--| | A room without books is like a body without a soul. | | -- Cicero| |--| ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell on CentOS 7
I find mention of a beta Appliance on Centos 7, but no mention of Rivendell 3.0. I fear I've missed a post. Rob On Wed, 14 Oct 2015, Rick Thomas wrote: Rob, Search in the RDD list for the subject “Rivendell on CentOS 7 [WAS: Rivendell on Windows?]” Or anything recent from Fred Gleason. Rick On Oct 14, 2015, at 4:54 AM, Rob Landry <41001...@interpring.com> wrote: On Tue, 13 Oct 2015, Rick Thomas wrote: PS: Tomorrow I’m going to try the CentOS-7 based Rivendell 3 beta that Fred mentioned in another posting to this list. I’ll report back when I have some results. Is there a Rivendell 3.0 in the works? I must have missed that post. Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] GPIO Permissions
A chown command in the rc.local file worked. Thanks for your help. Michael On Wed, Oct 14, 2015 at 12:41 PM, Brian P. McGlynn wrote: > Michael, > > Put a command in /etc/rc.local that chown's and it will work each time on > reboot. > > Brian > > -- > Brian P. McGlynn > Sent from my iPhone > > > On Oct 14, 2015, at 13:33, Michael Barnes wrote: > > > > Setting up a new Rivendell box that has a Measurement Computing PCI > DIO-24 card installed. When I fire it up, I find that it doesn't read > contact closures. Using gpitest I get a popup box that says "Can't open > GPIO device." I check /dev/gpio0 and find the permissions only for root. I > chmod it to 777 and everything works fine. However, on rebooting the > machine, the permissions reset and the relay contacts don't work again. > > > > How do I permanently change the permissions so they stay in place after > a reboot? > > > > This is a CentOS 6 Appliance install. > > > > Thanks for your ideas. > > > > Michael > > > > ___ > > Rivendell-dev mailing list > > Rivendell-dev@lists.rivendellaudio.org > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell on CentOS 7
Rob, Search in the RDD list for the subject “Rivendell on CentOS 7 [WAS: Rivendell on Windows?]” Or anything recent from Fred Gleason. Rick On Oct 14, 2015, at 4:54 AM, Rob Landry <41001...@interpring.com> wrote: > > > On Tue, 13 Oct 2015, Rick Thomas wrote: > >> PS: Tomorrow I’m going to try the CentOS-7 based Rivendell 3 beta that Fred >> mentioned in another posting to this list. I’ll report back when I have >> some results. > > Is there a Rivendell 3.0 in the works? I must have missed that post. > > > Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] imminent HD failure from large rdimport
On Wednesday 14 October 2015 12:57:46 pm Tom Van Gorkom wrote: > But why after importing does the used memory stay high, Because it's not being requested by/for anything else. > and why did the CPU > keep working? Would a failing drive cause the CPU to keep trying to find > good sectors and good data to read? Until it times out, yes. > The disk isn't near full. Irrelevant. Myself, I'd be looking at the relocated counts in the S.M.A.R.T. data, or more importantly the relocations pending. Anything pending more than about zero is a really bad thing. -- Cowboy ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] GPIO Permissions
On Wednesday 14 October 2015 01:33:42 pm Michael Barnes wrote: > I check /dev/gpio0 and find the permissions only for root. By "only for root" I suspect you mean owner only, and it's owned by root ? Or do you mean owner and group root ? I suspect a udev rule, or something along those lines. -- Cowboy ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] GPIO Permissions
Michael, Put a command in /etc/rc.local that chown's and it will work each time on reboot. Brian -- Brian P. McGlynn Sent from my iPhone > On Oct 14, 2015, at 13:33, Michael Barnes wrote: > > Setting up a new Rivendell box that has a Measurement Computing PCI DIO-24 > card installed. When I fire it up, I find that it doesn't read contact > closures. Using gpitest I get a popup box that says "Can't open GPIO > device." I check /dev/gpio0 and find the permissions only for root. I chmod > it to 777 and everything works fine. However, on rebooting the machine, the > permissions reset and the relay contacts don't work again. > > How do I permanently change the permissions so they stay in place after a > reboot? > > This is a CentOS 6 Appliance install. > > Thanks for your ideas. > > Michael > > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] GPIO Permissions
Setting up a new Rivendell box that has a Measurement Computing PCI DIO-24 card installed. When I fire it up, I find that it doesn't read contact closures. Using gpitest I get a popup box that says "Can't open GPIO device." I check /dev/gpio0 and find the permissions only for root. I chmod it to 777 and everything works fine. However, on rebooting the machine, the permissions reset and the relay contacts don't work again. How do I permanently change the permissions so they stay in place after a reboot? This is a CentOS 6 Appliance install. Thanks for your ideas. Michael ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] imminent HD failure from large rdimport
On Wednesday 14 October 2015 12:20:59 pm Tom Van Gorkom wrote: > the disk utility gave the warning of an imminent hard drive > failure. It is a nearly new 4TB WD NAS rated drive. I don't care what the thing is "rated" for, speaking as a disk recovery guy, back it up RIGHT NOW !!! Don't call your mom. Don't go to the bathroom. Back up that drive immediately !! If it doesn't fail in the next hour or so, great, but it very well may. -- Cowboy ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] imminent HD failure from large rdimport
Disk utilities report 102 bad sectors and over 13k read error rate. I agree - better replace it quickly. But why after importing does the used memory stay high, and why did the CPU keep working? Would a failing drive cause the CPU to keep trying to find good sectors and good data to read? The disk isn't near full. Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 Rio Grande Bible Institute 4300 S US Hwy 281 Edinburg, TX 78539 On Wed, Oct 14, 2015 at 11:47 AM, Frederick Gleason < fr...@paravelsystems.com> wrote: > On Oct 14, 2015, at 12:20 59, Tom Van Gorkom > wrote: > > > We are finally to the point of moving all our audio files into the new > Rivendell system. I left it importing 1100 audio files last night (probably > 5 hrs) using rdimport and when I arrived this morning all imported fine > with the standby having copied them all but the HD light was continuously > lit on the master server and while I tried to see what was using all the > CPU and memory, the disk utility gave the warning of an imminent hard drive > failure. It is a nearly new 4TB WD NAS rated drive. The problem seems to be > that the 8GB of RAM loaded up to 95% and stuck there with the CPU running > continuously at about 50% on the master server. The RAM of the client from > which I ran the import also loaded up to 90% but its CPU was nearly idle. > The standby server had no issues. Rebooting cleared the RAM but the failure > warning remains. > > It’s completely normal to see +90% usage of RAM on a Linux box. That’s > because Linux aggressively caches file data (see the ‘buff/cache’ counter > in top(1)). It has nothing whatever to do with disc failure. > > > > Do I need to replace the HD or can I run repairs and be confident? > > I would backup my data and replace the drive. Immediately. > > Cheers! > > > |--| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |--| > | A room without books is like a body without a soul. | > | -- Cicero| > |--| > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] imminent HD failure from large rdimport
On Oct 14, 2015, at 12:20 59, Tom Van Gorkom wrote: > We are finally to the point of moving all our audio files into the new > Rivendell system. I left it importing 1100 audio files last night (probably 5 > hrs) using rdimport and when I arrived this morning all imported fine with > the standby having copied them all but the HD light was continuously lit on > the master server and while I tried to see what was using all the CPU and > memory, the disk utility gave the warning of an imminent hard drive failure. > It is a nearly new 4TB WD NAS rated drive. The problem seems to be that the > 8GB of RAM loaded up to 95% and stuck there with the CPU running continuously > at about 50% on the master server. The RAM of the client from which I ran the > import also loaded up to 90% but its CPU was nearly idle. The standby server > had no issues. Rebooting cleared the RAM but the failure warning remains. It’s completely normal to see +90% usage of RAM on a Linux box. That’s because Linux aggressively caches file data (see the ‘buff/cache’ counter in top(1)). It has nothing whatever to do with disc failure. > Do I need to replace the HD or can I run repairs and be confident? I would backup my data and replace the drive. Immediately. Cheers! |--| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |--| | A room without books is like a body without a soul. | | -- Cicero| |--| ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] imminent HD failure from large rdimport
Help! We are finally to the point of moving all our audio files into the new Rivendell system. I left it importing 1100 audio files last night (probably 5 hrs) using rdimport and when I arrived this morning all imported fine with the standby having copied them all but the HD light was continuously lit on the master server and while I tried to see what was using all the CPU and memory, the disk utility gave the warning of an imminent hard drive failure. It is a nearly new 4TB WD NAS rated drive. The problem seems to be that the 8GB of RAM loaded up to 95% and stuck there with the CPU running continuously at about 50% on the master server. The RAM of the client from which I ran the import also loaded up to 90% but its CPU was nearly idle. The standby server had no issues. Rebooting cleared the RAM but the failure warning remains. Do I need to change some mysql settings? I am using the provided my.cnf file. Do I need to replace the HD or can I run repairs and be confident? Thanks, Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 Rio Grande Bible Institute 4300 S US Hwy 281 Edinburg, TX 78539 ___ 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???
On Wednesday 14 October 2015 02:17:03 am Rick Thomas wrote: > 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? > Not that specifically, but I did install CentOS-6 on a 3TB drive recently using that same installer. It will do it just fine, but you have to do it as a custom, I forget what they call it, when choosing the disk and partition. Also be aware that the CentOS boot loader ( grub ) can't work with disks 2G or larger !! It will be necessary to create a much smaller ( say, 500MB ) boot partition to work around the grub bugs. Grub will tell you it installed fine, but will otherwise never boot. -- Cowboy http://cowboy.cwf1.com "I like being single. I'm always there when I need me." -- Art Leo ___ 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???
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???
On Tue, 13 Oct 2015, Rick Thomas wrote: PS: Tomorrow I’m going to try the CentOS-7 based Rivendell 3 beta that Fred mentioned in another posting to this list. I’ll report back when I have some results. Is there a Rivendell 3.0 in the works? I must have missed that post. Rob ___ 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???
Thanks, Christian… Your reply is very helpful! 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? 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? Thanks! Rick On Oct 14, 2015, at 1:24 AM, Christian Pointner wrote: > 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] Rivendell broadcast appliance installer 2.6.5.1 seems to be allergic to 3TB disk drives???
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] Rivendell broadcast appliance installer 2.6.5.1 seems to be allergic to 3TB disk drives???
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