boot failed on 6.2

[scm]

I'm running an S2 D*vo on 6.2
bootpage -p showed "root=/dev/hda4"
I mfsbacked up and mfsrestored to a larger drive
ran tivopart for larger hda1
dd'd original root fs image to hda4
dd'd killhdinitrd'd 3.1.5 kernel to hda3
set bootpage -P "root=/dev/hda7 dsscon=true console=2,115200 upgradesoftware=false"
edited rc.sysinit.author for bash, telnet, ftp, enabled usb ports.
tried to boot in tivo got:

diskboot failed to verify written boot sector
Ram=64
...
over serial cable as tivo hangs at boot.
Can anyone shed some light on my problem?
Thanks

[hayreass]

Can anyone shed some light on my problem?
ThanksWell, it appears as though you dd'd to 3 and 4, yet you told it to boot from 7 (and I'll assume 6)

You need to set the boot parameters to boot from 4 and 3

Edit:
There's also the possibility that if you have everything dd'd to partition 7, you didn't edit /etc/fstab to reflect hda7.
I don't know what happens if you boot with fstab being incorrect.

Or it could be an error in running tivopart. I'm entirely unfamiliar with that process.

But based on what you said, I'd make sure the boot parameters pointed where they are supposed to first.

[scm]

Doh, I made a typo in my last post, it should have read:
set bootpage -P "root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false"
I checked it back on the pc and it says its booting from /dev/hda4
I had also dd'd a kernel and image to 6 and 7 respectively though too with the same results.

[PlainBill]

This still isn't right. It should read bootpage -P "root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" -C /dev/hda

Your original error "diskboot failed to verify written boot sector" indicates something is seriously wrong with the boot sector. It's time you gave us a little more information to work with - starting with how you copied the drive.

Standard troubleshooting process is to copy the drive, verify it boots, replace the kernel, verify it boots, add rc.sysinit.author, verify it boots, etc.

PlainBill

[scm]

This still isn't right. It should read bootpage -P "root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" -C /dev/hda

Your original error "diskboot failed to verify written boot sector" indicates something is seriously wrong with the boot sector. It's time you gave us a little more information to work with - starting with how you copied the drive.

Standard troubleshooting process is to copy the drive, verify it boots, replace the kernel, verify it boots, add rc.sysinit.author, verify it boots, etc.

PlainBill
Ok, so here was the process (assuming new tivo drive as secondary master)
after mfsbackup...
mfsrestore -s 2048 -bzpi /mnt/dos/tivo.bak /dev/hdc
was told not to try and boot this with such a large swap, but try and dd the root fs image before partitioning.
tried to dd image, but didn't work, couldn't mount anything so tried restoring normally.
mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdc
mfsadd -x /dev/hdc
put in tivo, booted ok.
pulled drive, put back in PC
mounted /dev/hdc4 ok
dd if=/dev/hdc4 of=/mnt/dos/tivoroot/hdc4.img
cd /
umount -f -a -r
mfsrestore -s 2048 -bzpi /mnt/dos/tivo.bak /dev/hdc
tivopart.x86 c /dev/hdc
mounted drives
dd if=/mnt/dos/tivoroot/hdc4.img of=/dev/hdc4
mke2fs /dev/hdc1
mount /dev/hdc4 /mnt/mnt4
cp /mnt/cdrom/s_2_kernels/3.1.5/vmlinux.px.gz /mnt/mnt4
cd /mnt/mnt4
gunzip -d -v vmlinux.px.gz
dd if=/mnt/mnt4/vmlinux.px of=/dev/hdc3
bootpage -P "root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" -C /dev/hdc
cp tivoftpd.mips /mnt/mnt4/var/hack
vi /mnt/mnt4/etc/rc.d/rc.sysinit.author to include usb drivers, bash, telnet, ftp
cd /mnt/mnt4/etc/rc.d
chmod 755 rc.sysinit.author
cd ..
mv netfilter-enable netfilter-notenabled
copied misc files to /dev/hdc1
then tried to boot on tivo - got said error
put drive back in PC
dd'd hdc4.img /dev/hdc7
dd'd vmlinux.px /dev/hdc6
tried booting in tivo again - same results