Skip to contentSkip to conversation

I've tried to get some support on this list about lvm

linux-lvm Hugh 4 participants 8 messages Sep 15, 2009 – Sep 22, 2009

lore
Share & tools
lore

Hugh

author
#0 lore raw

but I've had no responses.
I'm sure I've discovered a bug but nobody has answered my question of offered any advice or requested any further information.
Please look at my problem and see if there is anything which might help me.
This is the url:
http://forums.fedoraforum.org/showthread.php?p=1263530

I'll post it here too so that if for some reason you can't access the forum:

device-mapper: reload ioctl failed: Invalid argument Failed to
suspend LogVol00
I hope this is the right forum.
I've read hundreds of threads on this problem but they seem to be intermittent and the resolution has been using a different kernel version.
I'm using the latest kernel but I still have this problem [root@fc11-64 ~]# rpm -q kernel kernel-2.6.29.6-217.2.8.fc11.x86_64
[root@fc11-64 ~]# rpm -qa | grep lvm lvm2-2.02.48-2.fc11.x86_64 system-config-lvm-1.1.9-1.fc11.noarch

[root@fc11-64 ~]# lvresize -v -d -L 65.9375G /dev/VolGroup00/LogVol00
Finding volume group VolGroup00
Archiving volume group "VolGroup00" metadata (seqno 5). Extending logical volume LogVol00 to 65.94 GB Found volume group "VolGroup00"
Found volume group "VolGroup00"
Loading VolGroup00-LogVol00 table
device-mapper: reload ioctl failed: Invalid argument Failed to suspend LogVol00
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 6).

[root@fc11-64 ~]# lvextend -v -d -L 65.9375G /dev/VolGroup00/LogVol00
Finding volume group VolGroup00
Archiving volume group "VolGroup00" metadata (seqno 5). Extending logical volume LogVol00 to 65.94 GB Found volume group "VolGroup00"
Found volume group "VolGroup00"
Loading VolGroup00-LogVol00 table
device-mapper: reload ioctl failed: Invalid argument Failed to suspend LogVol00
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 6).

Running Logical Volume Manager gui and attempting to extend the volume results in the same error.

[root@fc11-64 ~]# pvdisplay
--- Physical volume ---
PV Name /dev/sdb2
VG Name VolGroup00
PV Size 67.93 GB / not usable 24.13 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 2173
Free PE 640
Allocated PE 1533
PV UUID eCuGyH-jV7L-Tgdg-JyYW-sWK1-ehZY-OLw0WS
</cut>

[root@fc11-64 ~]# vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 67.91 GB
PE Size 32.00 MB
Total PE 2173
Alloc PE / Size 1533 / 47.91 GB
Free PE / Size 640 / 20.00 GB
VG UUID 7I9mBS-xzMJ-L1fC-7IT4-ckJq-g8r3-pv333k
</cut>

[root@fc11-64 ~]# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID ph5nOV-3cyI-fFNV-WlyQ-rDI8-dTsY-5FcWn2
LV Write Access read/write
LV Status available

# open 0
LV Size 1.97 GB
Current LE 63
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
</cut>

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID ZGiTvh-XhRo-sLk5-bkJX-U30G-xkCD-rYszvt
LV Write Access read/write
LV Status available

# open 0
LV Size 45.94 GB
Current LE 1470
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
</cut>

[root@fc11-64 ~]# tail -3 /var/log/messages

Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18 
too small for target
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: 253:3: 
linear: dm-linear: Device lookup failed
Sep 10 20:55:46 fc11-64 kernel: device-mapper: ioctl: error adding 

target to table

[root@fc11-64 ~]# fdisk -l

Disk /dev/sda: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d4599

Device Boot Start End Blocks Id System
/dev/sda1 * 1 26 204800 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 26 13054 104651423+ 8e Linux LVM

Disk /dev/sdb: 73.0 GB, 73014444032 bytes
255 heads, 63 sectors/track, 8876 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd426be2d

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 9 72261 83 Linux
/dev/sdb2 10 6266 50259352+ 8e Linux LVM

