Partitions on raid-array not recognized on boot

Hey there,
I already had my share of problems with my raid setup and kernel/udev updates, but this one is new:
I have a raid1 setup with several partitions on the array which get recognized as /dev/md0p1, /dev/md0p2, etc.
My root-device is on /dev/md0p2 by the way.
After the last kernel-update I get dropped in the rescue shell at boot because the message "waiting 10 seconds for device /dev/md0p2" timed out. In the rescue shell I can see, that indeed the array is properly assembled (cat /proc/mdstat) is fine, but somehow the corresponding partitions (md0p1, sda1, sdb2, etc) are not linked in /dev or recognized at all (/proc/partitions).
However one execution of "blkid" seems to trigger some udev-event and afterwards all partitions and links magically appeared.
Has anyone any idea what causes this behaviour and how to fix it? It would be very enlightening to know which part of my system is actually responsible for setting up the partition-links (udev?).

Sorry guys, I've been inundated with problems lately.
Anyway, to answer your questions, yes I've swapped out everything.
As it stands right now, I have green lights on everything both sides even show up on IP and in ARD. The only issue now is that I can't see half of my RAID in DiskUtilities from my Xserve. I can format one side and not the other.
My server is an older G5 single 2GHz, build 7W98 and 2.5GB memory, (for reference).
Thank you for your input. I appreciate it.
DaveB

Similar Messages

Unable to add partition on raid array, device or resource busy.

Greetings,
I want to be able to create a disk image of a software raid of one of my arch box.
I'm able to create my image with G4U successfully. I'm also able to restore my image without error on my new box.
When my system boot up, I make sure that my raid array are up by doing cat /proc/mdstat.
I can see that md1 and md2 are 2 of 2 and active raid 1. But, when I look at md0 this is what I got:
md0 : active raid1 sdb3[1]
6289344 blocks [2/1] [_/U]
I try to add the partition sda3 to md0 array with this command:
mdadm --manage /dev/md0 --add /dev/sda3
The output of this command give me this :
mdadm: Cannot open /dev/sda3: Device or resource busy.
It seems that this error only occurs on /dev/md0 (/) array. I'm 100% sure that both, my image and my drive (vmware hdd) are good.
This is my partition table:
/dev/sda1 /dev/sdb1 = /boot (md1) 100MB
/dev/sda2 /dev/sdb2 = swap (md2) 2048MB
/dev/sda3 /dev/sdb3 = / (md0) 8GB
I have also tried the image creation with Acronis... same error.

I solved my issue.
My menu.lst was wrong..
kernel /kernel26 root=/dev/md0 ro
I should add this to my menu.lst:
kernel /kernel26 root=/dev/md0 ro md=0,/dev/sda3,/dev/sdb3
Now it work.
I followed the archlinux raid guide who's telling this:
Nowadays (2009.02), with the mdadm hook in the initrd it it no longer necessary to add kernel parameters concerning the RAID array(s).
Which is wrong because my distro is 2009.02, if someone can add a note to the wiki it can be usefull.
Thanks for your support

PM8M2-V RAID array not recognised by WinXP Pro

Greetings,
i'm just setting up a PM8M2-V system with 2 x WD 80GB JD SATA drives. In the RAID BIOS i have configured the drives to be RAID 0 (striped) for performance and made them bootable. From a IDE DVD rom, i'm running a WinXP Pro (corp ed - no pre-installed service packs) install but the OS will not detect any drives in the system.
I have downloaded the VIA_RAID_OM74.zip file from MSI VIA PIDE-SATA RAID Drivers and Utility for creating the RAID drivers and tried to create a floppy disk with the WinXP drivers on it using the embedded (and slightly cryptic) VIA MakeDisk.txt instructions.
Containined on the floppy disk are the following files/folders:
a:\TXTSETUP.OEM
a:\PIDE\WinXP\viapdisk.cat
a:\PIDE\WinXP\viapdisk.sys
a:\PIDE\WinXP\viapide.inf
a:\RAID\WinXP\viamraid.cat
a:\RAID\WinXP\viamraid.inf
a:\RAID\WinXP\viamraid.sys
*plus the other MS operating system files in the similar directory structure*
Problem - WinXP Pro does not recognise this created floppy disk as a hardware support disk and will NOT let the OS recognise the SATA RAID array as a drive.
Complete system specs
MSI PM8M2-V VIA P4800 + 8237R (RAID)
Intel P3 3ghz HT LGA775 CPU
2 x 512 DDR-RAM PC3200
2 x WD 80GB JD SATA drives configured in a RAID 0 Striped set and bootable
1 x IDE DVD D/L Burner (Master drive on IDE Secondary Channel)
ATI Radeon 9250 128m AGP Card
Web Excel 56K software modem

