Separate names with a comma.
Discussion in 'TiVo Series3 HDTV DVRs' started by bkdtv, Oct 19, 2007.
Is it done yet
Its still in the oven.
I waited another hour or so but there was still no hard drive or CPU activity, so I ended it. I removed the drives and tried the drive from the HD XL with another 2TB new drive. It worked for a while and also 'froze up', so I figured it wasn't a problem with the drives. I then put the HD XL drives into a pair of hard drive docks that I had available to me, and tried again. This time, it ran smoothly until completion, and never froze! It took 2.5/3 hours. I'm now running the HD drives and it seems to be working well so far...fingers crossed!
I do have a question that I forgot to put in the initial post: I had upgraded the HD's drive to a 750GB (I believe in 2007). Will the procedure be any different when copying the upgraded drive, or will it be the same as copying the stock Tivo drive?
Thanks a lot for the help, guys!
It's the same. I upgraded my original S3 to 1TB then recently upgraded from the 1TB to 2TB.
That's what I was hopin'....
The HD drive just finished copying, and everything seemed to go well. I'll put them together and get them up & running tomorrow...hopefully!
Well...I have good news and bad news...
The good news: I got both Tivos up-and-running with the new drives...
The bad news: On the HD, I 'only' got 287 hours, and on the HD XL, I 'only' got 300 hours. I was expecting about 318 hours on each...
Is this pretty typical for an upgrade, or did I do something wrong?
Did you forget to "Supersize"?
I didn't use 'Supersize'. After the copy was done, I just used the MFSadd. Do I need to supersize, too? Is that in the WinMFS tools also?
Yes to both questions.
Thanks for the help. Can I just do the supersize now (I hope!), or do I have to do the whole copy procedure over again?
You should be able to just do the supersize. The current difference between the HD and the HDXL (287 vs. 300) may be due to the previous upgrade. You should get an MSFinfo from the HD drive after the supersize and post it here.
Not sure which info is needed:
Mfsinfo (Drive 2)
Boot Page: root=/dev/hda7
Active Boot Partition: 6 Active Root Partition: 7
Backup Boot Partition: 3 Backup Root Partition: 4
MFS Super Header
devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hda14 /dev/hda15
map_start=1121 map_size=1 backup_map_start=589822
next_map_start=263266 next_map_size=6 next_backup_map_start=589816
zone_first=1122 zone_last=263265 zone_size=262144 min(chunk)=262144
free=262144 checksum=d6ea8fe3 logstamp=20644637 num_bitmap=1
map_start=263266 map_size=6 backup_map_start=589816
next_map_start=263272 next_map_size=34 next_backup_map_start=589782
zone_first=589824 zone_last=138215423 zone_size=137625600 min(chunk)=20480
free=7311360 checksum=bfbe1f6c logstamp=20657828 num_bitmap=14
map_start=263272 map_size=34 backup_map_start=589782
next_map_start=138219520 next_map_size=1 next_backup_map_start=138809343
zone_first=263306 zone_last=589777 zone_size=326472 min(chunk)=8
free=54080 checksum=f77728fe logstamp=20658273 num_bitmap=17
map_start=138219520 map_size=1 backup_map_start=138809343
next_map_start=138481665 next_map_size=10 next_backup_map_start=138809333
zone_first=138219521 zone_last=138481664 zone_size=262144 min(chunk)=262144
free=262144 checksum=f2af6123 logstamp=20644637 num_bitmap=1
map_start=138481665 map_size=10 backup_map_start=138809333
next_map_start=138481675 next_map_size=34 next_backup_map_start=138809299
zone_first=138809344 zone_last=310718463 zone_size=171909120 min(chunk)=20480
free=8478720 checksum=810bce02 logstamp=20657824 num_bitmap=15
map_start=138481675 map_size=34 backup_map_start=138809299
next_map_start=310728704 next_map_size=34 next_backup_map_start=310730718
zone_first=138481709 zone_last=138809292 zone_size=327584 min(chunk)=8
free=289848 checksum=68b061c9 logstamp=20658273 num_bitmap=17
map_start=310728704 map_size=34 backup_map_start=310730718
next_map_start=310728738 next_map_size=67 next_backup_map_start=310730651
zone_first=310730752 zone_last=1463283711 zone_size=1152552960 min(chunk)=20480
free=55992320 checksum=dabee648 logstamp=20657828 num_bitmap=17
map_start=310728738 map_size=67 backup_map_start=310730651
next_map_start=0 next_map_size=0 next_backup_map_start=0
zone_first=1463283712 zone_last=3905175551 zone_size=2441891840 min(chunk)=20480
free=2440560640 checksum=a64ac75d logstamp=20657759 num_bitmap=18
#: type name length base ( size )
1 Apple_partition_map Apple 63@1 ( 31.5K)
2 Image Bootstrap 1 1@309550766 ( 512.0 )
3 Image Kernel 1 8192@309550767 ( 4.0M)
4 Ext2 Root 1 524288@309558959 ( 256.0M)
5 Image Bootstrap 2 1@310083247 ( 512.0 )
6 Image Kernel 2 8192@310083248 ( 4.0M)
7 Ext2 Root 2 524288@310091440 ( 256.0M)
8 Swap Linux swap 262144@310615728 ( 128.0M)
9 Ext2 /var 524288@310877872 ( 256.0M)
10 MFS MFS application region 589824@311402160 ( 288.0M)
11 MFS MFS media region 137630712@171920054 ( 65.6G)
12 MFS MFS application region 2 589824@311991984 ( 288.0M)
13 MFS MFS media region 2 171919990@64 ( 82.0G)
14 MFS MFS App by Winmfs 2048@312581808 ( 1.0M)
15 MFS MFS Expanded by Winmfs 3594444800@312583856 ( 1.7T)
Total SA SD Hours: 2083 Total DTV SD Hours: 1818 64 % Free
Software: 11.0m-01-2-652 Tivo Model: TCD652160
I'm guessing by the number of SD hours shown (2083), that it didn't work...
The partition map looks OK as far as I can tell. Hopefully, it is just using a different formula for calculating the hours. I suggest putting it in the TiVo and see what it says.
I ran supersize on both the HD and the HD XL, and they're both up to 318HRS.!
Thanks for all of the help guys...very much appreciated!
(In my best Mr. Burns voice): Excellent.
I'm considering upgrading my S3 OLED (TCD648250B) to a 2TB drive and was looking at the WD20EURS on newegg. At the top of the page it says there's "a newer version of this item" with a link to the WD20EURX.
Is there any advantage using the EURX over the EURS in an S3? I don't know what SATA controller is in the S3, but I'm assuming it's not SATA III, so it seems like the 6.0Gb/s in the EURX wouldn't really help. yes? no?
Any other advantages/disadvantages of the EURX over the EURS? Specifically for my model TiVo that is... S3 OLED TCD648250B.
For that application, or any TiVo application, there is nothing to be gained by the EURX drives, but they should still work due to backwards-compatibility.
It's actually kind of ridiculous that they even make SATA-III X-model drives in the first place for a "Green" and low-performance drive.
I've used EZRX drives in TiVo HDs, built on the S3 platform, so it's highly unlikely that you'd have any issues. I only got SATA-III drives, because they were cheaper than SATA-II, due to a holiday sale.
I'm using EURSs in several S3s, both 648s and 652s, quite successfully.
I have no experience with the Xs, but as long as I can get the older ones, I'm going to keep on doing so, funds permitting.
And they're still shipping EURS drives in brand new Roamios. It's their go-to drive and has been for several years.
Pick the best daily sale you can find, don't forget to factor in tax & shipping, and forget the rest. They only use 1.5Gb/s even if you could figure out how to shove a 15000RPM SAS enterprise drive into it.