Trying to do a full disk restore on an IBM 3200 M3 with an LSI M5015 controller. When I go to restore the partition I get the following errors when restoring the partition table. Any ideas on the issue? I have restored this image to other machines without a problem.
Restoring the primary GPT to /dev/sda…
34+0 records in
34+0 records out
17408 bytes (17kB) copied, 0.00427887 s, 4.1 MB/s
Restoring the secondary GPT to /dev/sda…
dd: `/dev/sda': cannot seek: Invalid arguement
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.001422 s, 0.0 kB/s
Informing kernel that the OS that partition table has changed…
Error: Invalid argument during seek for read on /dev/sda
The disk and partitions in this system now:
*******************************************************************.
Error: Invalid argument during seek for read on /dev/sda
*******************************************************************.
Restoring partition /dev/sda1…
Unable to find target partition "sda1"!!!
*******************************************************************.
The disk and partition in this system:
major minor #blocks name
7 0 113284 loop0
8 0 487304192 sda
*************************************************.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looks like it's a RAID card there? Sometimes the RAID device won't have device name /dev/sda…
Did you restore the image on the same machine?
Was the image saved on a machine with a RAID card?
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay…I was out of town for a few days and wasn't able to get the email for monitoring!
Here is the output…the /dev/sda is there.
root@debian:~# cat /proc/partitions
major minor #blocks name
7 0 113284 loop0
8 0 487304192 sda
root@debian:~# parted -s /dev/sda print
Error: Invalid argument during seek for read on /dev/sda
root@debian:~#
There aren't any partitions on the disk:
root@debian:~# ls -l /dev/sd*
brw-rw--- 1 root disk 8, 0 2011-02-07 10:09 /dev/sda
I did capture the image using a RAID card although the model has changed slightly. The image contains a compatible driver. But the issue appears to be having the kernel recognize the RAID card. It shows the device but the device appears to be read only and not rw. When I go into parted and print it manually, here is the output:
(parted) print
Error: Invalid argument during seek for read on /dev/sda
Retry/Ignore/Cancel? i
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel?
OK/Cancel? ok
Backtrace has 8 calls on stack:
8: /lib/libparted.so.0(ped_assert+0x2a)
7: /lib/libparted.so.0(+0x4972c)
6: /lib/libparted.so.0(ped_disk_new+0x75)
5: parted()
4: parted(interactive_mode+0x11a)
3: parted(main+0x9c)
2: /lib/libc.so.6(__libc_start_main+0xe7)
1: parted()
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
It looks like it could be a driver issue even though it uses the megaraid_s. Here was the interesting post:
Good news for those IBM 3650 M2 with LSI ServeRaid M5015 owners. I have made a newer megaraid_s as driver, v04.17, compiled it using DDK and made a public driver repository that can be used during installati on. Driver can be found from address: http://downl oad.netserva nt.fi/megara id/ , that address can be used during XenServer installati on wizard's Load module as modules address. no need to
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the rest of the items I've put in this post are not on the mark. I've noticed that once I manually create a GPT label on the disk using parted then I can create all the partitions. I believe the problem actually resides with something around EFI and the partition tabel. It seems like the errors are around creating the GPT label and the partition tabel. Once the partition table is created, partclone has no problem restoring the partition.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used the expert mode to manually create the partitions (created GPT label, and then 3 ntfs partitions) and then was able to restore the disk. Any additional information I can pull to help with this issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After manually creating the partitions and restoring the images, I was able to recapture the disk, manually delete all the partitions, and then the restore worked fine. I suspect this RAID card was just enough different to cause the problem with the restore process.
It appears the issue was caused by the RAID card. Thanks for your help!
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying to do a full disk restore on an IBM 3200 M3 with an LSI M5015 controller. When I go to restore the partition I get the following errors when restoring the partition table. Any ideas on the issue? I have restored this image to other machines without a problem.
Restoring the primary GPT to /dev/sda…
34+0 records in
34+0 records out
17408 bytes (17kB) copied, 0.00427887 s, 4.1 MB/s
Restoring the secondary GPT to /dev/sda…
dd: `/dev/sda': cannot seek: Invalid arguement
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.001422 s, 0.0 kB/s
Informing kernel that the OS that partition table has changed…
Error: Invalid argument during seek for read on /dev/sda
The disk and partitions in this system now:
*******************************************************************.
Error: Invalid argument during seek for read on /dev/sda
*******************************************************************.
Restoring partition /dev/sda1…
Unable to find target partition "sda1"!!!
*******************************************************************.
The disk and partition in this system:
major minor #blocks name
7 0 113284 loop0
8 0 487304192 sda
*************************************************.
Looks like it's a RAID card there? Sometimes the RAID device won't have device name /dev/sda…
Did you restore the image on the same machine?
Was the image saved on a machine with a RAID card?
Steven.
BTW, when you see those errors, please run the following commands:
1. cat /proc/partitions
2. sudo parted -s /dev/sda print
then post the results.
Steven.
Sorry for the delay…I was out of town for a few days and wasn't able to get the email for monitoring!
Here is the output…the /dev/sda is there.
root@debian:~# cat /proc/partitions
major minor #blocks name
7 0 113284 loop0
8 0 487304192 sda
root@debian:~# parted -s /dev/sda print
Error: Invalid argument during seek for read on /dev/sda
root@debian:~#
There aren't any partitions on the disk:
root@debian:~# ls -l /dev/sd*
brw-rw--- 1 root disk 8, 0 2011-02-07 10:09 /dev/sda
I did capture the image using a RAID card although the model has changed slightly. The image contains a compatible driver. But the issue appears to be having the kernel recognize the RAID card. It shows the device but the device appears to be read only and not rw. When I go into parted and print it manually, here is the output:
(parted) print
Error: Invalid argument during seek for read on /dev/sda
Retry/Ignore/Cancel? i
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel?
OK/Cancel? ok
Backtrace has 8 calls on stack:
8: /lib/libparted.so.0(ped_assert+0x2a)
7: /lib/libparted.so.0(+0x4972c)
6: /lib/libparted.so.0(ped_disk_new+0x75)
5: parted()
4: parted(interactive_mode+0x11a)
3: parted(main+0x9c)
2: /lib/libc.so.6(__libc_start_main+0xe7)
1: parted()
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (2.3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Assertion (last_usable <= disk->dev->length) at
../../../libparted/labels/gpt.c:934 in function _parse_header() failed.
Aborted
I found this post that talks about a related issue with Xen and ESX.
http://boardreader.com/thread/Problem_installing_XenServer_5_5_to_IBM_5wi43X5ikn.html
It looks like it could be a driver issue even though it uses the megaraid_s. Here was the interesting post:
Good news for those IBM 3650 M2 with LSI ServeRaid M5015 owners. I have made a newer megaraid_s as driver, v04.17, compiled it using DDK and made a public driver repository that can be used during installati on. Driver can be found from address: http://downl oad.netserva nt.fi/megara id/ , that address can be used during XenServer installati on wizard's Load module as modules address. no need to
I think this may be related:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547183
I think the rest of the items I've put in this post are not on the mark. I've noticed that once I manually create a GPT label on the disk using parted then I can create all the partitions. I believe the problem actually resides with something around EFI and the partition tabel. It seems like the errors are around creating the GPT label and the partition tabel. Once the partition table is created, partclone has no problem restoring the partition.
I used the expert mode to manually create the partitions (created GPT label, and then 3 ntfs partitions) and then was able to restore the disk. Any additional information I can pull to help with this issue?
After manually creating the partitions and restoring the images, I was able to recapture the disk, manually delete all the partitions, and then the restore worked fine. I suspect this RAID card was just enough different to cause the problem with the restore process.
It appears the issue was caused by the RAID card. Thanks for your help!
Rob
OK, if you find anything new, please post it again.
Thanks.
Steven.