Disk /dev/dm-0: 102.9 GB, 102965968896 bytes
255 heads, 63 sectors/track, 12518 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 2113 MB, 2113929216 bytes
255 heads, 63 sectors/track, 257 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

Disk /dev/dm-3: 49.3 GB, 49325015040 bytes
255 heads, 63 sectors/track, 5996 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-3 doesn't contain a valid partition table

Anybody know what the problem is?
TIA,
Hugh

#1 lore raw
Quoted 2 lines · Hugh
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18 

too small for target

There's your answer: You're trying to make it bigger than the underlying device.

Use pvs -v to check device sizes for discrepancies. (--units s if necessary).

Alasdair

author
#2 lore raw
Quoted 11 lines · On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
Quoted 2 lines · Hugh
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18

too small for target

There's your answer: You're trying to make it bigger than the underlying device.

Use pvs -v to check device sizes for discrepancies. (--units s if necessary).

Alasdair

Thanks, now I can see what the problem is:

[root@fc11-64 ~]# pvs -v
Scanning for physical volume names

  PV         VG         Fmt  Attr PSize  PFree  DevSize PV UUID                               
  /dev/sda2  vg_fc1164  lvm2 a-   99.80G     0   99.80G qunnek-OG2y-hp2j-31J8-

J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G eCuGyH-jV7L-Tgdg-JyYW-
sWK1-ehZY-OLw0WS

How is this possible?
What's the solution?
How can I grow the DevSize?
Probably a better question to ask is, how can I add the unused space into the device and then the volume?

Maybe I should provide some more background.
I have a vmware virtual disk and I have grown the disk size by 20G.

[root@fc11-64 ~]# parted -l
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type     File system  Flags
 1      32.3kB  210MB  210MB  primary  ext3         boot 
 2      210MB   107GB  107GB  primary               lvm  

Model: VMware, VMware Virtual S (scsi)
Disk /dev/sdb: 73.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  74.0MB  74.0MB  primary  ext3         boot 
 2      74.0MB  51.5GB  51.5GB  primary               lvm  

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  49.3GB  49.3GB  ext3              

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2114MB  2114MB  linux-swap        

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  4194MB  4194MB  linux-swap        

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_root: 103GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  103GB  103GB  ext3              
#3 lore raw
Quoted 27 lines · Hugh
Quoted 5 lines · On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
Quoted 3 lines · Hugh
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18

too small for target

Quoted 8 lines

There's your answer: You're trying to make it bigger than the underlying device.

Use pvs -v to check device sizes for discrepancies. (--units s if necessary).

Alasdair

Thanks, now I can see what the problem is:

[root@fc11-64 ~]# pvs -v
Scanning for physical volume names

  PV         VG         Fmt  Attr PSize  PFree  DevSize PV UUID                               
  /dev/sda2  vg_fc1164  lvm2 a-   99.80G     0   99.80G qunnek-OG2y-hp2j-31J8-

J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G eCuGyH-jV7L-Tgdg-JyYW-
sWK1-ehZY-OLw0WS

Quoted 6 lines

How is this possible?
What's the solution?
How can I grow the DevSize?
Probably a better question to ask is, how can I add the unused space into the device and then the volume?

Hi Hugh,
taking into account this:

Quoted 3 lines

Maybe I should provide some more background.
I have a vmware virtual disk and I have grown the disk size by 20G.

and...

Quoted 11 lines

[root@fc11-64 ~]# parted -l
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type     File system  Flags
 1      32.3kB  210MB  210MB  primary  ext3         boot 
 2      210MB   107GB  107GB  primary               lvm  
Quoted 6 lines

Model: VMware, VMware Virtual S (scsi)
Disk /dev/sdb: 73.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

...this:

Quoted 5 lines
Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  74.0MB  74.0MB  primary  ext3         boot 
 2      74.0MB  51.5GB  51.5GB  primary               lvm  

