[Scott9mm]

SOLVED: Here is the bottom line. The entire problem was that I misread the command syntax and repeated that error over and over. The correct syntax is "/dev/sdX" but I repeatedly typed "/dev/sdx/". As soon as I typed the commands correctly, everything proceeded exactly as advertised.

I would add that I did NOT need to re-pair the cable card after using MFSTools to transfer and expand the 8T hard drive. In contrast. when I cloned a 1T Premiere+ drive to a 3T drive with a docking station and then expanded it using MSFTools I did need to repair the cable card.

Thanks to ClearToLand for spotting the extra "/" that screwed everything up. Thanks to jmbach for his troubleshooting assistance and his continued development of MFS Tools and detailed instructions for creating bigger TiVo drives. The TiVo community is great!

The details of my buffoonery follow below if anyone still cares.

---------------------------------------------------------------

I have a (lifetime) 2-tuner premiere with a 2T replacement hard drive I bought from Weaknees (when the original drive died). I planned to update it to 8T. I started using the instructions in the 8T Premiere post using MFSTools 3.3. I'm using a Sabrent USB docking station.

In response to the mfscopy command I get:

Copy Source: Input/output error reading volume header.
Copy Source: /dev/sdb/10: Not a directory.

Is there a problem with Weaknees hard drives that prevents upgrade via MSFTools?

Thanks for any help.
Scott

 

[jmbach]

I have (lifetime) 2-tuner premiere with a 2T replacement hard drive I bought from Weaknees (when the original drive died). I planned to update it to 8T. I started using the instructions in the 8T Premiere post using MFSTools 3.3. I'm using a Sabrent USB docking station.

In response to the mfscopy command I get:

Copy Source: Input/output error reading volume header.
Copy Source: /dev/sdb/10: Not or directory.

Is there a problem with Weaknees hard drives that prevents upgrade via MDFTools?

Thanks for any help.
Scott

It sounds like the source and target names may be switched in the command line.

Post screenshots of the command you are using and the output of "lsblk -o name,size" command.

Sent from my SM-G988U using Tapatalk

 

[Scott9mm]

It sounds like the source and target names may be switched in the command line.

Post screenshots of the command you are using and the output of "lsblk -o name,size" command.

Sent from my SM-G988U using Tapatalk

Thanks so much for your reply. I am sure the drives are not switched; in fact,I get the same result with only the source drive in the docking station. I am booting using MFSTools on a CD in a Windows notebook PC.

Question: How do I do a screenshot?

I thought there might be something wrong with the source drive data so, I tried a kickstart 58 on the source drive. That produced a "software updating" message on the screen that lasted for hours until I forced a restart (unplugging the power cord). Thinking a software update might be needed, i did a kickstart 56, which apparently reloaded the software but also "broke" the cable card pairing. Fortunately I had previously cloned the 2T source drive to an 8T drive which still boots with cable card pairing. So that 8T drive (with 2T capacity) is in the Premiere for now.

 

[jmbach]

Question: How do I do a screenshot?

Take picture with your phone of the screen.

Sent from my SM-G988U using Tapatalk

 

[jmbach]

I thought there might be something wrong with the source drive data so, I tried a kickstart 58 on the source drive. That produced a "software updating" message on the screen that lasted for hours until I forced a restart (unplugging the power cord). Thinking a software update might be needed, i did a kickstart 56, which apparently reloaded the software but also "broke" the cable card pairing. Fortunately I had previously cloned the 2T source drive to an 8T drive which still boots with cable card pairing. So that 8T drive (with 2T capacity) is in the Premiere for now.

A KS 58 can take as long as 3 hours to complete. The only other kickstart I would do is a 57 on a premiere.

Sent from my SM-G988U using Tapatalk

 

[Scott9mm]

Thanks, jmbach. I was overthinking the screenshot (trying to do digitally).

I think this link will show my screenshot.

Maybe I jumped the gun by killing the KS58 but it ran for some hours while the TV screen said it was "updating software" (no GSOD). The actual software reload was much faster and showed the same "updating software" TV screen.

 

[jmbach]

Thanks, jmback. I was overthinking the screenshot (trying to do digitally).

I think this link will show my screenshot.

Maybe I jumped the gun by killing the KS58 but it ran for some hours while the TV screen said it was "updating software" (no GSOD). The actual software reload was much faster and showed the same "updating software" TV screen.

The KS 58 does more than just reload/update the software, it is supposed to do some cleanup of the file system as well.

Sent from my SM-G988U using Tapatalk

 

[jmbach]

Does the drive still give you the same error?

Try running mfsinfo -d on the drive and post the output.

Sent from my SM-G988U using Tapatalk

 

[Scott9mm]

Does the drive still give you the same error?

Try running mfsinfo -d on the drive and post the output.

Sent from my SM-G988U using Tapatalk

Here's the link to new screen shot.

Also, I tried "mfsinfo -d /dev/sdb" and got the same input/output error message (/dev/sdb/10: Not a directory)

But this disk starts and runs fine in my TiVo Premiere

Can you recommend a good place to get the commands and options for mfstools?

Thanks.

 

[ClearToLand]

...In response to the mfscopy command I get:

Copy Source: Input/output error reading volume header.
Copy Source: /dev/sdb/10: Not a directory.

Why is there a slash after sdb?

mfscopy -aiM 4000 /dev/sdX /dev/sdY​

 

[jmbach]

Why is there a slash after sdb?

mfscopy -aiM 4000 /dev/sdX /dev/sdY​

Good catch. I overlooked it. That is likely the issue.

Sent from my SM-G988U using Tapatalk

 

[ClearToLand]

Here's the link to new screen shot.

Also, I tried "mfsinfo -d /dev/sdb" and got the same input/output error message (/dev/sdb/10: Not a directory)

No. According to both screen shots you're typing: "mfsinfo -d /dev/sdb/"

 

[ClearToLand]

...Can you recommend a good place to get the commands and options for mfstools?

IIRC, everything is at the beginning of the original MFS Tools 3 thread (first few posts).

 

[Scott9mm]

Good catch. I overlooked it. That is likely the issue.

Sent from my SM-G988U using Tapatalk

Many thanks to jmbach and ClearedToLand. That extra slash appears to be the whole problem.

This was a huge brain fart on my part!! Somehow I got it stuck in my head that there was a slash after the device name and I repeatedly saw what I thought was there vs what was actually there. I'd blame it on my ageing vision but I've always had a dyslexia thing, maybe it's just carelessness. It drove me nuts on college when we programmed in Algol, where punctuation plays big in the syntax. SWMBO says I cannot proofread and she is right.

mfscopy appears to be happily running now from the good clone (cablecard pairing intact) of the original 2T drive to a fresh 8T drive.

 

[Scott9mm]

IIRC, everything is at the beginning of the original MFS Tools 3 thread (first few posts).

Perfect. I just needed to find the right MFS Tools 3.2 thread, which wasn't the sticky thread at the top.