DBSTalk Forum banner
1 - 15 of 15 Posts

· AllStar
Joined
·
61 Posts
Discussion Starter · #1 ·
I've been following the instructions on upgrading my (owned!) HR24-200. I'm booted into Ubuntu and have installed all neccessary tools. I have 4 bays for HD's, so I'm using sda for the new 2TB drive, and sdb for the old 500GB drive with my old material on it.

I've gotten to this place in the instructions:

Type mkdir /mnt/fap
Type mkdir /mnt/hr24
Type mount -t xfs -o rtdev=/dev/sda3 /dev/sda2 /mnt/fap
Type mount -t xfs -o rtdev=/dev/sdb3 /dev/sdb2 /mnt/hr20
Type xfsdump -J - /mnt/hr20 | xfsrestore -J - /mnt/fap

At this point, I'm getting this output:

xfsdump: WARNING: write to stdio failed: 32 (Broken pipe)
xfsdump: ending media file
xfsdump: media file size 18874368 bytes
xfsdump: dump size (non-dir files) : 13698056 bytes
xfsdump: NOTE: dump interrupted: 16 seconds elapsed
xfsdump: Dump Status: INTERRUPT

And it's now just sitting there. Should I stop it? What did I do wrong?
 

· Registered
Joined
·
16,423 Posts
That seems more like one of, if not both, of the drives were not removed at the proper time from the unit. You can't remove them after an RBR. You have to do a menu reboot and pull the power from the unit at the moment the front panel lights go out or the drive is locked.
 

· AllStar
Joined
·
61 Posts
Discussion Starter · #4 ·
I did. I made sure of it each time.

But I'll try it again for each drive and let you know.

Here's an updated version of my output. It's now saying I need to use the -R option. But I don't know where to use it:

[email protected]:~# mount -t xfs -o rtdev=/dev/sda3 /dev/sda2 /mnt/fap
[email protected]:~# mount -t xfs -o rtdev=/dev/sdb3 /dev/sdb2 /mnt/hr20
[email protected]:~# xfsdump -J - /mnt/hr20 | xfsrestore -J - /mnt/fap
xfsrestore: using file dump (drive_simple) strategy
xfsrestore: version 3.1.1 (dump format 3.0)
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 3.1.1 (dump format 3.0)
xfsdump: level 0 dump of jeffrey-MacPro:/mnt/hr20
xfsdump: xfsrestore: ERROR: -R option required to resume or -Q option required to force completion of previously interrupted restore session
xfsrestore: Restore Status: ERROR
dump date: Tue Nov 20 10:33:17 2012
xfsdump: session id: 6142d59d-e808-42de-99b6-044ab1594f18
xfsdump: session label: ""
xfsdump: ino map phase 1: constructing initial dump list
xfsdump: ino map phase 2: skipping (no pruning necessary)
xfsdump: ino map phase 3: skipping (only one dump stream)
xfsdump: ino map construction complete
xfsdump: estimated dump size: 450384360768 bytes
xfsdump: creating dump session media file 0 (media 0, file 0)
xfsdump: dumping ino map
xfsdump: dumping directories
xfsdump: WARNING: write to stdio failed: 32 (Broken pipe)
xfsdump: ending media file
xfsdump: media file size 0 bytes
xfsdump: dump size (non-dir files) : 0 bytes
xfsdump: NOTE: dump interrupted: 13 seconds elapsed
xfsdump: Dump Status: INTERRUPT
 

· AllStar
Joined
·
61 Posts
Discussion Starter · #10 ·
CCarncross said:
Is this the exact same distro you were running a few years ago and the same Mac Pro? I'm sure there is way to find a pc and use the gparted boot disk. Everyone has at least one pc.
No. That distro was erased when the drive it was on needed repair. But yes, it's the same Mac Pro.

I'm out in the middle of nowhere. I'm afraid I don't have any access to a PC.
 

· AllStar
Joined
·
61 Posts
Discussion Starter · #11 ·
CCarncross said:
You do need to go through the graceful shutdown procedure for each drive again. I also highly recommend using an older version of gparted as I pointed out above.
I reformatted the new drive to free space, allowed the unit to reformat the drive on startup. Brought it fully up and functioning, then gracefully shut down the unit. I then replaced the original drive, again booted the unit and allowed it to come fully up, then gracefully shut down the unit.

I also trashed the /mnt/fap and /mnt/hr20 directories and started from scratch.

The INTERRUPT error is still happening.
 
1 - 15 of 15 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top