you have to resize sdb2 partition first.

Though I do not understand why it is possible to resize PV beyond end of device (doing that should display a warning message, but command will pass), this is definitely not a LVM bug.

HTH,

-- Marian

Quoted 42 lines

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  49.3GB  49.3GB  ext3              

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2114MB  2114MB  linux-swap        

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  4194MB  4194MB  linux-swap        

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_root: 103GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  103GB  103GB  ext3              

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

author
#4 lore raw
Quoted 112 lines · On Tuesday 22 September 2009 18:34:19 Marian Csontos wrote:
Quoted 24 lines · Hugh
Quoted 11 lines · On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
Quoted 2 lines · Hugh
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18

too small for target

There's your answer: You're trying to make it bigger than the underlying device.

Use pvs -v to check device sizes for discrepancies. (--units s if necessary).

Alasdair

Thanks, now I can see what the problem is:

[root@fc11-64 ~]# pvs -v
Scanning for physical volume names

  PV         VG         Fmt  Attr PSize  PFree  DevSize PV UUID
  /dev/sda2  vg_fc1164  lvm2 a-   99.80G     0   99.80G

qunnek-OG2y-hp2j-31J8- J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G
eCuGyH-jV7L-Tgdg-JyYW- sWK1-ehZY-OLw0WS

Quoted 5 lines

How is this possible?
What's the solution?
How can I grow the DevSize?
Probably a better question to ask is, how can I add the unused space into the device and then the volume?

Hi Hugh,

taking into account this:

Quoted 2 lines

Maybe I should provide some more background.
I have a vmware virtual disk and I have grown the disk size by 20G.

and...

Quoted 11 lines

[root@fc11-64 ~]# parted -l
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type     File system  Flags
 1      32.3kB  210MB  210MB  primary  ext3         boot
 2      210MB   107GB  107GB  primary               lvm
Quoted 4 lines

Model: VMware, VMware Virtual S (scsi)
Disk /dev/sdb: 73.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

...this:

Quoted 3 lines
Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  74.0MB  74.0MB  primary  ext3         boot
 2      74.0MB  51.5GB  51.5GB  primary               lvm

you have to resize sdb2 partition first.

Though I do not understand why it is possible to resize PV beyond end of device (doing that should display a warning message, but command will pass), this is definitely not a LVM bug.

HTH,

-- Marian

Quoted 36 lines

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  49.3GB  49.3GB  ext3

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2114MB  2114MB  linux-swap

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  4194MB  4194MB  linux-swap

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_root: 103GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  103GB  103GB  ext3
Quoted 5 lines

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Quoted 6 lines

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Thank Marian,

Any idea how to resize sdb2? It's lvm and maybe I could delete it and recreate it with fdisk but maybe it will break and everything will be lost.

Hugh

#5 lore raw
Quoted 5 lines · Hugh [[email protected]] wrote:

Any idea how to resize sdb2? It's lvm and maybe I could delete it and recreate it with fdisk but maybe it will break and everything will be lost.

Hugh

You should be able to use fdisk to delete the partition first and then create a new one with bigger size. MAKE SURE that the new partition's start sector is same as the old one.

Thanks, Malahal.

#6 lore raw
In reply to Hugh
Quoted 129 lines · Hugh
Quoted 119 lines · On Tuesday 22 September 2009 18:34:19 Marian Csontos wrote:
Quoted 26 lines · Hugh
Quoted 5 lines · On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
Quoted 3 lines · Hugh
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18

too small for target

Quoted 8 lines

There's your answer: You're trying to make it bigger than the underlying device.

Use pvs -v to check device sizes for discrepancies. (--units s if necessary).

Alasdair

Thanks, now I can see what the problem is:

[root@fc11-64 ~]# pvs -v
Scanning for physical volume names

  PV         VG         Fmt  Attr PSize  PFree  DevSize PV UUID
  /dev/sda2  vg_fc1164  lvm2 a-   99.80G     0   99.80G

