TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like
Google.
Pages:1
Messed up the last step of my Maxtor 80x2 upgrade for HDR212
(Click here to view the original thread with full colors/images)
Posted by: blenny
Hello, I recently bought a HDR212 (20 hour) from ebay with the intention of installing two new Maxtor 80 GB drives. I did everything right, but one very important detail...
- Bought two new 80 GB Maxtor IDE drives
- Performed a backup of the original Quantum (v1.x) to one of the Maxtor IDE Drives using Dylan/dd and marked the Maxtor drive as A.
- Performed a BlessTivo and MadTivo with the two Maxtor IDE drives installed
- Mistakenly put the original Quantum back into the TiVo with the correct Maxtor drive as drive B
- Booted up the TiVo, it rebooted once and when complete the TiVo only reported 117 hours.
- TiVo then upgraded from v1.x to v2.0 that night.
I'm hoping I can recover from this mistake and get a 80GB in place of the original Quantum Drive. Although, the way
I see it... I don't have a backup of the original v1.x drive image without the magic stuff Bless and Mad did. My
Maxtor A drive thinks it is married to the Maxtor B drive, but Maxtor B was married with Quantum A.
What do you think, is there a way to wipe/unmarry the Maxtor B and remarry it to the Maxtor A and just hope and pray I don't need a backup? Or maybe I'm missing an alternative...
I'm hoping this table comes out ok, it contains the partition information from Dylan's pdisk:
code:
QUANTUM A
# Type Name Length Base Size
-- -------------------------- ---------------------------------- --------------- ----------- ------
1 Apple_Partition_Map Apple 63 1 -
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 131072 540736 64.0M
9 Ext2 /var 262144 671808 128.0M
10 MFS MFS Application Region 1048576 933952 512.0M
11 MFS MFS Media Region 42016672 1982528 20.0G
MAXTOR B
# Type Name Length Base Size
-- -------------------------- ---------------------------------- --------------- ----------- ------
1 Apple_Partition_Map Apple 63 1 -
2 MFS MFS Second MFS Application Region 8192 64 4.0M
3 MFS MFS Second MFS Media Region 156293231 8256 74.5G
MAXTOR A
# Type Name Length Base Size
-- -------------------------- ---------------------------------- --------------- ----------- ------
1 Apple_Partition_Map Apple 63 1 -
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 262144 43999200 128.0M
9 Ext2 /var 262144 671808 128.0M
10 MFS MFS Application Region 1048576 933952 512.0M
11 MFS MFS Media Region 42016672 1982528 20.0G
12 MFS MFS Application Region 2 8192 44261344 4.0M
13 MFS MFS Media Region 2 112031950 44269536 54.45M
14 Ext2 Hack 131072 540736 64.0M
Posted by: kdmorse
Hmm... You should be able to dig your way out fairly easily. Use DBD to rebless the 80GB maxtor B drive. The Maxtor A drive should still be primed and ready to mfsadd the newly blessed B drive. The Quantum however will never boot again. (Unless restored from somewhere of course).
Might want to wait to see if other posts agree before you jump in though. If I'm wrong (eh, it happens...), it leaves you in a ditch.
-Ken
Posted by: davewill
Getting to an 80+80GB config should be easy enough, run BlessTivo on the Maxtor B drive, then install the two Maxtor drives, and the TiVoMad and marry process should happen normally. I do think you're hosed as far as having a clean backup goes, but I'd get a second opinion (or even a third) before I did anything too rash.
Posted by: DanT
YOU CAN RECOVER FROM THIS VERY EASY!!!!
Sorry, but I didn't want you to read the above answers and jump the gun.
You should copy the Maxtor A back over the Quantum, so that the Quantum is now identical to the TivoMad-ready Maxtor.
There is a backout script on TivoMad's site, that allows you to undo the changes he made, as long as the drive hasn't been booted in the Tivo yet. So you run that script on the Quantum, and it should back out the TivoMad updates.
Put that Quantum back in the Tivo by itself and make sure it boots up. This is just to verify that you're back to a good state with it.
Now re-bless the Maxtor B and put both Maxtors into the Tivo. You should now have your 200-hr Tivo (and the fixed Quantum as well).
------------------
Dan T.
RKBA!
Posted by: blenny
Sounds great DanT, but I'm concerned that the Maxtor A now contains more data than the Quantum A? I'm sure I selected the "My system will be great than X MB, so create a extra swap space".
Just adding up the aggregate "size" column reported back from pdisk shows Quantum A:2968.00MB Maxtor A with TivoMad:3154.45MB
Looks like the offical TiVoMad site is down right now, I'm hoping the script is human readable so I can see what it does, http://www.btinternet.com/~t.heartfield/tivo
Posted by: kdmorse
DanT's right - it could work. The orignal partitions were copied from the Quantum to the Maxtor. Then more parititions were added - but the original partitions were not modified much. So - if you copy the drive back from the Maxtor to the Quantum, all the original partitions will be copied back. The added partitions (including the second swap space) won't, as they won't fit.
The backout script (run on the Quantum) will then undo the changes it made to the partition table, and rc.sysinit. Since the Maxtor A was never actually booted in the tivo, the second swap space and the new mfs partition weren't actually added to the A drive yet. That could leave you with essentially an unmodified working Quantum A drive.
I give it a good 50-50 chance of working perfectly. And at this point, the quantum A is not usable, so there's nothing to loose.
-Ken
Posted by: oosik77
Shouldn't he back out the changes first and then copy it back?
------------------
I am Porky Pig of Borg. You will be assim... assim... assim... abosorbed.
Posted by: DanT
quote:
Originally posted by oosik77:
Shouldn't he back out the changes first and then copy it back?
Why? He'll just have to re-run TivoMad on the Maxtor after he copies it to the Quantum. He might as well save a step by copying it as-is to the Quantum, and backing it out there.
Plus, if it doesn't work this way, he can then run the backout script on the Maxtor, and try copying it again.
Also, blenny, when you copy the Maxtor to the Quantum, you WILL get an error about "No more space on device" since you're trying to copy 80G onto 20G. But don't worry about it, since you're only concerned with that first 20G.
------------------
Dan T.
RKBA!
vBulletin Copyright ©2000 - 2009,
Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2009
- Created by Stefan "Xenon" Kaeser
Modified by Adam J. de Jaray