Did you boot with WinXP CD 1st and then hit F6 to install the RAID controller drivers?

My DVD drive is now not recognized in boot camp.

I just found the Matshita DVD-R UJ-898 is no longer recognized in Boot Camp Win 7. Tried uninstalling in Device Manager but the driver fails to load upon restart and also fails when trying to update. The DVD drive works fine in OSX Lion so I know the drive is ok. It worked fine when I first installed Windows 7 in Boot camp last year. This is an early 2011 macbook Pro 17 with Lion. All updates have been installed. Hadn't used the drive in Win 7 for a long time so not sure when it ceased to work.

Found the solution. Microsoft Fix-It found and made the driver repairs automatically.

T40: Pointing device not recogniced after booting

The pointing device is sometimes not recogniced right after booting. The error message says: activate the pointing device by the bios setting. But in the bios section it is always set to automatic as welll as in the IBM system setup. The error occurs only randomly.
Might be something wrong with the bios? Any experience?? Battery problem?
Thanks!
Martin

Yes, it is the Cisco "b" wireless card and here's the driver:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42683
Make sure to follow the instructions on the download page, since the actual process has two steps before the driver is fully installed.
Hope this helps.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

New harddrive not recognized after boot

Hi,
I just got a new (never been used) Western Digital Green 4TB hard drive today, but it doesn't seem to be recognized by the OS after booting. In the BIOS it is recognized, but as having ~2TB of storage instead of 4TB. During booting I get this message a few times: "ata9: softreset failed (device not ready)". This causes booting to take around 30 seconds longer than usual and the drive makes some strange beeping noises while this is happening. Eventually the message stops printing, and the beeping stops, and the OS finishes booting, but the drive is not recognized at all.
Did I get sent a defective drive?
My motherboard is a z77 Sabertooth that I purchased in the summer of 2012. Is there a certain SATA port I need to use for a drive this big? Could it be that the drive is not getting enough power to spin up? I noticed that the drive has some extra pins that none of my other hard drives have, like in the left side of this image http://techreport.com/r.x/wd-red-4tb/straight.jpg. Am I supposed to plug anything into those?
Last edited by tylerpnn (2015-03-17 15:58:31)

The pins are for jumpers.
Try different SATA cables, SATA ports, and power connectors. If behaviour doesn't change you probably have a bad drive.

Trying to boot from an external hard drive - drive not recognized at boot

I am trying to upgrade my Operating system. I am going from Mac OS 10.4.11 to Mac OS 10.6.
Hardware:
Model Name:
MacBook Pro 15"
Model Identifier:
MacBookPro1,1
Processor Name:
Intel Core Duo
Processor Speed:
2.16 GHz
Number Of Processors:
1
Total Number Of Cores:
2
L2 Cache (per processor):
2 MB
Memory:
2 GB
Bus Speed:
667 MHz
To backup my existing environment I bought Seagate Free Agent GoFlex 500GB for PC and Mac. USB 3.0 but backward comaptible to USB 2.0 which is what my laptop is. The system requirements included support for 10.4.11. I attached the drive to my lap top and used disk utility to format to Mac Extended OS (journaled). It recognized the drive immediately.
I used SuperDuper 2.6.4 to copy all files to the external drive. It seemed to copy just fine. It said it made the drive bootable. TO test it, I shutdown the system and started it back up with the option key pressed, but it only gave me my original HD as a choice to boot from. When the system came up, it didn't recognize the external drive. I unplugged the drive and re attached it and it seemed to recognize it, I trued to reboot again and it doesn't recognize the hard drive on reboot. Only when I un attach and reattach it.
Any ideas?
Thanks in advance.

