Noob may have screwed up Creating Drives :(

[kulmak]

Ok, I think I may have screwed up, so here goes my question

DSR6000
160 gig 7200RPM 8 Meg Cache drive (Drive A)
120 gig 7200RPM 8 Meg Cache drive (Drive b)
2 9 DB 1000RPM Fans to reduce the heat caused by 7200 drives

Xtreme 2.5.2

I simply dropped the 160 gig drive into my PC as HDC and the 120 as HDD, followed the readme's, built everything up as a dual drive system, dropped the drives into my DSR6000, and everything works. I have 242 hours of recording time.

From what I was just reading, when the 160 drive reaches its limit on recording, the Tivo with either Crash or stop recording.

My Question is, Since my 160 is Drive A, will it record from Drive A to Drive B and then when Drive B fills crash or stop recording, or will this result when Drive A fills up?

I hope that is enough info to answere the question, if you need anymore, please let me know what else you need.

[PlainBill]

Ok, I think I may have screwed up, so here goes my question

DSR6000
160 gig 7200RPM 8 Meg Cache drive (Drive A)
120 gig 7200RPM 8 Meg Cache drive (Drive b)
2 9 DB 1000RPM Fans to reduce the heat caused by 7200 drives

Xtreme 2.5.2

I simply dropped the 160 gig drive into my PC as HDC and the 120 as HDD, followed the readme's, built everything up as a dual drive system, dropped the drives into my DSR6000, and everything works. I have 242 hours of recording time.

From what I was just reading, when the 160 drive reaches its limit on recording, the Tivo with either Crash or stop recording.

My Question is, Since my 160 is Drive A, will it record from Drive A to Drive B and then when Drive B fills crash or stop recording, or will this result when Drive A fills up?

I hope that is enough info to answere the question, if you need anymore, please let me know what else you need.

Tough to answer without a little bit more information. I don't know how TiVo fills the drives, but you are probably right - it will fill up the first drive, then the second.

If Xtreme used only 137 GiB of the 160, obviously you're ok. If it used the full 160 GiB, you'll get hosed when it goes over 137 GiB on the first drive.

Now, how to tell what happened. A 120 GiB in a Series 2 gives about 105 hrs recording capacity; a 137 should give 130; 235 total. BUT as I remember, my Series 1 uses a little bit less space for the software. So.... you're right on the edge.

Since you used Xtreme, you should have bash working. Get or make a serial cable and from a bash prompt, type in 'pdisk -l'. That should show you how each drive is partitioned, and you can figure it out. (If you have about 15% of the 160 GiB drive unused, you're safe).

PlainBill

[captain_video]

There should be no problem with your setup so don't panic. Linux will only recognize 137GB of your 160GB drive so it will never completely fill up unless you install the LBA48 hack that will allow the Tivo to recognize drives >137GB.

I hope you installed 2.5Xtreme and then upgraded to 2.5.2 instead of using the 2.5.2Xtreme image. The upgrade will install Superzap's excellent xPlusz suite of hacks whereas the 2.5.2Xtreme image doesn't give you much more than a bash prompt.

While it may seem logical that the A drive will fill up first and then the B drive, I have been told that this is not quite the case. Apparently, the Tivo will pretty much place the recordings where it pleases and they can end up on either drive. I don't know the details behind this so take it with a grain of salt until someone more knowledgeable can shed some light on the subject.

[kulmak]

Ok, thanks for the info. As for how I got there, yes I used a 2.5Xtreme ISO then upgraded to 2.5.2 with XPlus.

I was unsure about what would happen because I started reading how if you used larger drives then 140 and did not use the LBA48 hack you would have probs when you ran out of space.

Glad to hear that I should be good to go.

Thanks