Single drive in raid interface(solved)

Desire to utilize a raid connector for an IDE hard drive in my a7v333 mobo to provide a separate drive for my system.
Most descriptions allow for two drives to be utilized in raid configs.
My computer has a promise PDC20276 raid controller which can be set up prior to boot as a raid 0 array with a selection which permits a single device. However, even in windows, I have never been able to run a single device as I recall (ten years or more back when, in the last millenia!).
Please advise how to connect and use a single drive in the interface setup I have, as established in archlinux.
The mobo has two separate connectors provided for raid systems. I will use the blue connector for my single drive.
From that setup of a single drive, the computer boots into arch but I do not find the drive listed in K disk free.
What modules are necessary for this function?

try this utility : http://people.redhat.com/~heinzm/sw/dmraid/
the biggest problem with onboard ataraid/sataraid controllers under linux seems to be to find out what devices they create.
Also the promise fasttrak onboard raid controllers have much more in common with software raid solutions than with real hardware raid controllers like the adaptec scsi raid controllers.

Similar Messages

Panther server, move from single drive to RAID 1

Hello,
I am trying to find out if this can be done on a system (Xserve G3) with Panther server running on it. I know this is old, but right now the school will not upgrade the server.
It has the original 60GB hard drive and is running out of space. I would like to replace it with two 500GB HD's using software RAID.
In Panther, can you clone or CCC the OS and move it to a RAID1 from a single drive, or do we need to install and configure a new installation on the RAID set?
Any help would be greatly appreciated.
Mike

There were major changes in Disk format from 10.3 Panther to 10.4 Tiger, especially in RAID drives. I believe the 10.4 Server Installer converts your Boot RAID (if applicable) but does not deal with your data-only RAID drives. In the case you are proposing, the upgrade from 10.3 to 10.4 may require you to copy your data-only RAID drives yet again.
My older SCSI RAID drives which ran fine in 10.3 were not recognized as having a valid Driver (of any description) in 10.4. The old drives could not be mounted, and therefore could not be "promoted" to 10.4 RAID Drives. Luckily, RAID tools in 10.4 Tiger are much improved.
Using only one additional full-size drive, I was able to move the array to a spare Mac, install 10.3 to get them recognized, then Network-mount and copy them onto a single-member RAID array in 10.4 Server. Creating a single member of a Mirrored Array required some fancy command-line work in 10.4 Server.
The bottom line: If you can upgrade to 10.4 Server first, it will be much less work (and much less risk).

Seeking guidance on upgrading from single drive to RAID on XServe

Hi,
I'd be grateful for any guidance anyone can give me on upgrading my XServe to a RAID.
My 2GHz G5 XServe runs 10.3 and has a single 80GB drive. It's been running for 3 years providing mail, web sites (around 100) and around 10 java applications for that time without any trouble. However, I'd like to get it running on a mirrored RAID array (RAID1).
Is it possible to backup the existing disk to a FW drive. Insert a new disk, format the old and new disk as a RAID1 setup, then restore the previous OS setup, user, mail, web sites, applications etc?
I've got this server running very sweetly, it's extremely reliable but I'm worried about the disk failing.
I've read other posts here that have described trying to do this but that the old backup may overwrite low level RAID1 formatting upon restore. Any thoughts on how I can avoid that?
Kind Regards,
Chris.

Hi Chris
I’ve never done it that way because of the potential problems you describe. Perhaps some of the other guys have a way of making that method reliable. Seeing as you have an XServe why don’t you buy two drives instead of one? They are cheap enough nowadays. 2x250GB SATA drives should do.
I would target disk mode the server to a laptop for example and prep your RAID Mirror that way. Restore using DU or clone using CCCloner to the new RAID, restart and test. This way if you hit any problems you will still have a working server on your original drive. Plan on 40mins to an hour downtime.
Hope this helps – Tony

Boot Priority with Raid and Single Drives.