I haven't forgotten, it just takes forever to get to a result when backing up an entire system.
So here's what I did. I agree with this idea:
Limnos wrote:
mac-sales.com I mentioned above is the OWC Ogelthorpe uses.
I suspect StartupDisk is seeing a nicely mounted drive connected in a bootable interface (USB) with all the needed files (palced there by SuperDuper). However, what it doesn't know if that drive isn't really accessible until the computer has properly booted because the chipset doesn't work without full system support. This is not at all unusual in external drives. Many years ago you really has to insist upon having an Oxford chipset in an enclosure to guarantee booting, but for general backup use any chipset was fine.
I had an old Lacie drive I have used for file backups over the years:
Disk:
Name :
LaCie Group SA
Type :
Disk
Disk Identifier :
disk1
Media Name :
WDC WD80 0BB-00JHC0 Media
Media Type :
Generic
Connection Bus :
FireWire
Connection Type :
External
Connection ID :
58629628097197639
Partition Type :
GUID_partition_scheme
Device Tree :
/PCI0@0/PCIB@1E/FRWR@3/node@d04b560c0bf647/sbp-2@c000/@0:0
Writable :
Yes
Ejectable :
Yes
Mac OS 9 Drivers Installed :
No
Location :
External
Total Capacity :
74.5 GB (80,026,361,856 Bytes)
S.M.A.R.T. Status :
Not Supported
Disk Number :
1
Partition Number :
0
Name :
Macintosh HD
Type :
Volume
Disk Identifier :
disk1s2
Mount Point :
/Volumes/Macintosh HD 1
File System :
Mac OS Extended (Journaled)
Connection Bus :
FireWire
Partition Type :
Apple_HFS
Device Tree :
/PCI0@0/PCIB@1E/FRWR@3/node@d04b560c0bf647/sbp-2@c000/@0:2
Writable :
Yes
Universal Unique Identifier :
438A4768-6F2C-3A0A-96A3-AEF60B7B8815
Capacity :
44.5 GB (47,768,887,296 Bytes)
Free Space :
4.2 GB (4,464,005,120 Bytes)
Used :
40.3 GB (43,304,882,176 Bytes)
Number of Files :
432,903
Number of Folders :
97,585
Owners Enabled :
No
Can Turn Owners Off :
Yes
Can Be Formatted :
Yes
Bootable :
Yes
Supports Journaling :
Yes
Journaled :
Yes
S.M.A.R.T. Status :
Not Supported
Disk Number :
1
Partition Number :
2
I moved everything from the Lacie to the SEaget - at least is it will be useful for something!
Erased the Lacie, partitioned it to 2 partitions.
Formnatted the partition GUID as suggested. I had named the partition for the backup something cutre like 10.4.11 OS clone.
Used Disk Utility>Restore to backup/clone the environment.
During the backup, it renamed the partition Macintosh HD, which was encouraging. After waiting a very long time for the backup, I was able to try to test booting from it and received many diagnostic errors including permission type errors, some of the files in /etc did not beloing to root. I have a couple of things I am going to try but thought I'd throw it out here since you guys have kept me pointed in the right direction.
Any more ideas as to why the drive won' t boot? Did I not give the partition enough space? Is it the chipset thing?

Why in my new internal hard drive not recognized by boot disk?

