Help a newbie-Series 2-upgrade to 2 drive with 120 gb Samsung...HELP!

[macros746]

Hello all,
I'm new to this and am having a TERRIBLE time. I am attempting to comb the internet to find the solution (if there is one) but if anyone here can help me out it would be much appreciated. Let me lay out exactly what happened.
I am attempting to upgrade a TIvo series 2 with a 60 gb Western Digital Hard drive to a 2 drive Tivo by adding a 120 gb Samsung drive.
Following the Hinsdale guide and using MFS 2.0 tools I backed up the Tivo image...no problem.

to add a new drive i followed the Hinsdale instructions using the following command

mfsadd -x /dev/hdc /dev/hdb
with the drives set up as suggested. When I plugged everything into the tivo it hung on the powering up screen

checked all of the jumpers and tried again...same result.

All of the drives reported the correct size by the way. So then I restored the image onto the orignal Tivo drive and it booted up right away. I powered down and used the IDE cable with a master/slave set up to make sure that was working. It powered up fine.

Using a diffent tack I left the restored WD drive and I blessed the Samsung 120 GB using Dylan's book disk (it reported the size as 111 GB...but I am given to understand that this is correct for a drive of this size? Linux, BIOS and Windows all recognize the drive as the right size. Having gotten a successful bless I installed it along side of the WD drive......it hung on the powering up screen.

I decided to use a different tack....using the Hinsdale guide I expanded the restore image across the two drives using the following command:

mfsrestore -s 127 -xzpi /mnt/dos/tivo.bak /dev/hdc /dev/hdb

I got a successful message telling me my Tivo had been expanded to 199 hours. But when I installed the two drives it seemed as though all was well...I got past the powering up screen to the almost there screen....and then I got the GSOD.

I decided that the Samsung drive must be faulty. So I restored and expanded the image to the Samsung drive alone. Changed the jumpers to master and....it booted up beautifully. SO it seemed that the Samsung drive was fine. So then I blessed the Western Digital drive and tried to add that as the slave. Hung up on the Powering Up screen.

Finally I expanded the image over two disks using the same command as above only with the Samsung as master and the Western Digital as the Slave.....same result..apparent success and then GSOD.

I've tried these combinations over and over. I don't believe I am making any errors...it just doesn't seem to work. Either drive works beautifully by itself but it will not run with two drives. Is the power supply insufficient? Am I missing something obvious? Please help......I promised this to my friend by tomorrow. I've read other posts using this same setup with no problem....so how could it be the power? HELP!

THanks for your time....I apologize for the length of this post

Macros

[mrblack51]

there is a problem with mfstools 2.0 and the way it creates swap partitions. Search on AVS and you should find some info on the issue.

[macros746]

I used the -s 127 switch in my command line when I expanded across the two drives.....so I don't believe that that is the solution. Any other ideas?

Macros

[macros746]

Another question in relation to all of this...for those that have done a succesful upgrade.....how long did you have to wait before Tivo booted? Should I leave it to try for 10 minutes or is that just overkill? If I get the GSOD should I leave it plugged in to try to fix itself?

Macros

[orangejaylove]

ack I got two 120gb Sammys waiting to go in hope its not the drives... or that I'm going to have the same problem... good luck

[macros746]

While cruising all of the Tivo hacking forums for info I DID find several people that had issues with the 120 samsungs....but I also found tons of people that had no trouble.....I wouldn't worry too much. I think I've isolated the problem.....the y-splitter that I was using (purchased at Radio Shack) had a loose prong. Last night I got a clean boot twice in a row with both drives...and then suddenly it wouldn't boot anymore after I moved it. The only thing I could think of that would cause that was a loose wire. So I took everything apart meticulously and found that loose prong....I'll replace the cable tonight and let you know if that was it.

Macros

[macros746]