I thought I would share something that I discovered yesterday after struggling to get a Sata Raid array to play nicely with a single sata drive.
Sorry if this is already widely known but I couldn’t find any reference to it.
Setup:
MSI K8N Platinum SLI
2x 160GB Maxtor DM10 Raid0 Array (Windows)
1x 160GB Maxtor DM10 Single Drive (Backup)
The main issue I was having was no matter how I setup the array and what I set as the first boot device windows would always try to boot from the single drive.
The array was set to bootable when it was created, and it set to be the first device under the hard disk boot priority sub menu.
If I tried installing windows with the single drive plugged it would always be seen as C: drive and would copy the boot files here even if I selected D: (array) as install location.
If I tried unplugging the single drive and installing windows, it install and boot correctly from the array.
But as soon as I plugged the single drive back in windows would look for the boot files on it and tell me there was an error and no boot files could be found.
When looking through the bios I noticed a setting called “Extended IDE Drive”, this makes the drive appear as an IDE drive so that there is no need to install the sata driver F6 on install.
Once I set this to No/None the drive disappeared from the bios but after a reboot windows saw the drive correctly and allowed me to install windows to the array which was now correctly drive C:
Once windows was installed, the drive appears under the raid controller same as the array drives.
The drive is fully accessible and working natively with the sata drivers installed.

Quote from: jarvo on 30-January-07, 04:38:13
Yeah, not matter what the HDD order is winxp always tries to boot from the single drive when its plugged in.
Not sure if this only happens to me or if other people have had similar issues.
IDE drivers becomes automatically as 1st HDD. you need to switch them.
have you arranged hard disk boot priority? (not main priority)
have a try to push "F8" or "F11" during post to popup menu, and choice correct HDD to boot from there.

Can you combine the two sides of an Xserve RAID into a single drive?

I am looking to combine my Xserve sides into a single drive so that it will be more efficient for storing beyond hi-def video. I have an Xserve RAID with 14x750GB drives which format in RAID5 down to 4.09TB per side. I want to create a singe 8.18TB drive from these.
Is there an easy way to do it?

Thanks for the info William, I did backup a few important files before this happened, but I would like to get to a few more.
It happened when our IT guy was showing me how to create a new RAID set. He created a set while explaining a few things, then selected the new one he made, and deleted it. Right then, both sets disappeared and were deleted, the empty one he made, and the one we needed. I was watching him, and he didn't select both, just the empty one he'd made. So, I was hoping that there would be a work around just so that I could maybe use a data rescue utility to possibly pair the 2 together long enough for me to back up some files.
If anyone has any recommendations, please let me know.
thank you.

Cloning a single drive to a new RAID 1 set

Hi,
Can I clone a drive from a machine (that has dual controller, RAID 1 capability but, was not setup using it) to a new pair of hardware RAID 1 disks using method/software in the same machiine, now. I think the machine should have originally used it's hardware
RAID 1 capability but, for whatever reason wasn't and now, I would like to do that. Can I use Acronis or Ghost to clone the single drive to the new RAID 1 set?
Thanks.
gk

It is possible to create a mirror from an existing JBOD disk, however the ability to do this depends on the capabilities of the RAID controller. In my experience, this is something found on high-end controllers, of which I know exist but have not used.
There is a method using some 3ware cards where you have to take a disk image of the single disk. Then you import it into a mirror but the drive is erased. Then you can redeploy the disk image onto the mirror.
Of course there is a big problem you may encounter. You would only want to do this if the disk was originally on RAID JBOD. If the disk was originally on IDE or AHCI modes, going through this process would likely result in Windows STOP 0x7B on first boot
after being cloned to the mirror.
If the data is important on this disk, I would recommend not trying to put it into a mirror. Instead you can use Ghost (or similar) program to do a sector copy to a new disk. I typically recommend that the new disk be a different size from the old disk so
you can easily determine which is which.

K8tNEOFSR SINGLE DRIVE AND NO STUPID RAID?!!!!

Hi, I have 1 sata wd 160 gb drive on my pc (k8t neo FSR+ am 64+3000+1gig Kingston+RADEON9800PRO ) connected to the VIA VT8237 serial ata ( not promise, I don’t have that) everything works fine, the problem is that I cant disable RAID,. I want to use only one single drive as fast as I can.
but the RAID bios always appears on the screen when booting slowing things downn
( pressing F10 doesn’t help because I don’t have other drive) then windows starts loading.
How can I disable raid and keep one single sata drive functioning ? pata ( cd drive) and sata is enabled on bios One of the readme files mentions that there are 2 type of sata bios, one with raid and the other without it (6420NXXX.ROM) how can I install the new sata bios? Anybody knows a solution?
Thanks
Sorry for the lousy English

