Western Digital 160gig drive won't work

[tivoholic2112]

Okay, Here's my tail of woe. Wanted to add some hours to my Philip Series 1 Tivo (312). Had started out with a 30 gig drive many years ago, and had upgraded to a Maxtor 120 gig drive. Hit Google, found that MFSTools had been updated, and downloaded a copy. Pulled the Maxtor, and connected it with a new Western Digital 160 gig drive. Still have the original 30 gig drive, so I'm not too worried. That was a mistake. Ran the mfsadd command, exact command:
mfsadd -r 4 -x /dev/hdb /dev/hdc
Mfsadd reports that all is well, I now have nearly 300 hours of capacity. Pull the drives, and put them back in the Tivo. Endless loop, "just a few more minutes". What the heck??? Pull the drives, and put them back in the pc, run MFS Tools, and it reports the block 0 has signature 9214 rather than 1492. Okay, start googling. Find MFSLive (boy, wisht that happened first) download WinMFS and boot up the pc. WinMFS reports that both of the drives are "not a tivo drive". Run make bootable, command completes successfully. No change in "not a tivo drive" though. Download MFSLive, and run blesstivo with no parameters on the new drive. (got nothing to lose there). Command completes successfully. Run blesstivo with the bpage parameter on the original drive. Command completes successfully. Reboot MFSLive, no complaints about unknown partition. Back to the Tivo, no joy at all, in fact worse off than before. Now stuck at my little man in his field of marbles. Hit the MFSLive support forum, Spike, (very helpful) offers some suggestions. States:
Series 1 can handle only 137GB per drive w/o installing hacked linux kernel.
So you 160GB won't work if you do

mfsadd -r 4 -x /dev/hdb /dev/hdc

Winmfs has a tool that can divorce it so divorce "B" drive then make sure your 120GB work ok in a live Tivo.

Mfslive cd do

mfsadd -r 2 -nx /dev/hdb /dev/hdc

MFSSplit won't let me "divorce" the drives. Spike wants me to run MFSInfo. Get back:
mfsinfo /dev/hdb /dev/hdc
mfsinfo: /dev/hdb10: no such device or address

mfsinfo /dev/hdc /dev/hdd
mfsinfo: /dev/hdc10: no such device or address

At this point, Spousal Unit is becoming impatient with lack of Tivo in household. Back to Google. Find out about InstantCake, and purchase a copy with TWP. (adding the CacheCard was part of the plan) Tell the Spousal Unit, sorry, all those shows you saved, bye-bye. Not appreciated, but telling her light at end of tunnel visible help. Pop the Maxtor and the WD in the PC, boot up InstantCake, follow the scripts, and success is reported. Out come the drives of the PC and back into the Tivo. Stuck at "just a few more minutes". What the heck? Pull the drives, and attach the WD 160 back in the PC and run InstantCake. Success is reported. Back to Tivo, no joy, stuck in start up. Okay, let's try it with original Maxtor 120 gig drive. Bake the cake, success reported, and back to Tivo. Trumpets sound, angels sing, I've got Tivo back. Well, what to do about the WD 160 gig drive. Okay, let's run BlessTivo on it, and pop it in with the Maxtor. Run BlessTivo with MFSLive, success reported, connect it up in the Tivo. Silence...stuck in starting up. Okay, let's try it with WinMFS. Fire up WinMFS, and "erase format" on the WD 160 gig drive. Connect up the Maxtor, and rerun WinMFS MFSadd command. Success. Run MFSInfo with both drives connected and get back this info:

Mfsinfo (Drive A: 1, Drive B: 2)

Boot Page (Byte Swapped)
Boot Page: root=/dev/hda7
Active Boot Partition: 6 Active Root Partition: 7
Backup Boot Partition: 3 Backup Root Partition: 4

MFS Super Header
state=0 magic=abbafeed
devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hdb2 /dev/hdb3
zonemap_ptr=1121 total_secs=551263232

Zone Maps
Z0: type=0
map_start=1121 map_size=1 backup_map_start=1048574
next_map_start=263266 next_map_size=9 next_backup_map_start=1048565
zone_first=1122 zone_last=263265 zone_size=262144 min(chunk)=262144
free=262144 checksum=cdc1734a logstamp=2424408 num_bitmap=1
Z1: type=2
map_start=263266 map_size=9 backup_map_start=1048565
next_map_start=263275 next_map_size=66 next_backup_map_start=1048499
zone_first=1048576 zone_last=25825279 zone_size=24776704 min(chunk)=2048
free=24256512 checksum=6de702ad logstamp=2424419 num_bitmap=15
Z2: type=1
map_start=263275 map_size=66 backup_map_start=1048499
next_map_start=25826305 next_map_size=5 next_backup_map_start=25827322
zone_first=263341 zone_last=1048492 zone_size=785152 min(chunk)=8
free=761040 checksum=3f0c9711 logstamp=2424419 num_bitmap=18
Z3: type=2
map_start=25826305 map_size=5 backup_map_start=25827322
next_map_start=238688257 next_map_size=9 next_backup_map_start=238689270
zone_first=25827328 zone_last=238688255 zone_size=212860928 min(chunk)=32768
free=212860928 checksum=eea97298 logstamp=0 num_bitmap=14
Z4: type=2
map_start=238688257 map_size=9 backup_map_start=238689270
next_map_start=0 next_map_size=0 next_backup_map_start=3735928559
zone_first=238689280 zone_last=551263231 zone_size=312573952 min(chunk)=32768
free=312573952 checksum=ea570a25 logstamp=0 num_bitmap=15