My OS HD died and I am replacing it with a Seagate 500 GB, 7200rpm 6gb/s drive. I am booting from snow leopard disk on my dual core, Intel 3 GHz 2007 Mac pro. the set up wind sees my other data disks (internal HD2 with my data, and two external fire wire drives but not the new disk. I want to load the OS onto the new disk...that was my goal. Any ideas?

Most brand new drives out of the box appear as "Unformatted" or Windows formatted. If you want to place Mac OS X on a drive, you need to erase it and create a GUID partition Map and a Mac OS X Extended, journaled Volume. (It is not difficult, those are the defaults).

CD/DVD not recognized when booted in OS 9

Hi,
I have a PB G4 667 titanium (the gigabite ethernet model) that can boot into OS 9. I normally run OS 10.4.5. I recently re-installed OS 9.2.2 using a generic install disk (not the one that came with this specific model). It boots fine into OS 9, but it will not recognize CD's or DVD's or some extensions, like Apple DVD player (which says it is missing a .lib file.
I also had a new upgraded SuperDrive (MCE Technologies) before I had to re-install OS 9. I didn't try to run OS 9 and see if the drive worked after it was installed, so I don't know if that might be the problem. I tried to load the driver into the extension folder, but there was no folder called "Supporting Authoring files" like the read me text said there should be for OS 9.
Any suggestions as to how to get OS 9 to recognize my CD/DVD's?
PB G4 Ti 667 Gig-Ethernet Mac OS X (10.4.5) I boot into OS 9 on occasion
PB G4 Ti 667 Gig-Ethernet Mac OS X (10.4.5) I boot into OS 9 on occasion

HI, marbot61. It sounds to me as though the problem is not that discs aren't recognized, but that your drive itself is not supported by your OS 9 installation — and perhaps it isn't supported in OS 9, period. Call MCE and ask for help setting OS 9 up to support the drive.
If you used a model-specific OS 9 installer disk that came with some other Mac, rather than a retail OS 9.2.1 disc (white, with a big gold 9 on its label) or the installer disk that originally came with your Powerbook, that may be the problem. It may be essential for you to use the disk that was shipped with the Tibook to install OS 9 on it. You should never expect to get a functional OS 9 installation from an installer disk that is specific to any model other than the one you're installing it on, and MCE will be justified in telling you they can't support your drive until you have a proper OS 9 installation on the Powerbook.

Why does raid array not mount?

Set-up: (Equipment was Purchased NEW July 2004)
Xserve: running OSX Server version: 10.3.9
Xserve Raid Box with both arrays using Raid-5:
Array One has Five 250GB ADM (this side works and mounts fine-NO Problems)
Array Two has Four 250GB ADM (this side DOES NOT mount) Our name for this Array/volume is: "RAID2RIGHTSIDE"
We've been using both sides (array 1 & 2) for years with no trouble. Sever locked-up last week and was shut-down, since then Array Two will not mount.
Currently I have all normal green lights (front and back of Xserve Raid Unit)
Disk Utillites 10.4.4: We can see the Array Two from within DU, though the name of the volume is gray/dimmed
Raid-Admin version 1.5.1: shows Array Two IS ON-LINE (all green lights too)
Things I tried-MULTIPLE Times
-Shut-down Xserve & Xserve Raid Unit and disconnect power and Batteries, waited more than 10-mins
-Verified and Repaired Array Two using Disk Utilities version 10.4.4
-Xserve Raid Unit: Removed all cables, Batteries, Power supplies, Fiber Boards, and other board in back
-Xserve Raid Unit: Removed and reset ADMs
-Vacummed dust - all of above
Any ideas why Array Two (RAID2RIGHTSIDE) will not mount? Your suggestions are appreiciated.
Thank you for reading this.
Pictures below

Finder, Preferences: General and Sidebar.

[SOLVED (mysteriously)] Arch on USB not recognized during boot

Hi there,
I hope, someone can help me with my problem, I have been searching and trying different things for quite some time now, without success.
I treated myself a new Notebook, Acer Aspire S7 and wanted to run Arch on it. However I am new to Linux and want to try it out on an USB-Stick, to keep the factory install of Win8 intact. (Also, this notebook does not have such a great HDD capacity) Additionally I want to have full disk encryption.
So I followed the Beginner's Guide with modifications described here and here
When it came to install the bootloader I chose Grub for EFI.
I then removed the USB-Stick with the live-Arch, which I used for installation and rebooted and it worked!
However: As soon as I completely shut down and boot again, the USB-Stick with my installation is no longer recognized. If i boot the live-Arch again, reinstall Grub and then reboot, it again works.
Here is something, I found strange. This is the output of efibootmgr:
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001,0003,0002,2002,2003
Boot0000* USB HDD: KingstonDataTraveler 2.0
Boot0001* Intel HDD0
Boot0002* Windows Boot Manager
Boot0003* arch_grub
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
BootCurrent is 0000, but that number does not appear in the Boot-Order list. Could that be something?
Well, I hope someone has an idea. I will happily share any information about my setup with you, just ask.
Thanks,
Max
Last edited by MaxT (2014-04-07 08:35:20)

Sorry for digging that threat up again. I just wanted to share with you the solution to the problem I was having. Perhaps it will save someone else some frustration.
The Acer Aspire S7 has a dongle that goes in the display port and provides an ethernet and an VGA port. It was that dongle that prevented the USB stick with the Arch installation from being recognized. Done attached -> USB stick was ignored, dongle detached -> it worked.
I have no idea, why that is the case, but maybe this info is helpful for someone.
Cheers,
Max

Hard Drive not recognized when booting from XP CD on docking station

The hard drive on my X60 failed to the point where I couldn't recover and reinstall the image. I have backups of all my data and a docking station so I didn't sweat it. Bought a new drive and installed it and this is when the trouble began.
I created an XP CD with SP2 slipstreamed in to make sure I have the latest drivers. I boot from XP CD and everything works until I try to install Windows. According to the installation CD there is no drive installed!
I reinstalled the drive to make sure and this time I booted off of Ubuntu Linux which installed flawlessly. That leads me to believe that there is a driver problem with Windows.
I need help! I would like to install Windows on the machine but nothing I've tried works.

edgardo wrote:
According to the installation CD there is no drive installed!
Standard Microsoft XP SP2 does not come with any SATA device drivers.
You have two options:
Go into the T60 BIOS and switch the SATA controller mode away from AHCI to "IDE" mode (or pehaps its "legacy" or "compatibility" mode - I forget what specific term is used in a ThinkPad BIOS).
Find the SATA device driver for XP (it's probably in the Intel Chipset driver download) on the Lenovo X60 support web site, download it and install it using the additional driver installation option which is offered right at the start of an XP install.
If you chose option 1, remember to switch the SATA controller back to AHCI mode in the BIOS after you have installed the SATA device driver.
Cheers,
Bill
Message Edited by billbolton on 03-09-2008 02:11 PM
I don't work for Lenovo

Windows .iso 7 will not load Boot Camp. The disk is not recognized by Boot Camp.

Boot Camp also does not reconize XP on disk but, guess that the new version of Maverick does not support it. If anyone knows otherwise please post.

You should visit the Boot Camp forum and read the Boot Camp help manuals.
https://discussions.apple.com/community/windows_software/boot_camp
http://www.apple.com/support/bootcamp/

[SOLVED] Source Architectures Arrays not recognized by makepkg

Hello,
I am in the process of updating my PKGBUILD's in order to migrate them to AUR4.
As suggested here, one should rework a PKGBUILD in order to not use bash conditionals regarding source architecture selection.
On my system (x86_64 architecture) - after reworking my package PKGBUILD script - on issuing 'makepkg --source' the system does not take into account neither the source_x86_64 or md5sums_x86_64 arrays; the i686 source/md5sums arrays are always selected:
# Maintainer: Frontier (frontier314 at gmail dot com)
pkgname=jaspersoftstudio
_pkgname=JaspersoftStudio
_binname="Jaspersoft Studio"
pkgver=6.1.0
pkgrel=1
pkgdesc="Eclipse based Jasper Reports generator"
arch=('i686' 'x86_64')
url="http://community.jaspersoft.com/project/jaspersoft-studio"
license=('Eclipse')
depends=('java-runtime' 'gtk2')
source_x86_64=("http://sourceforge.net/projects/jasperstudio/files/JaspersoftStudio-${pkgver}/TIBCOJaspersoftStudio-${pkgver}.final-linux-x86_64.tgz")
source=("http://sourceforge.net/projects/jasperstudio/files/JaspersoftStudio-${pkgver}/TIBCOJaspersoftStudio-${pkgver}.final-linux-x86.tgz")
md5sums_x86_64=('01e1da5e396a07b82dbc0cd20be437de')
md5sums=('2e6710b79c96f2f21880640fe8176048')
package() {
install -d -m 0755 ${pkgdir}/opt/${pkgname}
cp -a ${srcdir}/TIBCOJaspersoftStudio-${pkgver}.final/* ${pkgdir}/opt/${pkgname}
install -d -m 0755 ${pkgdir}/usr/bin
ln -sf "/opt/${_pkgname}/${_binname}" ${pkgdir}/usr/bin/${_pkgname}
ln -sf "/opt/${_pkgname}/${_binname}" ${pkgdir}/usr/bin/${pkgname}
cat > ${_pkgname}.desktop << EoF
[Desktop Entry]
Version=${pkgver}
Encoding=UTF-8
Name=Jaspersoft Studio
Comment=${pkgdesc}
Exec=GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc /opt/${_pkgname}/${_binname}
Icon=/opt/${_pkgname}/icon.xpm
Terminal=false
Type=Application
Categories=Java;Development;
EoF
install -D -m 0644 ${srcdir}/${_pkgname}.desktop ${pkgdir}/usr/share/applications/${_pkgname}.desktop
Both makepkg.conf and pacman.conf have the correct architecture setting (snippets):
makepkg.conf
# ARCHITECTURE, COMPILE FLAGS
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
pacman.conf
Architecture = x86_64
Can someone explain to me what I am doing wrong here?
Many thanks in advance.
Last edited by Frontier (2015-06-09 05:30:07)

Scimmia wrote:The PKGBUILD posted is wrong, it will use both x86.tgz and x86_64.tgz files. I you tried something else, post it.
Nothing more than Raynman and WorMzy suggested; using architecture-specific source arrays.
The updated PKGBUILD:
# Maintainer: Frontier (frontier314 at gmail dot com)
pkgname=jaspersoftstudio
_pkgname=JaspersoftStudio
_binname="Jaspersoft Studio"
pkgver=6.1.0
pkgrel=1
pkgdesc="Eclipse based Jasper Reports generator"
arch=('i686' 'x86_64')
url="http://community.jaspersoft.com/project/jaspersoft-studio"
license=('Eclipse')
depends=('java-runtime' 'gtk2')
source_x86_64=("http://sourceforge.net/projects/jasperstudio/files/JaspersoftStudio-${pkgver}/TIBCOJaspersoftStudio-${pkgver}.final-linux-x86_64.tgz")
source_i686=("http://sourceforge.net/projects/jasperstudio/files/JaspersoftStudio-${pkgver}/TIBCOJaspersoftStudio-${pkgver}.final-linux-x86.tgz")
md5sums_x86_64=('01e1da5e396a07b82dbc0cd20be437de')
md5sums_i686=('2e6710b79c96f2f21880640fe8176048')
package() {
install -d -m 0755 ${pkgdir}/opt/${pkgname}
cp -a ${srcdir}/TIBCOJaspersoftStudio-${pkgver}.final/* ${pkgdir}/opt/${pkgname}
install -d -m 0755 ${pkgdir}/usr/bin
ln -sf "/opt/${_pkgname}/${_binname}" ${pkgdir}/usr/bin/${_pkgname}
ln -sf "/opt/${_pkgname}/${_binname}" ${pkgdir}/usr/bin/${pkgname}
cat > ${_pkgname}.desktop << EoF
[Desktop Entry]
Version=${pkgver}
Encoding=UTF-8
Name=Jaspersoft Studio
Comment=${pkgdesc}
Exec=GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc /opt/${_pkgname}/${_binname}
Icon=/opt/${_pkgname}/icon.xpm
Terminal=false
Type=Application
Categories=Java;Development;
EoF
install -D -m 0644 ${srcdir}/${_pkgname}.desktop ${pkgdir}/usr/share/applications/${_pkgname}.desktop
Now, when you say
on issuing 'makepkg --source' the system does not take into account neither the source_x86_64 or md5sums_x86_64 arrays
What exactly do you mean? Where are you looking to see if it's taken into account?
On the previous version of the PKGBUILD (still available on the "old" AUR3.5), I've used bash conditionals to check for the correct binary package download:
# Maintainer: Frontier (frontier314 at gmail dot com)
pkgname=jaspersoftstudio
_pkgname=JaspersoftStudio
_binname="Jaspersoft Studio"
pkgver=6.1.0
pkgrel=1
pkgdesc="Eclipse based Jasper Reports generator"
arch=('i686' 'x86_64')
url="http://community.jaspersoft.com/project/jaspersoft-studio"
license=('Eclipse')
depends=('java-runtime' 'gtk2')
if [ "$CARCH" = "i686" ]; then
source=("http://sourceforge.net/projects/jasperstudio/files/JaspersoftStudio-${pkgver}/TIBCOJaspersoftStudio-${pkgver}.final-linux-x86.tgz")
md5sums=('2e6710b79c96f2f21880640fe8176048')
fi
if [ "$CARCH" = "x86_64" ]; then
source=("http://sourceforge.net/projects/jasperstudio/files/JaspersoftStudio-${pkgver}/TIBCOJaspersoftStudio-${pkgver}.final-linux-x86_64.tgz")
md5sums=('01e1da5e396a07b82dbc0cd20be437de')
fi
package() {
install -d -m 0755 ${pkgdir}/opt/${pkgname}
cp -a ${srcdir}/TIBCOJaspersoftStudio-${pkgver}.final/* ${pkgdir}/opt/${pkgname}
install -d -m 0755 ${pkgdir}/usr/bin
ln -sf "/opt/${_pkgname}/${_binname}" ${pkgdir}/usr/bin/${_pkgname}
ln -sf "/opt/${_pkgname}/${_binname}" ${pkgdir}/usr/bin/${pkgname}
cat > ${_pkgname}.desktop << EoF
[Desktop Entry]
Version=${pkgver}
Encoding=UTF-8
Name=Jaspersoft Studio
Comment=${pkgdesc}
Exec=GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc /opt/${_pkgname}/${_binname}
Icon=/opt/${_pkgname}/icon.xpm
Terminal=false
Type=Application
Categories=Java;Development;
EoF
install -D -m 0644 ${srcdir}/${_pkgname}.desktop ${pkgdir}/usr/share/applications/${_pkgname}.desktop
Testing THIS PKGBUILD with namcap produces no warnings, where testing the updated PKGBUILD produces warnings for the source_* arrays (probably namcap isn't updated to 'understand' architecture array strings).
Also with the old PKGBUILD when issuing makepkg --source, due to the bash conditionals, one could 'see' (from the shell messages) that the correct source package was downloaded. Now, when issuing the same command on the new PKGBUILD it downloads the i686 source always; however, issuing makepkg (without --source) downloads the correct source (in my case x86_64).
Last edited by Frontier (2015-06-09 06:02:02)

New hard drive in, not recognized when boot from DVD

Well, I installed my new Seagate ST3750640AS, 750 GB Baracuda and when I boot from the Tiger install DVD, there is no Hard Drive listed. What could have gone wrong. I have an early model G5 iMac.

Are you sure the cable is connected? Look at the [DIY|http://www.apple.com/support/manuals/imac> for replacing your drive and see if there's anything you may have missed.

Partitions on raid-array not recognized on boot

Similar Messages

Maybe you are looking for