PDA

View Full Version : Can't mount factory Maxtor drive from SVR-2000


B1sh0p
06-09-2006, 03:43 PM
Hi,

I'm new to Tivo hacking, and can't seem to find an answer to this question even though I've searched and read as much as I can.

I have two Sony SVR-2000 Series 1 Tivos, one that is slightly older than the other. Each one was factory fresh when it was opened, and had never been hacked before. Last night I readied my two TurboNet cards from 9th Tee, and downloaded the Steve Jenkins Boot Disc and instructions, and started the process. Basically all I wanted to do was install TivoWebPlus. No storage upgrades, and I was going to do this on the existing drives in the Tivos. Both are single drive 30 hour models.

After hooking up the first drive to an old computer as master on IDE channel 2, I was able to boot using the default method and login as root, mkdir the mountpoints, and mount using the following command(s):

mount /dev/hdc4 /mnt4
mount /dev/hdc4 /mnt7
mount /dev/hdc4 /mnt9

Everything went great, and I was able to copy over the appropriate files and edit the Tivo to allow FTP and Telnet access. After that I hooked everything back up, FTP'ed some more files, installed it, and TivoWebPlus loaded fine. Great.

The problem is with Tivo #2. This unit is exactly the same as Tivo #1 (also an SVR-2000) but it has a Maxtor drive instead of a Quantum drive.

Booting the Jenkins disc using the same method, I was able to login, but after creating the mountpoint directories, mounting them never works.

Sometimes I will get:

mount /dev/hdc4 /mnt4
Success
mount: you must specify the filesystem type

If I type df at that point, the mount doesn't exist.

If I boot with some of the other boot methods on the Jenkins disc, I'll get:

mount /dev/hdc4 /mnt4
/dev/hdc4: Input/output error
mount: you must specify the filesystem type


This drive is detected fine in my Bios as the Master on IDE channel 2. I can tell it's detected in Linux from the boot messages that flash across the screen. I understand there may be DMA or Byteswapping issues, but I don't really understand what to do in order to make it work. Should I use a different boot command from the Jenkins CD? Should I use a different Bootdisc? I've tried installing the drive as Master on IDE channel 1 too, and get the same problems.

What do I need to do to mount this other drive? Why did it work the first time with the exact same setup, just using a Quantum drive instead?

Thanks for any help!!

funtoupgrade
06-09-2006, 07:00 PM
Is the drive locked at 10MB?

B1sh0p
06-09-2006, 09:03 PM
Well, it appears in my BIOS IDE Hard Drive Autodetection as being only 10MB, so I guess so. I thought the Jenkins disc automatically 'unlocked' locked drives?

funtoupgrade
06-09-2006, 09:37 PM
Do an internet search for diskutil.exe (much safer than qunlock) which can be downloaded and run in DOS to unlock your drive. You should then be able to proceed. Every time one of these drives is hooked up to the TiVo the drive is usually locked by the firmware on the motherboard.

technomutt
06-10-2006, 10:46 AM
just to add my 2 cents, as a rabid Sony Tivo fan...

I'm surprised your Quantum wasn't also "locked". Funtoupgrade is right on the money:Do an internet search for diskutil.exe (much safer than qunlock) which can be downloaded and run in DOS to unlock your drive. You should then be able to proceed. Every time one of these drives is hooked up to the TiVo the drive is usually locked by the firmware on the motherboard.Maxtor bought out Quantum some years ago, and this "locking" seems to occur only on these two brands of drives (they must have similar drive firmware). I've never seen it on others. I've been using Western Digitals in all of my Sonys, which work very well (and last longer) and Tivo never locks them.

Funtoupgrade, what's the danger in Qunlock? You obviously have more experience than I do... what can happen?

B1sh0p
06-11-2006, 10:33 AM
THANK YOU, unlocking the drive was it. The Jenkins document is misleading in this regard... he warns you to never try to unlock a drive that's already unlocked, and the boot CD is supposed to automatically do it, so I just dismissed locking as the culprit. Especially when the other drive worked fine without it!

Anyway, it's working fine now, and TivoWeb is running great!