I bought two 320G Seagate drives from NewEgg ($94 each) and a TwinBreeze bracket from weaKnees. Followed the Hinsdale instructions, reinstalled the new drives in the TiVo and BAM - GSOD. Removed the 'B' drive and tried again. It came up fine. Hmmm.. bad drive? So I switched the 'B' drive to the 'A' postion and redid the backup/restore. Put it, by itself, in the TiVo and it ran fine. Reinstalled the previous 'A' drive as the new 'B' drive (using ANOTHER end-to-end backup/restore) and BAM - GSOD.
So I either have a bad TwinBreeze cable (doubtful, as I tried THREE different IDE cables - all new) or a bad Y-Power Cable (also doubtful as both drives spun up nicely) or mfsadd (mfsadd -x /dev/hdc /dev/hdb) is kaiboshing the new A/B combo for some reason. Drive jumpering has been verified MANY times.
Doesn't matter WHAT drive I use for the new, expanded 'A' drive, but as soon as I try to add a SECOND 320G drive, it barfs. I can live with 273 hours instead of 70 for a good long time, but I was REALLY looking forward to 600+ hours... It's running on a single 320G right now just fine.
Any ideas?
So I either have a bad TwinBreeze cable (doubtful, as I tried THREE different IDE cables - all new) or a bad Y-Power Cable (also doubtful as both drives spun up nicely) or mfsadd (mfsadd -x /dev/hdc /dev/hdb) is kaiboshing the new A/B combo for some reason. Drive jumpering has been verified MANY times.
Doesn't matter WHAT drive I use for the new, expanded 'A' drive, but as soon as I try to add a SECOND 320G drive, it barfs. I can live with 273 hours instead of 70 for a good long time, but I was REALLY looking forward to 600+ hours... It's running on a single 320G right now just fine.
Any ideas?
Comment