Hardware question - UltraAta 133 PCI


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Hardware question - UltraAta 133 PCI
# 1  
Old 09-13-2008
Hardware question - UltraAta 133 PCI

Not sure I put this in the right forum, and if I was incorrect. I do a appligize.

Recently I have lost two external hard drives due to heat. I bought internal drives, seperate case's, and made them usb externals. They lasted a long time, but the heat killed them.

While rooting through my peaces and parts box, I found an siig ultra ata 133 pci card. I remember when I first tried to use this in FreeBSD(I think 5.?), it wasn't reconized. And I used in on some windblows systems.

Well, I'd like to try again to use it.

I currently am running FreeBSD 6.3 beta(?) and am ready to upgrade to 7.

Has anyone used this card before? If not, is there a pci card I can buy that will work with bsd?

Different question while I am at it. I also purchased some WD MyBook's awhile back that also did not work with FreeBSD. It would take somewhere like 10/15 minutes before the os would reconize them. Articles I found noted it had something to do with the drives not giving up their serial number or something along that lines. I also found that a patch had been created, but? I just found that article a couple days ago. Would anyone know if this patch had been incoporated into 7???? Id love to stop network backups to these drives and plug then directly into the bsd box for backups.

Lol, and I could as one more question about ntfs-3g???? If anyone had used it? But, I'm just going to install that port after the upgrade and try it.

drool
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Processor performance question [hardware]

A few of our machines need upgrading and we are looking into a selection of processors at present. There are suggestions on the vendor's websites that the L3 cache was specifically introduced for gamers. Is this true? Does having L1, L2 and/or L3 cache help at all in performance or are the... (0 Replies)
Discussion started by: figaro
0 Replies

2. AIX

Hardware upgrade question

I have an IBM pseries 7028-6E1 server with a six drive bay that is currently plugged into the scsi backplane of the motherboard. I am going to install a PCIX Ultra320 scsi raid adapter, and swing the drive bay over to it. I am just wondering how this is going to work. Should I power the server... (1 Reply)
Discussion started by: markper
1 Replies

3. UNIX for Dummies Questions & Answers

Hardware question

Folks; Is there a command to know if my hardware can run 64-bit or 32-bit? I'm trying to re-install SUSE 64-bit on one of our server but i'm not sure if this server hardware designed for 32-bit only or for both Any help? (14 Replies)
Discussion started by: Katkota
14 Replies

4. UNIX for Dummies Questions & Answers

Hardware question

I would like to use my sunblade to firewall the connections to my desktop and laptop, these at the minute are on a wifi router. What is the best solution? (0 Replies)
Discussion started by: Kawakaze
0 Replies

5. AIX

IBM Hardware question

I am looking to buy a 7044 - either a 170 or 270. From what I can find on web searchs the 170 is NOT upgradable to more that one CPU? Is that correct? Can I upgrade the planer on a 170 to a 270 to support multiple CPU's? Does anyone have any other suggestion for AIX hardware? (5 Replies)
Discussion started by: dizman67
5 Replies

6. UNIX for Dummies Questions & Answers

Light *nix system for 133 mhz?

I have an old pc, about 133-200 mhz with very little memory and hard-drive. I want to install a small and fast *nix system with ion or some other simple wm for maximal performance. It's supposed to be used as a desktop. If someone could share their experience with older machines and some... (2 Replies)
Discussion started by: riwa
2 Replies

7. Red Hat

S3 Savage KM 133

HI I have problem working with S3 Savage KM 133 Video Card on Redhat Linux 9 Enterprise Edition. It hangs up once probing done on Video Card.So i tried insalling Linux with options as to run the set up on 640*480. As knows case i searched the web forums to get help. Please let me know how can i... (0 Replies)
Discussion started by: prakashpichika
0 Replies

8. HP-UX

newbie question about hardware for HP-UX 11.i

I've been asked by my copmpany to scour the web for a computer on which we can run HP-UX 11.i --- Is there a certain architecture type that I need or will any Compaq HP computer be fine for running HP-UX 11.i ?? Thanks!! (3 Replies)
Discussion started by: jalburger
3 Replies

9. UNIX for Dummies Questions & Answers

Hardware question?

Does anyone know how to install a second Ethernet adapter on a Sun Sparc 10? (2 Replies)
Discussion started by: jskillet
2 Replies
Login or Register to Ask a Question
MOUNT_UDF(8)						    BSD System Manager's Manual 					      MOUNT_UDF(8)

NAME
mount_udf -- mount a UDF filesystem SYNOPSIS
mount_udf [-o options] [-s sessionStart] [-n lastRecordedLBA] [-b blockSize] [-p packetSizeInBlocks] [-v verificationPolicy] [-w] devicePath mountPath DESCRIPTION
The mount_udf command attaches the UDF filesystem residing on the device devicePath to the global filesystem namespace at the location indi- cated by mountPath. This command is normally executed by mount(8) at boot time. The options are as follows: -o options Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -v verificationPolicy This is an advanced option not useful for regular use. It controlls the verification policy when writing to RW type optical media. Its value can be "meta", "all", or "none". Policy "meta" means only the metadata are verified after they are written. This is the default policy. Policy "all" means to verify data written, which could be several times slower than policy "meta". Policy "none" does not verify any data. It is only slightly faster than "meta" in normal cases, but may result a corrupted UDF disc if the write of metadata fails. -s sessionStart This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the start Logical Block Address of the last session where UDF data structures (VRS and AVDP) resides. This value overrides the value obtained from the device. -n lastRecordedLBA This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the last recorded Logical Block Address where the UDF VAT ICB will be searched. This value overrides the value obtained from the device. -b blockSize This is an advanced option not useful for regular use. It specifies the block size in bytes used when mounting the UDF volume. This value overrides the value obtained from the device. -p packetSizeInBlocks This is an advanced option not useful for regular use. It specifies the packet size in blocks when manually mounting the UDF volume. This value overrides the value obtained from the device. -w This is an advanced option not useful for regular use. It forces to enable the experimental packet writing function on optical media that has not been fully supported, such as CD-R, CD-RW, DVD-R, DVD+R, HD DVD-R, and BD-R. Writing to these media does not work on some drives and may cause data corruption or data loss on some other drives. Therefore, this flag should be used only by file system developers when debugging the experimental write functions. The -s, -n, -b, and -p flags are not useful in normal use. They are mainly used for debugging and data recovery. Since the -s, -n, and -p flags are all specified in units of block size, when any of these flags are specified, it is strongly recommended that the -b flag is also specified. SEE ALSO
mount(2), unmount(2), fstab(5), mount(8) BUGS
Reading of all UDF revisions (1.02 - 2.60) on both block device (e.g., hard drives and USB drives) and most optical media is supported. Writing to block devices, DVD-RW and DVD+RW is supported with the following exceptions: (1) Cannot write Finder Info, Resource Fork, or other extended attributes in UDF volumes of revision 1.02 and 1.50; (2) Cannot write to mirrored metadata partition. HISTORY
The mount_udf utility first appeared in Mac OS X. 4th Berkeley Distribution December 6, 2006 4th Berkeley Distribution