tivosohn
07-07-2003, 05:07 PM
Please help. I did the following thing and got the following error. Not sure what I did wrong. Any help will be appreciated.
On my HDVR2, I restored the 3.1.0 images on the a WD 160 (8mb cache) drive and a WD 80. I ran the mfsadd -x /dev/hda /dev/hdb. Then I applied the Monte hack on the WD160 drive, which is the primary drive (hda). When I popped the drives into the Tivo, it boots up fine and finished acquiring the information from the satellite. After 5 minutes, I see the following information on my bash prompt screen. (I only paste partial of the repeated info:
...
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:09 (hda), sector 2186
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:09 (hda), sector 2188
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplL
...
Then it reboots itself and stuck on the Powering up screen and the following thing shows on the bash prompt :
Partition 6 signature is false, trying alternate
diskboot found partition 2 signature is false.
Ram size = 64
Service number is xxxxxxxxxxxxxxx.
What is password?
Then I pop the drives backing my PC and did a bootpage -p /dev/hda. It returns a wired string of something like this.
rnot=.ddv.hda6 BARH_........
Any idea what did I do wrong? If I only apply the Monte hack on the WD160 or WD80, things work flawlessly. But when I try to do a dual drive, thing starts to blow up.
On my HDVR2, I restored the 3.1.0 images on the a WD 160 (8mb cache) drive and a WD 80. I ran the mfsadd -x /dev/hda /dev/hdb. Then I applied the Monte hack on the WD160 drive, which is the primary drive (hda). When I popped the drives into the Tivo, it boots up fine and finished acquiring the information from the satellite. After 5 minutes, I see the following information on my bash prompt screen. (I only paste partial of the repeated info:
...
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:09 (hda), sector 2186
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:09 (hda), sector 2188
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplL
...
Then it reboots itself and stuck on the Powering up screen and the following thing shows on the bash prompt :
Partition 6 signature is false, trying alternate
diskboot found partition 2 signature is false.
Ram size = 64
Service number is xxxxxxxxxxxxxxx.
What is password?
Then I pop the drives backing my PC and did a bootpage -p /dev/hda. It returns a wired string of something like this.
rnot=.ddv.hda6 BARH_........
Any idea what did I do wrong? If I only apply the Monte hack on the WD160 or WD80, things work flawlessly. But when I try to do a dual drive, thing starts to blow up.