Tyan S2735-8M Maximum Hard Drive Limit/Not Working/Doesn't work with 1TB 1000GB hard drives

I never saved any of the logs, but basically no matter what OS (Linux) I used, I could not get my 1000GB hard drive to work (Seagate SATA).  The BIOS recognizes the drive and fdisk -l shows the hard drive as it should.

The tricky thing is that different OS's will give you different results, but don't be fooled.  You can't use these larger drives for long.  I was getting all kinds of seek/IO errors and also messages that the port could not be read.

In one custom kernel I had, what would happen is that after attempting to format a 900GB partition, the whole drive became invisible and inaccessible to the kernel (if you attempt to format a smaller amount it might work, but make no mistake it will be unstable and the symptoms I describe will invetiably happen at some point and fortunately I discovered it before putting these into production again).  An fdisk -l would only show the 500GB drive and not the 1000GB drive.  Updating the BIOS to Tyan's latest did not help either.

In Centos 5.3 the symptoms I had were the same messages, but a worse effect.  After the I/O errors it caused both SATA ports to become unusable at that point, so you couldn't run any command on your server until you reboot.  I'm sure this is a limitation of the BIOS or SATA chipset and I don't see any work around, this is either a BIOS or SATA chipset issue and I doubt Tyan has any plans for an update (considering the last update was in 2005). I hope this saves someone else the trouble, hassle and headache.

I know for sure 500GB Seagate drives work, since this is what I have in them.  I'm not sure if 750GB would work since I don't have any of those drives around.

Latest Articles

  • Openvz Quick Install for CentOS 5 Tutorial
  • Subnet Mask Lengths / Quick Reference
  • Linux How To Add/Delete A Default Route/Gateway
  • DRBD WFConnection Problem/Solution
  • How not to change an IP address in CPanel during a migration
  • CPanel Cannot Login Internal Server Error Could not fetch uid or gid for : root https://192.168.1.42:2083
  • sed script to automatically update IPs in named/BIND and httpd/Apache
  • mdadm Linux Software RAID QuickStart Guide
  • HeartBeat Error/High Load heartbeat: [7120]: WARN: Gmain_timeout_dispatch: Dispatch function for retransmit request took too long to execute: 20 ms (> 10 ms) (GSource: 0x926b390)
  • VirtualBox Error Failed to start the virtual machine Centos 5.5 Mirror. Medium '/home/testuser/.VirtualBox/HardDisks/Centos 5.5 Mirror.vdi' is not accessible. UUID {a1a9fad7-0402-4867-b8f3-39fb49454bc5} of the medium '/home/testuser/.VirtualBox/HardD
  • Installing Virtualbox on Centos 5.5
  • Openvz Live Migration Error - Error: undump failed: Invalid argument Restoring failed: Error: iptables-restore exited with 2 Error: Most probably some iptables modules are not loaded Error: rst_restore_net: -22
  • OpenOffice Writer Default Paragraph Annoyance
  • DirectAdmin Install Webalizer Stats
  • Ubuntu Linux HTML Rendering left bracket < problem appears as 003C box
  • Solution - error while loading shared libraries: libgd.so.2: cannot open shared object file: No such file or directory
  • Linux Kernel Boot Black Screen of Death Freeze/Halt Solution
  • Linux Kernel Freeze/Hang during boot on io scheduler cfq registered (default)
  • VirtualBox/VBOX Centos 5.5 Installation Kernel Freeze Problem "NET: Registered protocol family 2" And Solution
  • VirtualBox OSE/VBOX Can't Access Shared Folder Solution