Tweet
I have followed the Tivo upgrade instructions to replace my existing
Series 1 Sony Tivo drive (30gb) to a new Maxtor Quickview (160gb)
drive. This went smoothly and Tivo seems be working fine.
In preparation for installing a network adapter I connected my new
Tivo drive to my PC (primary slave). I changed the jumper to slave
and booted with the Jenkins ISO. But for some reason I CANNOT
successfully mount the partitions: If I look at the boot messages
the partition types are hdb3, hdb6, hdb8 - Ext2. I believe these are
the partitions I need access to. Whenever I attempt to mount
these I get:
mkdir /mnt3
mount /dev/hdb3 /mnt3
==>
mount: you must specify the filesystem type.
I have tried all partitions and I have tried specifying a
filesystem type.
mount -t ext2 /dev/hdb3 /mnt3
==>
mount: wrong fs type, bad options, bad superblock on /dev/hdb3,
or too many mounted file systems
After scrolling up to the output of the boot process I noticed the
drive was reported as 10mb. I used the Weaknees process of
creating a boot floppy and using diskutil to unlock the drive. Now
the drive is recognized as 137gb but I still get the same messages
on mount.
Any ideas?
-Steve
Series 1 Sony Tivo drive (30gb) to a new Maxtor Quickview (160gb)
drive. This went smoothly and Tivo seems be working fine.
In preparation for installing a network adapter I connected my new
Tivo drive to my PC (primary slave). I changed the jumper to slave
and booted with the Jenkins ISO. But for some reason I CANNOT
successfully mount the partitions: If I look at the boot messages
the partition types are hdb3, hdb6, hdb8 - Ext2. I believe these are
the partitions I need access to. Whenever I attempt to mount
these I get:
mkdir /mnt3
mount /dev/hdb3 /mnt3
==>
mount: you must specify the filesystem type.
I have tried all partitions and I have tried specifying a
filesystem type.
mount -t ext2 /dev/hdb3 /mnt3
==>
mount: wrong fs type, bad options, bad superblock on /dev/hdb3,
or too many mounted file systems
After scrolling up to the output of the boot process I noticed the
drive was reported as 10mb. I used the Weaknees process of
creating a boot floppy and using diskutil to unlock the drive. Now
the drive is recognized as 137gb but I still get the same messages
on mount.
Any ideas?
-Steve
Comment