Partition Maps
#: type name length base ( size )
1 Apple_partition_map Apple 63@1 ( 31.5K)
2 Image Bootstrap 1 4096@64 ( 2.0M)
3 Image Kernel 1 4096@4160 ( 2.0M)
4 Ext2 Root 1 262144@8256 ( 128.0M)
5 Image Bootstrap 2 4096@270400 ( 2.0M)
6 Image Kernel 2 4096@274496 ( 2.0M)
7 Ext2 Root 2 262144@278592 ( 128.0M)
8 Swap Linux swap 614400@540736 ( 300.0M)
9 Ext2 /var 262144@1155136 ( 128.0M)
10 MFS MFS application region 1048576@1417280 ( 512.0M)
11 MFS MFS media region 24777728@2465856 ( 11.8G)
12 MFS New MFS Application 1024@27243584 ( 512.0K)
13 MFS New MFS Media 212860928@27244608 ( 101.5G)
14 Apple_Free Extra 16192@240105536 ( 7.9M)

Tivo B drive
1 Apple_partition_map Apple 63@1 ( 31.5K)
2 MFS New MFS Application 1024@64 ( 512.0K)
3 MFS New MFS Media 312573952@1088 ( 149.0G)
4 Apple_Free Extra 6768@312575040 ( 3.3M)

Total SA SD Hours: 293 Total DTV SD Hours: 256 100 % Free
Software: 3.0-01-1-000 Tivo Model: not set in MFS

Pull the drives and back to the Tivo. Hopeful at this point, but hopes are dashed on the rocks when stuck are "just a few more minutes. Pull the drives, and put them back in the PC. Fire up WinMFS and check MFSInfo. Reports that "not a tivo drive". Okay, now I'm totally confused. Pull the WD 160, and fire up InstantCake with just the Maxtor, success reported, and everything runs fine in TivoLand. At least at this point, Spousal Unit is no longer walking around with that unhappy look on her face.
So, I'm looking for ideas at this point. Could it be the the Maxtor is a 5400 drive and the WD is a 7200 drive? Should I switch out the WD for a Seagate? (only other IDE drive at Fry's) And, just cause I like to be complete, I've changed cables, and I've also checked the WD drive in Windows.

Thanks!!!!
Tivoholic2112

[Lou Jacob]

It's hard to follow your entire story here; you've got a LOT of variables in that you've got two different drives, and you are using three different tools/methods to perform your upgrade.

Best I can guess is that you've got a compatibility problem (or a defect) with the WD drive. Hopefully, you ran diagnostics on it just to rule out that problem; that should always be the FIRST thing you do.

Search around a bit and you'll find that others have had problems with certain WD drives (caviar blue) and also see the references to the thread I posted in the upgrade center at TCF; that could be the problem, as well...

[tivoholic2112]

Thanks for the quick reply Lou. It is a WD Caviar Blue, Model WD1600AAJB-00J3A0. I'm going to see if Fry's will take it back and try a Seagate. Also, sorry about the long post, as you can probably guess, I'm in the field, and a bit obsessive about documenting exactly what I'm doing.
Thanks!

[tivoholic2112]

Hi Lou,
Fry's doesn't stock anything wth ide except WD. I found this drive Hitachi P7K500 320GB Hard Drive - 7200, 8MB at an online retailer. do you know if this drive would work in my series one with my 120 gig maxtor? Thanks again for your help.

[Lou Jacob]

Hi Lou,
Fry's doesn't stock anything wth ide except WD. I found this drive Hitachi P7K500 320GB Hard Drive - 7200, 8MB at an online retailer. do you know if this drive would work in my series one with my 120 gig maxtor? Thanks again for your help.

You might want to consider one of the drives we offer; we know those work!!!

[tivoholic2112]

Okay Lou, consider me spanked. I was going to order a drive from you, but went over to a friends house and driving back saw a computer store. Said, "hey, what the heck, let's see what they have." Turns out that they've got a seagate 80 gig drive for 49 bucks, and I figure, well, I'll buy this now, and pop in in the Tivo, and get the spousal unit back on the path to tivo bliss. Use instantcake on the new drive, pull the old drive, and pop it in. All good. Cool! Pull out the new drive, and mfadd it via WinMFS, and put them both back in the Tivo. Now, better than all good, Got 250 hours, got TWP+ got a happy spousal unit. Well, that wasn't meant to last. Came home today, and better half reports that tivo keeps rebooting all by itself, interrupting prime view time. Check the logs, and sure enough, its trying to make the daily call, and then reboots. Force a manual test call (all via CacheCard ethernet interface) and all good. Try the daily call, and all good, until loading data. at 76% tivo reboots. Trying it again, same thing, all good until 76% loaded, and then a reboot. Any ideas or suggestions for me? Going back to the last thing changed, it's gotta be the new drive, but everything else is working fine, recordings, playback, interface, so can't figure out what the new drive might have done to the program database so that it forces a reboot at 76%. Thanks for all your help, and yes, I will be purchasing my hardware (might pull the plug on an HD tivo, and will want to add storage) from you!!