GSOD on new Drive

Advertisements

Hi Guys,

I had a failed drive so bought a new samsung 320GB and got hold of new lba48.bak image.

ran the restore command as listed in steveconrad's awesome guide.

Installed the cachecard drivers using the lba48 bootable cd.

Re-installed the drive into the tivo.

On boot up the cachecard was recognised and loaded correctly. However I got a GSOD after the final wait a few moments splash page.

Realised I had forgotten to run copykern so back to the PC to run that.

Ran successfully

but still getting the GSOD

Where am I going wrong?

Thanks,

 

So I have tried to simplify the problem.

Just in case the cachecard was causing an issue I ran the restore again and the copykern but did not install the cachecard drivers.

As before it shows the grey screen followed by the GSOD and then it reboots (not sure I mentioned the reboot in the first post but the behaviour is consistent)

Any help greatly appreciated,

Thanks

 

It probably would.....

but, I don't want to give up this early into my problems plus I am loathed to spend money if I can help it

I am going to try the normal tivo.bak rather than the lba48 see if that makes a difference.

Give a day or two and I am sure my resolve will weaken!

Thanks,

 

Advertisements

Ok.


I have tried a tivo.bak with a default kernel and run the copykern

All this completed successfully.

When I power on the tivo it GSOD after the Power Up and then the Wait a few moments screens. It then resets and boots again ad infinium.

So I have tried:

1. lba48 kernel with and without cachecard drivers and cache card (have the bleeding hands to prove it!)

2. default kernel without cachecard drivers but with cachecard.

I am using

restore -x -s 300 -zpi /mnt/dos/tivo/tivo.BAK /dev/hdc

I am using .BAK's sourced from 'a friend' wink wink

I am downloading them using firefox and downthemall to an XP laptop.

I am then scp'ing them to a suse share drive and restoring from that using mfstools 2.0

Any ideas

Thanks,

 

Thank you

So simple and yet so effective !!

I was following the guide which was for a drive smaller than the 274GB threshold so it didn't alter the blocksize.

Incidentally I am sure I saw a thread that said a MFStools bug had been fixed on the blocksize effect, and that the default of 2 (k?) would work. I cannot find the thread so I may have imagined it.

3 days hard slog worth it in the end. Would have been about an 30 mins with no blood if I had got it right first time

Thanks again