Seagate 1.5TB (1500gb) $149

[TexasGrillChef]

MicroCenter in Dallas (Microcenter.com)

Now has Seagate Baracuda 1.5TB (1500gb) drives on sale for $149 each.

I am using one on my S3 NOW.... It works like a charm! :)

I also installed 4 on my Promise NS4300 NAS (Raid 5) 4167gb formated!

TGC

P.S. They are OEM Bare Drives. Not in a retail boxed package. Same warranty though. 5 Years.

[[NG]Owner]

Link. (http://www.microcenter.com/single_product_results.phtml?product_id=0298834)

[NG]Owner

[jlib]

Are you using it internally or externally with your S3 and are you getting full capacity? When they first came out there were some reports of problems with TiVo. Is your drive a newer one?

I love the $1/GB $0.10/GB ratio that seems to be the current standard now.

[TexasGrillChef]

Are you using it internally or externally with your S3 and are you getting full capacity? When they first came out there were some reports of problems with TiVo. Is your drive a newer one?

I love the $1/GB ratio that seems to be the current standard now.

I am using it as a eSATA drive on my ORIGINAL TiVo S3. The internal is still the original 250gb drive.

TiVo is reporting 231 HD Hours. Not for sure how new it is. Just bought it 2 weeks ago. Along with 5 more (6 Total). 4 for my NAS, 1 for the TiVo and 1 for my Popcorn Hour.

TGC

[Welshdog]

Newegg has it for less + free ship:

$129.99 (http://www.newegg.com/Product/Product.aspx?Item=N82E16822148337)

[jmpage2]

I was under the impression that the Linux kernel in the Tivo software could not address all of the disc space on drives larger than 1TB.

[bigpatky]

Are you using it internally or externally with your S3 and are you getting full capacity? When they first came out there were some reports of problems with TiVo. Is your drive a newer one?

I love the $1/GB ratio that seems to be the current standard now.

that $1/GB ratio is a tad off. i think you mean 10 cents/gb.

[TexasGrillChef]

I was under the impression that the Linux kernel in the Tivo software could not address all of the disc space on drives larger than 1TB.

Shhhhhhhh... Don't tell me TiVo PLEASE!

TGC

[ciper]

Perhaps something has changed but according to this thread http://mfslive.org/forums/viewtopic.php?f=11&t=257&st=0&sk=t&sd=a&start=30#p4484 the drive may be too large.


I am dying to know the maximum A drive size, and B drive size for the TivoHD (which should be more than the S3)

[mr.unnatural]

CompUSA had these for $119.99 over the weekend (Black Friday deal?). If you ordered two of them and paid via PayPal you could get another $20 back. Mine are being delivered on Friday.:p

[jlib]

Perhaps something has changed but according to this thread http://mfslive.org/forums/viewtopic.php?f=11&t=257&st=0&sk=t&sd=a&start=30#p4484 the drive may be too large.

I am dying to know the maximum A drive size, and B drive size for the TivoHD (which should be more than the S3)The problems seem to be with those users trying to boot from the drive. Maybe using it as an external eSATA drive overcomes those limitations? We definitely need more reports of eSATA use. TexasGrillChef's total hours report seems to be what one would expect so I am taking that as a credible report of success (at least as eSATA on an S3). The next time I need a computer drive I will get one and try it first with my S3.

Also, the early Seagate 1.5s had generic problems that affected many computers so that might have been part of the problem in the early reports. Supposedly, a new firmware update fixed current drives.

TexasGrillChef, do you have suggestions turned on? Curious if any problems if it is filled.

[Jonathan_S]

I was under the impression that the Linux kernel in the Tivo software could not address all of the disc space on drives larger than 1TB.As I understand it it's a partition size limitation, not a total drive size limitation.

But I never figured out how a 1.5tb drive got partitioned if you tell WinMFS to set it up as an external drive. Assuming it breaks it into partitions that are individually smaller than the magic number it should work fine.

[ciper]

As I understand it it's a partition size limitation, not a total drive size limitation.
The problems seem to be with those users trying to boot from the drive. Maybe using it as an external eSATA drive overcomes those limitations? .

That sounds plausible. So it would seem that the A drive maxes out at ~1.25TB while the B drive could potentially be significantly larger?

[lrhorer]

I was under the impression that the Linux kernel in the Tivo software could not address all of the disc space on drives larger than 1TB.
'Not even. The kernel is perfectly capable of addressing whatever size drive one might throw at it. The MFS file system on the S3 is 48 bit, which limits it to 2.2 TB. The MFS file system on the THD is 64 bit, so it has no such limit. It's not entirely clear yet why there were some problems with drives larger than 1.1TB, but it was thought it might a bug in MFS Tools and the way it partitions drives. I haven't visited the site recently, so I don't know the current status of handling large drives under MFS Tools.

[ciper]

'Not even. The kernel is perfectly capable of addressing whatever size drive one might throw at it. The MFS file system on the S3 is 48 bit, which limits it to 2.2 TB. The MFS file system on the THD is 64 bit, so it has no such limit. It's not entirely clear yet why there were some problems with drives larger than 1.1TB, but it was thought it might a bug in MFS Tools and the way it partitions drives. I haven't visited the site recently, so I don't know the current status of handling large drives under MFS Tools.
The kernel has pieces that are 32 bit and without a patch will not work with partitions larger than 1TB. Look at DDB/forum/showthread.php?p=299520#post299520

[mr.unnatural]

From what I've read in other forums, the 1.5TB Seagate suffered from a firmware glitch that didn't allow it to play nice in Linux or Mac OS, particularly when used in a multi-drive configuration or RAID array. A quick call to tech support will get you a download to flash the firmware. I still haven't heard if this allows it to be used in a Tivo so if you've got one with the latest firmware, give it a shot and let us know how it goes.

Here's the skinny on the drives that are affected and the correct firmware versions to be applied:

ST31500341A drives with part numbers of 9JU138-301 should be updated to CC1H.

Drives with part numbers of 9JU138 -300 and -336 should be updated to SD1A.

[ciper]

In case anyone cares the narrowed down list of hard drive limitations in a Tivo can be found here
http://mfslive.org/forums/viewtopic.php?f=11&t=257&start=45

1. You can have only 16 partitons per drive.
2. 128 character device names in the superheader devlist.
3. 1 TiB partition limit due to linux Kernel (a patch is available for hacked units)
4. 2 TiB partition limit due to Apple partitition table being used
5. The tivo application code (tivoapp) appears to use signed 32bit integers for sector numbers and sizes in a number of places.


So with the correct configuration a 1.5TB drive should be able to function. It seems as if the current available tools may improperly partition the 1.5TB drive in certain circumstances.

[jmpage2]

Out of curiosity, what are the noise levels for anyone who has gone ahead and set one up?

[TexasGrillChef]

TexasGrillChef, do you have suggestions turned on? Curious if any problems if it is filled.

So far everything has worked fine. I don't use suggestions. At most right now I have around 130hours of HD programming recorded. It did get up to about 159 hours.

Who knows what if I really fill it up.

TGC