On Aug 16, 2012, at 2:58 PM, Gregg Wonderly <[email protected]> wrote: > The ramdisk image contains the drivers that are available at boot time. If > you are not booting off of that array, then modules in the OS build should be > available, and should be queried and/or loaded to activate that device based > on the OSes and module management boot sequences. > > If you open a shell window, what does the following command produce? > > dmesg | grep 'sd[a-z]' > > If you want to go with LVM, I can provide you assistance in doing that, it is > really not hard. Before using the below > script, post your output back here and lets make sure we understand which > disks are being recognized/used for which function. > > Basically, it goes like this: > > for each disk in the array, do something like the following, where DISK_CHAR > is one of the letters (besides 'a' if that is your boot drive) > > Put this text into a file named makearray, and then you can do > > sh makearray b c d e > > for example, to make an LVM array out of those disks, striped, with out any > error recovery. Pay attention to which device letters you are using here, > and note that this script provides defaults if you don't provide any > arguments! > I crafted this just now, but it should work for 6 scsi resolved SATA/SCSI > disks beyond the first disk (the /dev/sda) disk. > > #!/bin/bash > lst= > drives=${*:-"b c d e f g"} > for DISK_CHAR in ${drives} > do > lvm pvcreate /dev/sd${DISK_CHAR} > lst="${lst} /dev/sd${DISK_CHAR}" > done > > # with all the drive names for the volume group > lvm vgcreate vg_riven_store ${lst} > > # now create the mountable volume > lvm lvcreate --name lv_varsnd --size NNNNg vg_riven_store > > with these commands you'll get an array. However, if you lose one disk, the > whole pool is gone. As was suggested, using ZFS would be a better choice, > even if you just build ZFS for your centos appliance, and then create your > snd pool with it instead.
I should of followed on after this with the other two commands you'll need. You can create a filesystem on the logical volume using the following. Specify the filesystem type that you want, if not ext4. mkfs -t ext4 /dev/mapper/vg_riven_store/lv_varsnd and then you'll need to mount it on /var/snd or wherever you need it to appear. Simply doing mount /dev/mapper/vg_riven_store/lv_varsnd /var/snd will do the trick from the command line. But you'll want to put something in /etc/fstab at some point too. Gregg Wonderly > On Aug 16, 2012, at 1:45 PM, Nathan Steele <[email protected]> > wrote: > >> I don't disagree, and am running a networked setup now but I am using >> older servers with SCSI drives and as such have six 74Gb scsi drives to >> put in this one, which will replace our current server(which will be >> switched to backup duty. I have /var/snd, mysql, and the CAE running on >> the server, airplay runs on a seperate machine, and production on a >> seperate machine with its CAE local. I like the thought of not having >> the audio leave the server for playout to air. the longer term plan is >> to replace all the machines with newer (SATA) hardware, but we are a >> non-comm that is just going on air so we need money coming in first. the >> curent servers were ones I had in my personal server lab not being used >> for anything important. long story short I just need this one to work >> for maybe the next 6 months... >> >> Nathaniel C. Steele >> Assistant Chief Engineer/Technical Director >> WTRM-FM / TheCrossFM >> >> On 8/16/2012 2:32 PM, Bill Putney wrote: >>> One way to go is to forget about running Rivendell on the /var/snd file >>> system computer. If you need that much storage, set up a computer with BSD >>> or Solaris X86 and build a ZFS store to put your /var/snd on. Offer it as >>> an NFS share and after you get your simple/tiny disk Broadcast Appliance >>> built, mount /var/snd from the NFS share. >>> >>> You'll have all the advantages of a high reliability, flexible and easy to >>> administer file server which can have lots of cooling fans (since it >>> doesn't have to be in the studio) and you'll have a simplified Rivendell >>> installation that can be put on a quiet, low power small foot print >>> computer in the studio. >>> >>> A lot of places put the MySQL server on the separate machine but I think >>> it's easiest to just let the BA disk install put that on the playout >>> station. You can't hardly buy drives smaller than 320 GB these days and >>> you only need about 10% of that for a full Rivendell installation if the >>> audio storage is somewhere else. >>> >>> Bill Putney - KPTZ Port Townsend, WA >>> >>> Sent from my iPad >>> >>> On Aug 16, 2012, at 10:27 AM, Nathan Steele <[email protected]> >>> wrote: >>> >>>> Not really a Rivendell problem.... >>>> >>>> Dell poweredge 2850 with Perc4/dc raid controller, broadcast appliance >>>> install doesn't see the disk...any idea how to fix this? I have six disk >>>> setup in a raid 5 ready to go. >>>> >>>> I can take out the raid card but don't know how to setup the software >>>> raid, and I have to use raid to get enough space for my /var/snd..... >>>> >>>> >>>> Thanks >>>> >>>> -- >>>> Nathaniel C. Steele >>>> Assistant Chief Engineer/Technical Director >>>> WTRM-FM / TheCrossFM >>>> >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> [email protected] >>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>> >>> >>> >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