qunnek-OG2y-hp2j-31J8- J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G
eCuGyH-jV7L-Tgdg-JyYW- sWK1-ehZY-OLw0WS

Quoted 6 lines

How is this possible?
What's the solution?
How can I grow the DevSize?
Probably a better question to ask is, how can I add the unused space into the device and then the volume?

Hi Hugh,

taking into account this:

Quoted 3 lines

Maybe I should provide some more background.
I have a vmware virtual disk and I have grown the disk size by 20G.

and...

Quoted 11 lines

[root@fc11-64 ~]# parted -l
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type     File system  Flags
 1      32.3kB  210MB  210MB  primary  ext3         boot
 2      210MB   107GB  107GB  primary               lvm
Quoted 5 lines

Model: VMware, VMware Virtual S (scsi)
Disk /dev/sdb: 73.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

...this:

Quoted 4 lines
Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  74.0MB  74.0MB  primary  ext3         boot
 2      74.0MB  51.5GB  51.5GB  primary               lvm

you have to resize sdb2 partition first.

Though I do not understand why it is possible to resize PV beyond end of device (doing that should display a warning message, but command will pass), this is definitely not a LVM bug.

HTH,

-- Marian

Quoted 36 lines

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol00: 49.3GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  49.3GB  49.3GB  ext3

Model: Linux device-mapper (dm)
Disk /dev/mapper/VolGroup00-LogVol01: 2114MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2114MB  2114MB  linux-swap

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_swap: 4194MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  4194MB  4194MB  linux-swap

Model: Linux device-mapper (dm)
Disk /dev/mapper/vg_fc1164-lv_root: 103GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  103GB  103GB  ext3
Quoted 6 lines

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Quoted 7 lines

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Quoted 3 lines

Thank Marian,

Any idea how to resize sdb2?

Easy. Just search web for:
linux resize partition

Or check these direct links:
command line GNU parted: http://www.gnu.org/software/parted/index.shtml
GNOME gparted: http://gparted.sourceforge.net/
KDE qtparted: ...

Quoted 3 lines

It's lvm and maybe I could delete it and recreate
it with fdisk but maybe it will break and everything will be lost.

Marian

Quoted 8 lines

Hugh

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

author
#7 lore raw
In reply to Alasdair G Kergon
Quoted 10 lines · On Tuesday 15 September 2009 21:49:39 Alasdair G Kergon wrote:
Quoted 2 lines · Hugh
Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18

too small for target

There's your answer: You're trying to make it bigger than the underlying device.

Use pvs -v to check device sizes for discrepancies. (--units s if necessary).

Quoted 8 lines

Alasdair

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

This makes no sense to me Alasdair.
This may be the error message but it defies explanation.
I still think there is something wrong with the lvm sine it's the one throwing the error and everything else seems normal.:
[root@fc11-64 ~]# pvs -v
Scanning for physical volume names

  PV         VG         Fmt  Attr PSize  PFree  DevSize PV UUID                               
  /dev/sda2  vg_fc1164  lvm2 a-   99.80G     0   99.80G qunnek-OG2y-hp2j-31J8-

J3HT-0Aye-3w2rMN
/dev/sdb2 VolGroup00 lvm2 a- 67.91G 20.00G 47.93G eCuGyH-jV7L-Tgdg-JyYW-
sWK1-ehZY-OLw0WS
[root@fc11-64 ~]# pvscan

  PV /dev/sdb2   VG VolGroup00   lvm2 [67.91 GB / 20.00 GB free]
  PV /dev/sda2   VG vg_fc1164    lvm2 [99.80 GB / 0    free]

Total: 2 [167.71 GB] / in use: 2 [167.71 GB] / in no VG: 0 [0 ]

Perhaps I just don't know how to interpret the output but it appears to be normal and I don't know what to do next.
I'm desperate to recover my old fc9 disk, any suggestions or step by step guides which might point out where I went wrong or what the actual problem might be?

Thank, Hugh