Hi
The screen you are seeing appears to be the VIA SATA drives screen, aslong as SATA are connected and enabled you will see this. It is setting up your satas,
CH_0 is the drive on SATA1, CH_1 is the SATA2 connector. Ignore the raid, it is a controller for the sata drive.
cheers
jocko

Raid 0 vs Single Drive

I have a Lumix GH4 and I'm starting to edit in 4k. I need a new thunderbolt drive and was wondering if Raid 0 is faster than a single drive. A LaCie 6T Big2 Raid vs LaCie D2 single drive. Both are the same price.
Thanks
Rob

Ian R. Brown wrote:
... I have no idea what sort of real life (eg. editing in FCP X) performance improvements I would see (or where) if I had a RAID and/or another 12GB RAM.
I'm VERY shy in any prediction and any 'number values' according that magic idol 'speed' ..
No, I don't link to my 4k-4x Multicam-on-a-Mini-stunt again , but in my humble opinion and observation, plain 'numbers' don't mirror the performances of FCPX! What I said before: any not-too-stuffed usb3 drive is more than fast enough to deliver a 4k-native-stream. The question is: is FCPX to display that stream? With all the bells&wistles related to it, waveforms, thumbnails, perhaps applied effects etc etc etc.
And, don't get tired to repeat that: What if the project contains multiple video-streams, compos (green screen, pip, ...), compounds, Multicam?
Then, the transfer-rate from one metal-box to the other is just one (weak) criteria.
I've read somewhere (sorry no link at hand), you'll notice a dramatic decline of performance, if a drive is close-to-full - which makes sense, when you visualize how data is handled on a spinning platter... (2015, and we rely on technique from turntables...). Or, imagine some 'super-fast' Pegasus - and just 2 tiny booms have to dance across the spinning driks, collecting bits for say 6 streams of video..
(pic source: http://news.bbc.co.uk/2/hi/technology/6677545.stm )
And I've read somewhere (should be fcp.co), that FCPX and Compressor do handle videos differently on task of 'conversion' ..
And there are many folks, who keep their Macs very busy, by indexing HDDs, loading updates, sharing to clouds, listening to streamed musuc etc etc etc.. then, more Ram = more better!
... summary:
drive-speed is a topic; but by far not the only one to create a 'snappy' FCPX experience!

Making two hard drives work or appear as a single drive

I have a G5 with two 500 GB internal drives. One I use to backup the first, however, now my drives are full and I would like to buy 1 TB external to back up the two internal drives but is there anyway to setup the second internal drive to work with the first like a single 1 TB drive instead of two 500GB drives? I'm not sure how I would use the second drive otherwise. I don't want to have to drag files to it every time I want to save something on it. How should I set it up? Any help would be greatly appreciated. Thanks.

Thanks for your help. I will have to research it a bit. I'm not 100% sure what a rAID is or how it works and with regard to the second comment on using the 500 GB as super duper backup...you may have misunderstood or maybe I wasn't clear. I won't have a 500 GB to use as any backup. I want my two internal 500 GB drives to be viewed as a single 1TB drive that can be backed up to a 1TB external drive. I just don't understand how to make my 2 500GB drives into one drive. I prefer not to split it up into application on one of the drives and user info on the other because I won't get the max space out of both. I have tons of photos, music, and video on my machine and little in the way of programs. Will a RAID make the two 500GB drives into a single drive?

How do I remove one failing hard drive from raid set and replace with new one

Last Friday apparently one of my raid drives started failing.
As I mentioned on this forum I started getting continous beeping.
I was finally able to get the raid working at a degraded level. I ordered a replacement hard drive which is arriving today.
(In the meantime I made twice daily backups of my work.....)
Below was the message I got from the browser based raid software:
Blahblah 09    1000.2GB   RaidSet Member SamSung HD103SJ
Blahblah 10    1000.2GB     Free                 SamSung HD103SJ
Blahblah 11    1000.2GB   RaidSet Member SamSung HD103SJ
Blahblah 12    1000.2GB   RaidSet Member SamSung HD103SJ
(See this earlier thread if you wish!)
http://forums.adobe.com/thread/727867?tstart=0
At one point when I did the checked the browser interface I saw the message Failed and Degraded
As I said, I was able to work over the weekend on the degraded system.
This morning I got the beeping again and did the rescue and now I am running a "full raid" without the notice that one raid was "Free".
In any case, the new hard drive is arriving today.
What steps should I take to incorporate the new drive into the raid system.
I have one OS drive
and 4 tb raid drives.   One needs to be replaced with the new one that I am getting today.
Thanks
Rowby

Harm,
Regarding your comment:
Re: How do I remove one failing hard drive from raid set and replace with new one
Please tell me how to read the serial number from an individual drive rather easily, without un-installing them:
If you select the proper drive to change out, you only need to remove one drive and look at its serial number...
Step 1: Identify bad drive serial number using Areca's tools
Step 2: Turn off the computer
Step 3: Remove what you think is the bad drive based on following your numbered cable method, marked hot-swap bays, whatever
Step 4: Verify that the serial number matches the "bad drive" serial number from step 1; if it does great, proceed; if it does not match, go back to step 3
Step 5: Change out the CORRECT drive - that's the bottom line for this whole procedure
Cheers,
Jim

Calling multiple smartforms in a single driver program.

Hi ,
Can anybody tell me how can I call multiple smartforms in a single driver program.
Each form has been assigned a output type.
Regards,
Sudha.V

Hi,
Here i have 2 smartforms assigned to different OUTPUT TYPES
Use this way
IF nast-kschl = 'FUCI' .
    ci_form = 'ZLAYOUT'.
ELSEIF nast-kschl = 'RD04'.
    ci_form = 'ZLAYOUT01'.
ENDIF.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname           = ci_form
    IMPORTING
      fm_name            = fnam
    EXCEPTIONS
      no_form            = 1
      no_function_module = 2
      OTHERS             = 3.
AFter this call the smartforms based on the output type
Please closeif solved,
Thanks,
Aditya
Edited by: aditya on May 21, 2008 6:15 PM

SATA raptor (single drive in RAID0) - HDTach jaggies?

I just reinstalled Windows and ran HDTach, hoping to remove the jagged peaks in my HDTach results. Here's what I get:
I followed the steps found in the RAID FAQ setup guides (F6 to install the RAID drivers, enabled SATA DMA, stripe is setup with 32k block size) and I have installed the 5.11 nVidia drivers. Is there any way I can make the graph smoother?
Specs:
K8N-Neo2 Platinum
1gb OCZ DDR3200
AMD Athlon 64 3500+
WD Raptor 74gb SATA in RAID0

Quote from: Built2Last on 22-March-06, 09:45:09
Chippy99, Just to eliminate the confusion: 1. the first post[hd tach pic] was nVidia RAID 0 stripe 2 x 80 Gig Seagate SATA II . the second post [hd tach pic] was nVidia non RAID 160 Gig Seagate SATA II . 3. the third post was same as first post except using hd tune instead.
syar2003, What is optimum stripe size [block] for this RAID config? TIA
I have the same exact drive as that, and its absolutely not capable of a burst speed over 300mb/sec in single drive. That hdtach result shows it exceeding the SATAII standard by about 25%. Mine bursts for about 248mb/s and average read for 62mb/s just about half of what you have there. This evening when I get home from work I will post my HDTach and HDTune results in single drive, then I will build a Dual drive Raid 0 array using 2 of these and post the results as well.
In the even that HDTach is not fubar in anyway, where is this firmware you speak of? That Seagate drive beats a single raptor easily and comes close to beating a Raid 0 dual Raptor 130gig setup. Can you run HDTune on that single 160gb Seagate?

RAID Interface Mappings with RocketRaid 2310 (rr2310_00) fail in .37

EDIT: This post was originally titled:
RAID Interface Mappings (Hard {Challenge?} Question) [with edit]
It has since been changed because further investigation found it to be a completely different problem... Go figure.
Also, this post is tightly coupled with another post (link further down in the comments).
Greetings...
Alright. So I'm not new to Linux to say the least, but I swear every time I have to deal with udev and related tasks something goes funky.
So, here's the issue:
I have a RocketRAID 2310 raid adaptor (made by HighPoint) that has a RAID5 configured using four 750 GiB drives. (of 8 in the machine)
The machine dual boots both Windows and Linux, and that is the main source of the issue. It appears as thought he Linux drivers and the Windows drivers, while both functional, are not designed to be intermixed... Which I suppose from a server perspective is a perfectly reasonable limitation, even if frustrating. Anyway, I digress...
I've been working with this card for years now, accepting the limitation that I could only access it from Windows. Today, though, I made an interesting discovery. I was reconfiguring some devices and noticed something strange about the fdisk output:
Disk /dev/sde: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 4294967295 2147483647+ ee GPT
Disk /dev/sdf: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0x0046b51b
Disk /dev/sdf doesn't contain a valid partition table
Disk /dev/sdg: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0xac7a1898
Disk /dev/sdg doesn't contain a valid partition table
Disk /dev/sdh: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0xac3cad83
Disk /dev/sdh doesn't contain a valid partition table
The four drives showing up as individual drives is completely normal per my experience with this card... What's new since installing Arch is the GPT partition table detected on the first drive, and more importantly, the sectors! For those that didn't catch that, let me highlight:
Disk /dev/sde: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
/dev/sde1 1 4294967295 2147483647+ ee GPT
Yeah... Goes to a sector about three times the max. Also known as the raid partition! Huh, would you look at that. Sadly, udev doesn't catch it, and there is no /dev/sde1 partition.
Now there are two posibilities here as far as I can tell:
First, that somehow the entire GPT partition table is smaller then the striping block size of the RAID5, and that fdisk manages to read it entirely off the first disk in the raid. Striping is set at 64k I think, so it's possible, but seems a stretch...
Second, that the raid is being detected, but udev is missing it and something funny is happening with the device/partition mappings.
Now I would love to experiment to find out what is going on here, but the raid contains critical data (that, although backed up to tape, is still something I don't want to have to restore! Rebuilding the array takes 5 hours minimum, then restoring from tape is likely another 10... 15 hours downtime is not an option). What this means is that all tests on it have to be NON-DESTRUCTIVE, read only operations. To complicate matters (just because things can't be that easy), the contents of the RAID5 is a partition level TrueCrypt volume, so no easy way to determine the contents based off of partition identifiers.
I tried using parted, but sadly it coughs up a lung and aborts all operations when it sees a partition boundry outside the scope of the disk (as is the case here). Seriously, it won't even try. Wimp...
So that's where I am. Mistery partition that only fdisk can see. If I could get a file handle to it, I could try to get TrueCrypt to decrypt it to find out if it's a striping artifact or not.
Aside:
I suppose this question also links to another, more generic question: Given a 'file' (which could be any *nix file handle) that contains a valid partition table and partitions (say a dd if=/dev/sda of=/home/user/device.bak), how does one go about accessing it's partitions? Are there udev tricks, or some other method? Edit 1a: I know how loopback mounting works, but that doesn't expose the partitions within because it doesn't flag a uevent for the udev daemon to respond to... Not sure how to manually tell it to process /dev/loop0 and look for partitions (supposedly splitting it up into /dev/loop0p1, /dev/loop0p2, etc.)
Additional notes:
- I am not sure what device driver is being used for those four drives to be visible... It's not rr2310 (the HighPoint RAID driver), but I know the card uses a resold chipset (maybe Marvel?), so it could be detected by a number of other kernel drivers. lsmod doesn't have anything useful there. Is there maybe a way to determine what device file is associated with what driver module?... So many good questions. Too many for one post!
- The RAID BIOS config is a useless piece of junk. It loads into memory too early in the BIOS operations on this board, and thus runs into a race condition for detecting it's own hardware. 90%+ of the time it will list no drives detected, but continue booting and everything is there just fine. It conflicts with the AMI (Megatrends) BIOS, but not with similar Pheonix based ones on similar boards (which detect the drives and raid properly every boot)... For those thinking of RAID cards for their servers, don't grab HighPoint! I've since stayed clear, but this server has a long life expectency, so I'm having to live with it.
So there we have it! Hit me, Arch Forums, with your best theories or hacks!
Edit 1b:
I was recently reconfiguring two other drives in another computer to use a RAID0 array and didn't bother wiping them before initialising the array... Normally I wouldn't have even bothered checking, but today I felt curious. The RAID0 was striped with 64k blocks, same as the above mentioned RAID5... And low and behold, the new RAID0 array had the old partition table of one of the original drives. What this proves is that the striping of a RAID array (and I know that a rundundant array of independent disks array is redundant... ) can leave a partition table intact and readable. That makes the first option seem more probable...
Last edited by SeanM (2011-02-22 20:05:48)

Hi, I downloaded your last package, and adapted for the 232x model, using the rr232x-linux-src-v1.10-090716-0928.tar.gz from RR.
I'm not an expert in pkg building, but after some reading I considered myself enough armed, ... I thought so (sic)
So I did replace all strings related to the model and the package version in the install, PKGBUILD and patches. It patches fine except the Makefile.def that is rejected. I hope you could share some light in that issue.
Currently, the kernel is 3.1.2-1-ARCH, so might that be the problem?
that is rr232x.install
# This is a default template for a post-install scriptlet. You can
# remove any functions you don't need (and this header).
KERNEL_VERSION=`uname -r`
# arg 1: the new package version
pre_install() {
/bin/true
# arg 1: the new package version
post_install() {
depmod -v $KERNEL_VERSION > /dev/null 2>&1
/bin/cat <<EOF
==> To use this module, sata_mv has to be unloaded or the kernel will panic
==> To unload sata_mv, please do
==>
==> # rmmod sata_mv
==>
==> as root before loading rr232x
==>
==> If you want to use this module permanently, you should blacklist
==> sata_mv by adding 'blacklist sata_mv' to /etc/modprobe.d/modprobe.conf
EOF
# arg 1: the new package version
# arg 2: the old package version
post_upgrade() {
post_install
# arg 1: the old package version
post_remove() {
depmod -v $KERNEL_VERSION > /dev/null 2>&1
the modded PKGBUILD
# Maintainer: count-corrupt <corrupt at giggedy dot de>
pkgname=rr232x
pkgver=1.10
pkgrel=1
pkgdesc="Kernel modules for Highpoint RocketRAID 230x and 231x SATA cards. Patched for use with kernel26 =2.6.37, >=2.6.38 and kernel >= 3 (a.k.a. linux)"
arch=('i686' 'x86_64')
url="http://www.highpoint-tech.com/USA/bios_rr2320.htm"
license=('custom')
groups=()
if [[ `uname -r` == 2.6.* ]]; then
depends=('kernel26')
else
depends=('linux')
fi
makedepends=()
provides=()
conflicts=()
replaces=()
backup=()
options=()
install=$pkgname.install
source=( http://www.highpoint-tech.cn/BIOS_Driver/rr232x/Linux/new%20format/rr232x-linux-src-v1.10-090716-0928.tar.gz scsi_lck.patch kernel3.patch)
noextract=()
md5sums=()
#_kernver=`uname -r`
_kernver=`uname -r`
build() {
mkdir -p $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/scsi/
# Apply the scsi lock patch to make the driver work with kernel26 > 2.6.37
cd $startdir
patch -p0 -i $startdir/scsi_lck.patch
patch -p0 -i $startdir/kernel3.patch
cd $startdir/src/rr232x-linux-src-v$pkgver/product/rr232x/linux/
make KERNELDIR=/usr/src/linux-$_kernver || return 1
# Install the kernel module
install -m 644 -D rr2320_00.ko $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/scsi/
mkdir -p $startdir/pkg/usr/share/licenses/$pkgname
cp $startdir/src/rr232x-linux-src-v$pkgver/README $startdir/pkg/usr/share/licenses/$pkgname/
patches kernel3.patch and scsi_lck.patch are modded accordingly.
To avoid dependencies,
makepkg -i --skipinteg
so I get those results ...
┌─17:40 joan@WS01 ~/src/rr232x_mod
└─>>> makepkg -i --skipinteg
==> S'està fent el paquet: rr232x 1.10-1 (dv nov 25 17:44:16 CET 2011)
==> Comprovant les dependències en temps d'execució ...
==> Comprovant de dependències per l'assemblatge ...
==> S'estan recuperant les fonts...
-> S'ha trobat rr232x-linux-src-v1.10-090716-0928.tar.gz
-> S'ha trobat scsi_lck.patch
-> S'ha trobat kernel3.patch
==> AVÍS: S'està ometent la comprovació de la integritat.
==> S'està extraient el codi font...
-> S'està extraient rr232x-linux-src-v1.10-090716-0928.tar.gz amb bsdtar
==> S'està eliminant el directori pkg/ existent...
==> S'està entrant en l'entorn fakeroot...
==> Iniciant build()...
patching file src/rr232x-linux-src-v1.10/osm/linux/os_linux.c
patching file src/rr232x-linux-src-v1.10/osm/linux/osm_linux.c
patching file src/rr232x-linux-src-v1.10/osm/linux/osm_linux.h
patching file src/rr232x-linux-src-v1.10/inc/linux/Makefile.def
Hunk #1 FAILED at 74.
Hunk #2 FAILED at 119.
2 out of 2 hunks FAILED -- saving rejects to file src/rr232x-linux-src-v1.10/inc/linux/Makefile.def.rej
==> ERROR: S'ha produït un error en build().
S'està cancel·lant...
so I guess the scsi_lck.patch is fine, and the issue must be in the adressing of the kernel version.
the rejected Makefile
--- src/rr232x-linux-src-v1.10/inc/linux/Makefile.def.orig 2011-08-13 10:13:37.000000000 +0200
+++ src/rr232x-linux-src-v1.10/inc/linux/Makefile.def 2011-08-13 11:15:53.000000000 +0200
@@ -74,19 +74,39 @@
KERNELDIR := /lib/modules/$(shell uname -r)/build
endif
-KERNEL_VER := 2.$(shell expr `grep LINUX_VERSION_CODE $(KERNELDIR)/include/linux/version.h | cut -d\ -f3` / 256 % 256)
+KERNEL_MAJ_VER := $(shell expr `grep LINUX_VERSION_CODE /usr/src/$(uname -r)/include/linux/version.h | cut -d\ -f3` / 65536 % 65536)
+
+KERNEL_VER := $(KERNEL_MAJ_VER).$(shell expr `grep LINUX_VERSION_CODE $(KERNELDIR)/include/linux/version.h | cut -d\ -f3` / 256 % 256)
ifeq ($(KERNEL_VER),)
$(error Cannot find kernel version. Check $(KERNELDIR)/include/linux/version.h.)
endif
+
ifneq ($(KERNEL_VER), 2.6)
ifneq ($(KERNEL_VER), 2.4)
-$(error Only kernel 2.4/2.6 is supported but you use $(KERNEL_VER))
+ifneq ($(KERNEL_MAJ_VER), 3)
+$(error Only kernel 2.4/2.6/3 is supported but you use $(KERNEL_VER))
endif
endif
+endif
+
+ifeq ($(KERNEL_VER), 2.4)
+
+HPT_LIB := $(HPT_LIB)-regparm0
+_TARGETMODS := $(addprefix $(HPT_LIB)/,$(TARGETMODS))
+
+VPATH := .. $(HPT_ROOT)/osm/linux
+TARGET := $(TARGETNAME).o
+
+C_INCLUDES += -I$(HPT_ROOT)/osm/linux -I$(KERNELDIR)/include -I$(KERNELDIR)/drivers/scsi
+
+$(TARGET): $(TARGETOBJS) $(_TARGETMODS)
+ @echo $(if $V,,[LD] $@)
+ $(if $V,,@)$(CROSS_COMPILE)$(LD) -r -o $@ $^
+
-ifeq ($(KERNEL_VER), 2.6)
+else # for kernel >= 2.6
TARGET := $(TARGETNAME).ko
@@ -119,20 +139,6 @@
@echo '$$(addprefix $$(obj)/,$$(TARGETMODS)): $$(obj)/%.o: $$(HPT_LIB)/%.o' >>$@
@echo ' @cp -f $$< $$@' >>$@
-else # for kernel 2.4 modules
-HPT_LIB := $(HPT_LIB)-regparm0
-_TARGETMODS := $(addprefix $(HPT_LIB)/,$(TARGETMODS))
-VPATH := .. $(HPT_ROOT)/osm/linux
-TARGET := $(TARGETNAME).o
-C_INCLUDES += -I$(HPT_ROOT)/osm/linux -I$(KERNELDIR)/include -I$(KERNELDIR)/drivers/scsi
-$(TARGET): $(TARGETOBJS) $(_TARGETMODS)
- @echo $(if $V,,[LD] $@)
- $(if $V,,@)$(CROSS_COMPILE)$(LD) -r -o $@ $^
endif # KERNEL_VER
endif # KMOD
Had tried already several days without success, and I'm runnin' out of ideas, so I ask for some guidance to find back the path.
Thanks in advance
Last edited by ga01f4733 (2011-11-25 17:27:13)

DIY Fusion Drive and RAID 5

Hi everyone!
I have spent several hours by reading various forums but haven’t found any definitive answers.
I have a 12 Core Mac Pro with the following setup: one 1TB SATA hard drive that carries the system and applications. For the files and storage there are three 2TB SATA drives in RAID 5 controlled by Apple RAID card. I am going to install a 512 GB Samsung 840 Pro SSD drive in the optical bay and have initially planned to use it just for the system and applications, but am curious if the following is possible.
1) Is it possible to combine the RAID 5 array with the SSD and create a Fusion drive?
2) If yes, will it retain all the features of the RAID 5?
3) Should TRIM be enabled?
Thank you in advance!

TRIM directly addresses the shortcomings of having only garbage collection available. SSD controller manufacturers and designers (including SandForce, the controller manufacturer for OWC's SSDs), recommends that TRIM be used with their products. So does Samsung.
For example, here's a 2011 article from OWC describing how you don't need TRIM on their SSDs and how it can in fact hurt performance or reliability.
That article has been discussed here on MacInTouch before. In my opinion it's bad advice, and inaccurate in some of its assertions. It also ignores the recommendation made by SandForce to use TRIM with their SSD controllers. But even if one were to take that article at face value, applying that advice to SSDs other than OWC's makes little sense.
The reason I'm advising against TRIM is simply that it's yet another driver-level modification of the OS, and these always carry potential risk (as all the folks with WD hard drives who lost data can attest to).
Apples and oranges comparison, for a variety of reasons. The short of it is that TRIM is supported natively in all recent versions of OS X. The tools used to enable it for third party SSDs do not add a new kernel extension; they change the setting to allow Apple's native TRIM implementation to be used with SSDs other than those factory installed by Apple.
This shows that the 840s do work slightly better with TRIM than without, but the differences are (in my opinion) trivial, a 9% increase at best.
One of the major reasons for the skepticism that exists about TRIM is that so many people, the authors of both articles you linked to included, don't understand it.
TRIM is not, strictly speaking, a performance-enhancement technology -- though it is plainly obvious that most people think it is.
Though it can, in many circumstances, improve performance, there are also circumstances under which it will provide little or no noticeable benefit. Not coincidentally, a new SSD tested fresh out of the factory packaging is unlikely to show much (if any) benefit. Or rather, TRIM is providing a real benefit for new SSDs, but that benefit doesn't become measurable in terms of benchmark performance testing until every memory cell in the SSD -- including many gigabytes of cells hidden from visibility by the SSD controller -- have been written to at least once. Writing 128 GB of files to an SSD with a nominal capacity of 128 GB won't do it, as there are several gigabytes (exact number varies depending on the model) still unwritten.
Under real-world use conditions, having TRIM disabled means eventually having noticeable write performance degradation due to write amplification. It is far greater than "9%" -- it can be a 50% or greater drop in write performance, depending on various factors. Defining "eventually" is difficult because it depends on how the SSD is used. But given enough time and write cycles, it can happen to all SSDs used without TRIM, no matter how sophisticated their garbage collection algorithms are.
Under those same real-world use conditions, having TRIM enabled means that the SSD should almost never reach a state of having noticeable write performance degradation, as it should almost never get into a state where write amplification is happening.
I will concede that it is possible to design a lab test in such a way as to defeat the benefits provided by TRIM, but such tests do not reflect any real-world usage scenario I can imagine. Furthermore, those same contrived tests would put an un-TRIMmed drive into an equally-addled state even more quickly.
I would suggest reading through the rather lengthy previous discussions about TRIM. Here are a couple of my past posts that are most relevant to the current discussion:
A description of what TRIM is here.
I addressed some of OWC Larry's comments about TRIM use with OWC/SandForce SSDs here.
http://www.macintouch.com/readerreports/harddrives/index.html#d09dec2013

My MacBook Air won't turn on? I have to dropped it but earlier in the day I got a notification about a full single drive. I have tried the ideas in the communities but its still not working, help!

My MacBook Air won't turn on? I have to dropped it but earlier in the day I got a notification about a full single drive. I have tried the ideas in the communities but its still not working, help!

See this article:
http://support.apple.com/kb/ht3964
Find the section that applies to your computer, and follow the instructions.
Shut down the computer.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.
Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.

Single drive in raid interface(solved)

Similar Messages

Maybe you are looking for