Well all.....sadly that wasn't it. Now I'm in a GSOD boot cycle (I got a short boot and then it went back to the powering up screen. I'm inclined to let it continue and see if it can fix itself....if anyone else has any ideas I'm listening....

macros

[tivosohn]

I am only guessing this is a problem due to the swap space doesn't handle that size of total drive space. Anyone know what could have caused this? I ask this because I am seeing the same thing as soon as I stick in the access card. If I leave the access card out, the machine runs fine. Once I put it in, I get a lot of "DriveReady SeekComplete Error" as I mentioned in my other post.

http://www.dealdatabase.com/forum/showthread.php?s=&threadid=25694

[fixn278]

Originally posted by macros746
Hello all,
I'm new to this and am having a TERRIBLE time. I am attempting to comb the internet to find the solution (if there is one) but if anyone here can help me out it would be much appreciated. Let me lay out exactly what happened.
I am attempting to upgrade a TIvo series 2 with a 60 gb Western Digital Hard drive to a 2 drive Tivo by adding a 120 gb Samsung drive.
Following the Hinsdale guide and using MFS 2.0 tools I backed up the Tivo image...no problem.

to add a new drive i followed the Hinsdale instructions using the following command

mfsadd -x /dev/hdc /dev/hdb
with the drives set up as suggested. When I plugged everything into the tivo it hung on the powering up screen

checked all of the jumpers and tried again...same result.

All of the drives reported the correct size by the way. So then I restored the image onto the orignal Tivo drive and it booted up right away. I powered down and used the IDE cable with a master/slave set up to make sure that was working. It powered up fine.

Using a diffent tack I left the restored WD drive and I blessed the Samsung 120 GB using Dylan's book disk (it reported the size as 111 GB...but I am given to understand that this is correct for a drive of this size? Linux, BIOS and Windows all recognize the drive as the right size. Having gotten a successful bless I installed it along side of the WD drive......it hung on the powering up screen.

I decided to use a different tack....using the Hinsdale guide I expanded the restore image across the two drives using the following command:

mfsrestore -s 127 -xzpi /mnt/dos/tivo.bak /dev/hdc /dev/hdb

I got a successful message telling me my Tivo had been expanded to 199 hours. But when I installed the two drives it seemed as though all was well...I got past the powering up screen to the almost there screen....and then I got the GSOD.

I decided that the Samsung drive must be faulty. So I restored and expanded the image to the Samsung drive alone. Changed the jumpers to master and....it booted up beautifully. SO it seemed that the Samsung drive was fine. So then I blessed the Western Digital drive and tried to add that as the slave. Hung up on the Powering Up screen.

Finally I expanded the image over two disks using the same command as above only with the Samsung as master and the Western Digital as the Slave.....same result..apparent success and then GSOD.

I've tried these combinations over and over. I don't believe I am making any errors...it just doesn't seem to work. Either drive works beautifully by itself but it will not run with two drives. Is the power supply insufficient? Am I missing something obvious? Please help......I promised this to my friend by tomorrow. I've read other posts using this same setup with no problem....so how could it be the power? HELP!

THanks for your time....I apologize for the length of this post

Macros

Two quick things to check. First, WD drives are extremely picky about jumpers. If it is a single master and you add a second drive, some of their HD's require you to move the jumper to Master w/ Slave Present.

Also, are you sure when you blessed the drives, you had them set up properly? msadd -x /dev/hdc /dev/hdb assumes the original drive is connected to your second IDE channel in the primary position and the new drive to be added is the second drive on the primary channel. Make sure you check in the bios to make sure the drives are being recognized properly.

Good luck.

[tivosohn]

msadd -x /dev/hdc /dev/hdb assumes the original drive is connected to your second IDE channel in the primary position and the new drive to be added is the second drive on the primary channel.

Is it a MUST for the master drive in the order as you mentioned? Will it be a problem if I have the first on the primary master IDE and the second drive on slave master IDE. Then ran the msadd -x /dev/hda /dev/hdb ? Is that not going to work? By the way, my cmos does recognize the drives with the correct sizes.

[mrblack51]

most tivo boot disks reserve primary master for a dos drive, so i would recommend not connecting a drive you want to put into the tivo as primary master. beyond that, it shouldnt matter where you put the drives or the order, so long as you adjust the commands accordingly

[fixn278]

Originally posted by tivosohn
Is it a MUST for the master drive in the order as you mentioned? Will it be a problem if I have the first on the primary master IDE and the second drive on slave master IDE. Then ran the msadd -x /dev/hda /dev/hdb ? Is that not going to work? By the way, my cmos does recognize the drives with the correct sizes.

I think the primary master is the only one you can't use (something about byte-swapping maybe)

You may alreday know this but..

hda=primary master
hdb=primary slave
hdc=secondary mater
hdc=secondary slave

I would disconnect everything from the bus except the two drives you are using and the cdrom or the floppy

Then, make sure if anything is on the primary master spot, it is the cdrom.