The superblock is located at the start of the last track on the drive. To apply the patch, CD into the directory with your pdcraid. The procedure that has worked for me is to calculate the offset of the start of the last track from logical CHS. That might be a pain. This may be lower than or equal to the offset actually chosen by the Promise controller based on the LBA capacity and track size reported.
|Date Added:||20 July 2010|
|File Size:||33.68 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Promise FastTrak TX Controller Review
Which means that if you want to boot from a Promise RAID volume, you need to use a customized initial ramdisk initrd to load the module before you can remount the root to the RAID volume.
No need for an initrd anymore.
Fortunately, the driver can be monolithized. You need to disable detection of any IDE controllers above your onboard integrated channels.
Ttx2000 apply the patch, CD into the directory with your pdcraid. This is done using a series of additional kernel parameters – e. Theoretically it should be enough to clean the MBR: The history of these drivers picked up some spin around 2. The key part of the patch is the single line containing the formula: Now it might be a bit of a problem to decide what this really means, fssttrak the logical CHS is bogus with modern drives and it may not match the total capacity reported by that same drive.
In Fadttrak, the controller is frequently referred to by the name of its chip: One of them was the Promise FastTrak TX that we’ve been selling as part of Windows machines for quite some time now, with positive response.
The situation described here pertains to the Linux kernel versions around 2.
This may be lower than or equal to the offset actually chosen by the Promise controller based on the LBA capacity and track size reported. The proprietary Promise driver is modular-only – probably due to the fact that it consists of an open-source wrapper and a binary-only library.
The superblock is located at the start of the last track on the drive. The drivers are only any good as a way to access a Windows partition from Linux. In my practical user experience, both ways provide a shaky solution that pretty much fails to deliver the traditional RAID advantages: The procedure that has worked for me is to calculate the offset of the start of the last track from logical CHS. I have corrected that bug, here’s a patch – I just hope that I got the formula right.
Also, if you wanted to re-use such a Promise-tainted drive in another Promise array, it might be a good idea to remove the old RAID superblock itself, to prevent the RAID controller its drivers, really from detecting the long defunct array.
That might be a pain.