Added 2nd HD, now stuck at Powering up. (or will loop)

[Toaster]

I upgraded my S1 Dtivo to a 160gb Maxtor, running Superzap's 2.5.2 sw.

I recently bought a 120gb Western Digital HD to add as a second HD, so I pulled Drive A (160gb maxtor) put in PC as Secondary Master, put 120gb WD in pc as primary slave, cd-rom was primary master, and a 10gb dos hd was secondary slave. I booted with MFStools 2.0 (rev j) newest disc from the Hinsdale how-to site, did a backup of my A-drive (hdc), then proceeded to do a mfsadd -x /dev/hdc /dev/hdb, it finished in a second (bam!), I pressed ctrl-alt-delete, waiting for the post, powered down, removed the drive's from the pc, placed them back in the Dtivo, and it was stuck on Power up screen.

I checked jumpers, the 160gb is master, the 120gb wd is slave- tried again, power up for about 15+ minutes. Pulled the 120gb out and the 160gb gets past the power up (alone) but resets/reboots at almost there screen.

I thought maybe it was the ata/66 80 conductor cable- I stretched it pretty far when I put in the second drive- so I replace it with a factory 2-drive 40 conductor ide from another Dtivo, same results.

I'm not sure what went wrong- the jumper settings or something got fubar with adding the 2nd drive. The maxtor has 3 jumper settings, Master/Slave/Cable select, it is set to MASTER, the WD is set for SLAVE...

PLEASE HELP... I'm afraid I lost 160gb worth of recordings.

Edit: btw, when I upgraded to the 160gb, I used the -s 127 command to add the extended buffer.

[genericuser]

Ugh... I bet you have a WD1200JB <-- model. The one with 8MB cache, correct?

I had the same problem that you did. I could not add the WD120 gig as a B drive. I had to make it the A drive.

I had the same problem as you. After running the mfsadd -x /dev/hdc /dev/hdd command, I would sit at the power up or reboot.

Perhaps someone with more wisdom than I can show you how to remove the partitions that mfsadd created. If you do figure it out, let us know.

My only thought is to copy the maxtor to the WD (assuming you were not 100% full on the maxtor). Then it would be the boot drive.

[Toaster]

Well this is strange, here is what happend.

I tried many combination (if not all of them), which drive was master/slave, where they were on the cable (black (end) connector or gray (middle) connector), I tried a new cable (ata/66 from another new HD), a 2 drive cable from a DSR6000 (factory cable). NOTHING WORKED! I tried making them both cable select, and switching positions on the cable. The unit would just sit there. I tried with 1 drive (drive-a/160gb maxtor), and it would just reboot at "Almost There..." :mad: :eek: :confused:

So finally I gave up, and put them back to 160gb (drive-a) master at the gray middle connector of the ata/66 cable (not sure if this one cable with the Maxtor or the Western digital? but its an 80 conductor ata/100+ cable), the Western digital 120gb drive-b as slave at the far end (black) connector, and the blue connector in the motherboard (NOTE: this was the way I tried it the very first time, and many other times in the process)

I figured I'd boot it up one more time (for the heck of it), and this time it got to Almost There... (first time with 2 drives), and it GSOD'd... I left it alone, it worked for about 20+ mins, and then it came back to life, and now seems to work...:D

Everything seems to be in place, all my recordings, settings, etc... so I couldn't tell you why it didn't work then all of a sudden did work...?

Now its got 242 hours of recording time.

[BubbleLamp]

Well you guys need to brush up on your IDE specs. Check out the links in my old post here (http://dealdatabase.com/forum/showthread.php?s=&threadid=20341#post75045).

[Toaster]

Having good information is always a bonus, however the situation for me was, the exact same configuration didn't work (more than once) then all of a sudden started working!? (WTF!?)

at least 12 times my unit would not get past the Powering Up... screen, then all of a sudden (after trying other configurations and then reverting back to the main and ultimately the correct configuration) it did boot and I got the GSOD.

[GREEK]

try runideturbo=false next time, helps with aftermarket large drives. The jumpers need some playing with here and there, have one that needed BOTH to be cable select. BTW I have a unit with dual WD1200JB with 8mb cache, been up over a year. I run ideturbo=false on ALL nonstock tivo drives, and ALL sereis2 drives for use in sereis1 machines........

[Toaster]

Now that its working, should I set ideturbo=false, or leave it alone?

[genericuser]

Leave it alone.

I would have suggested runideturbo=false, but since you already had a booting A drive, I did not think it was necessary.

Question: Does that bootflag get reset during the mfsadd -x operation? That is one thing I never thought of.

As far as I know, there is no need to add that bootflag to the B drive. I do not even think that is possible.

Glad you got it back up and running.