Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks guys! I need to save these instructions, really helpful!
First of all, here's the output pvscan:
PV /dev/sda2 VG VolGroup00 lvm2 [232.69 GB / 32.00 MB free]
Total: 1 [232.69 GB] / in use: 1 [232.69 GB] / in no VG: 0 [0 ]
For me this appears LVM does not see the big SATA in any way.
Secondly, to follow the instruction of using pvcreate, I need to find out the uuid of that big SATA at the time it was in LVM or right now?
And thirdly, I need to check the BIOS options for SATA disks. At least this one is easy for me!
For me this appears LVM does not see the big SATA in any way.
It saw the first time right? You mentioned that you moved that data to big SATA disk and that is what you are trying to recover. I am not sure what you mean by this?
Quote:
Secondly, to follow the instruction of using pvcreate, I need to find out the uuid of that big SATA at the time it was in LVM or right now?
I think this is the UUID for your big SATA disk:
Code:
pv1 {
id = "sb4SLy-laOq-JGaX-zctr-mtkJ-9Zfb-23gPUB"
device = "/dev/sda1" # Hint only
And thirdly, I need to check the BIOS options for SATA disks. At least this one is easy for me!
I thought pvscan would mention the SATA disk, if it sees it. But of course, since it has been removed, why should the command mention it. It is just that I am not too familiar with these commands.
Ok, can I see the current uuid with some command?
I checked the BIOS and there two settings I am not sure...
"Extended IDE drive [Auto]"
"Access Mode [Auto]"
These are current settings. The other option is "Disabled".
The UUID (which is the same as I posted in my instructions) comes from the archived VolGroup00 metadata that you posted (Thank you for that, BTW.) back in #10.
The partition does not currently have a UUID, since the PV header was wiped by pvremove. That is why you have to identify the device (very carefully) by its /dev/xxxx name. The UUID is just to tell pvcreate which entry to use from that metadata.
The BIOS settings in question would be for SATA ports. If those are on an add-on card rather than on the motherboard, then you would have to find out how to access the settings for that card.
I suppose I have to arrange everything so that the device name would be the same as in that LVM config file in question?
It doesn't matter, but you do have to use the current device in place of that red "{X}" in my instructions (along with the correct path to the archive file, of course). Whatever device you specify is going to get a PV header written to it, so be sure it's right. You will get a warning that the device does not currently have a PV header. Of course not -- you wiped it. Enter the requested uppercase "YES" at that prompt.
Quote:
How about when and if this pvcreate command succeeds, what is the next step to get the disk visible?
The next step would be the vgcfgrestore command that I gave:
Ok, now I again bumped against that same old issue of not being able to mount that disk:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol02,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg says:
VFS: Can't find ext3 filesystem on dev dm-2.
As if the disk has anyway been written over in some phase...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.