Back up failed at 2%

[ehr091]

Hello, I am new to this board and I have searched for an answer to my problem and I need help.
I have a series2 Hughes dtvio. I have a problem with mfstools.
Every time I start to back up my Tivo drive iget the folowing error.
backup failed : /mnt/dos/tivo.bak : bad address.
I am really stuck and I have tried monte and I still get stuck at the same place. What am I doing wrong? how do I get past this. I have a drive configurerd for fat32 and it should work but it crasheswhen I get to about 2% backed up.

[SR712]

Have you actually mounted the FAT32 drive under /mnt/dos/ first?

[ehr091]

yes I have. I am using the Hinsdale method

# mkdir /mnt/dos
# mount /dev/hda /mnt/dos

then
# mfsbackup -6so /mnt/dos/tivo.bak /dev/hdc

then it goes on to tell me the tivo drive has 1248mb compreesed and then crashes at 24 of 1248mb 1.87%

[hayreass]

yes I have. I am using the Hinsdale method

# mkdir /mnt/dos
# mount /dev/hda /mnt/dos

then
# mfsbackup -6so /mnt/dos/tivo.bak /dev/hdc

then it goes on to tell me the tivo drive has 1248mb compreesed and then crashes at 24 of 1248mb 1.87%

If you have your fat drive installed as primary master, try this instead

mkdir /mnt/dos
mount /dev/hda1 /mnt/dos 
mfsbackup -6so /mnt/dos/tivo.bak /dev/hdc

this of course assumes you have your tivo drive installed as Secondary Master

[ehr091]

I just tried the new instructions but I still get the same result. I must be missing something

[WRabbit8]

I just tried the new instructions but I still get the same result. I must be missing something

You are probably not really mounting your FAT32 partition. You need to know what partition it is on /dev/hda to get a sucessfull mount. What output are you getting when you "mount"? what does "df" show after you attempt to mount the partition?

If the FAT32 is primary partition 1, you will mount /dev/hda1.
If the FAT32 is primary partition 2, you will mount /dev/hda2.
If the FAT32 is an extended partition, you will mount /dev/hda5 (or higher).

It is likely you are not really mounting your FAT32 partition, and root is running out of space at 2%.

-WR

[ehr091]

ok this is what I get when I type df

/dev/hda1 20023216 1 k blocks
U/A 24752/19998464
USE 0%
Mounted on /mnt/dos
I have tried Monte and I still get the same error

[ehr091]

Also, does the size of the fat32 drive matter? The tivo drive is 40 gigs and the fat32 drive is 20 gigs, would that have an effect?

[PlainBill]

Try this command: fdisk -l /dev/hda. This will report the partitions on /dev/hda. Post the results here.

PlainBill

[ehr091]

Ok PB, this is what I got back when I did fdisk on dev/hda

/dev/hda1 Start-1 End-2494 Blocks-20033023+ ID-c System win95a Fat32(lba).

[PlainBill]

Ok PB, this is what I got back when I did fdisk on dev/hda

/dev/hda1 Start-1 End-2494 Blocks-20033023+ ID-c System win95a Fat32(lba).

Thank you for presenting us with a unique problem. Your FAT32 partition is /dev/hda1; your command is correct. You say "It crashes". Please elaborate. Does it give an error message; lock up; reboot? I am inclined to think there is an error either on your FAT32 drive, or your TiVo drive.

PlainBill

[ehr091]

it just locks up. It shows me the amount of mb in total and how many kb it has transfered.

24 of 1449 (1.86%) and thats where it stops each time. it will not go any further. It will stop and then say that the tivo.bak file is an invalid address.
I have to manually reboot each time.
backup failed : /mnt/dos/tivo.bak : bad address

[PlainBill]

it just locks up. It shows me the amount of mb in total and how many kb it has transfered.

24 of 1449 (1.86%) and thats where it stops each time. it will not go any further. It will stop and then say that the tivo.bak file is an invalid address.
I have to manually reboot each time.
backup failed : /mnt/dos/tivo.bak : bad address

Please understand that we're out on the ragged edge of troubleshooting here. The last ideas I have are related to a drive problem. First, try running scandisk (including a surface scan) on the fat32 drive and see if it finds any problems. If that doesn't help, try using the manufacturer's diagnostic utility on the TiVo drive, and do a media scan (surface scan).

PlainBill