LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This 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


Reply
  Search this Thread
Old 05-03-2015, 05:50 PM   #61
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled

That command does not print out anything.
 
Old 05-03-2015, 05:52 PM   #62
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
My version of blkid is very old, maybe that explains.
blkid 1.0.0 (12-Feb-2003)
 
Old 05-03-2015, 05:54 PM   #63
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, SLES, CentOS, Red Hat
Posts: 2,385

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
Try this and see if that helps:

Code:
file -sL /dev/mapper/VolGroup00-LogVol02
 
Old 05-03-2015, 05:56 PM   #64
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
Hmm, very strange. It produced:
/dev/mapper/VolGroup00-LogVol02: DOS executable (device driver) for DOS
 
Old 05-03-2015, 06:04 PM   #65
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, SLES, CentOS, Red Hat
Posts: 2,385

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
I was expecting it to return ext3 but the output is something unexpected. I have no idea what to try with this. Did you perform mkfs anytime after removing it from LV? Not sure how can ext3 fs can turn into DOS. I have tried file command on my RHEL 6 and the output shows me the file system with which it is formatted. May be because F10 is quite old file command not showing the correct output but cannot for sure.
 
Old 05-03-2015, 06:13 PM   #66
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
I was expecting anything else but DOS. As I told, I've tried to find a file system in this disk with e.g. Testdisk. I wonder if it can cause something like this. Otherwise I have refused to write on this disk with any program other than Gparted. I have written an LVM flag sometimes on the disk, just because I had no other idea.
 
Old 05-03-2015, 06:24 PM   #67
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, SLES, CentOS, Red Hat
Posts: 2,385

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
I am out of ideas for now, I am away from my test system and cannot say for sure what you could try. The message:

Code:
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
I got yesterday during testing but that was because I have done vgcfgrestore incorrectly. Once I figured it out it went fine. I would suggest you to recheck the steps that you have performed so far.

---------- Post added 05-04-15 at 04:55 ----------

Another thing you can try to see if you get more information is:

Code:
file -sL /dev/sdb1
This will give you UUID information.
 
Old 05-03-2015, 06:31 PM   #68
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
Don't worry, you have also helped me a lot! I will check my commands.
That file command returned:
/dev/sdb1: LVM2 (Linux Logical Volume Manager) , UUID: sb4SLylaOqJGaXzctrmtkJ9Zfb23gPU

as promised.
 
Old 05-03-2015, 06:41 PM   #69
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
The graphical LVM interface allows me to edit the properties of a Logical Volume. It also shows that this volume has no file system. I can select the file system and choose it to be mounted and/or mounted at boot and name the mount point. I suppose this edit would format the disk again and edit fstab? I cannot be sure if I have anything left on this disk, but this would make sure there isn't anything. I will not do it.
 
Old 05-03-2015, 06:44 PM   #70
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,786

Rep: Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216
Also, let's see the contents of /etc/lvm/backup/VolGroup00. Hopefully, it matches the archived metadata that you posted earlier. [EDIT] That's aside from differences in device names.

Another bit of useful information would be the output from
Code:
file -sk /dev/mapper/VolGroup00-LogVol02

Last edited by rknichols; 05-03-2015 at 06:47 PM.
 
Old 05-03-2015, 06:55 PM   #71
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
This file command produced the same result as "file -sL", namely:
/dev/mapper/VolGroup00-LogVol02: DOS executable (device driver) for DOS

The current LVM conf in /etc/lvm/backup/VolGroup00 is:
# Generated by LVM2 version 2.02.39 (2008-06-27): Mon May 4 01:04:27 2015

contents = "Text Format Volume Group"
version = 1

description = "Created *after* executing 'vgchange -ay VolGroup00'"

creation_host = "localhost.localdomain" # Linux localhost.localdomain 2.6.27.41-170.2.117.fc10.x86_64 #1 SMP Thu Dec 10 10:36:29 EST 2009 x86_64
creation_time = 1430690667 # Mon May 4 01:04:27 2015

VolGroup00 {
id = "Yc5AQm-23OO-0Rs5-tw7R-HzdR-iOcy-K2e0Ev"
seqno = 10
status = ["RESIZEABLE", "READ", "WRITE"]
extent_size = 65536 # 32 Megabytes
max_lv = 0
max_pv = 0

physical_volumes {

pv0 {
id = "Husf13-G5Ed-wuuD-UBcI-6EjZ-zQnW-1EHdkm"
device = "/dev/sda2" # Hint only

status = ["ALLOCATABLE"]
dev_size = 487990440 # 232.692 Gigabytes
pe_start = 384
pe_count = 7446 # 232.688 Gigabytes
}

pv1 {
id = "sb4SLy-laOq-JGaX-zctr-mtkJ-9Zfb-23gPUB"
device = "/dev/sdb1" # Hint only

status = ["ALLOCATABLE"]
dev_size = 3907024002 # 1.81935 Terabytes
pe_start = 384
pe_count = 59616 # 1.81934 Terabytes
}
}

logical_volumes {

LogVol00 {
id = "OiJx9U-oSOX-vKVo-hTTM-BmMR-E4oi-7aPAMW"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 1

segment1 {
start_extent = 0
extent_count = 7350 # 229.688 Gigabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv0", 0
]
}
}

LogVol01 {
id = "psguY9-0QmF-S58p-Iowo-Sz1c-iQja-lW4pxj"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 1

segment1 {
start_extent = 0
extent_count = 95 # 2.96875 Gigabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv0", 7350
]
}
}

LogVol02 {
id = "apdg4m-EqzS-JNrz-4h9g-Yoc3-92S3-MdPzu3"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 2

segment1 {
start_extent = 0
extent_count = 1 # 32 Megabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv0", 7445
]
}
segment2 {
start_extent = 1
extent_count = 59616 # 1.81934 Terabytes

type = "striped"
stripe_count = 1 # linear

stripes = [
"pv1", 0
]
}
}
}
}
 
Old 05-03-2015, 07:23 PM   #72
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,786

Rep: Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216Reputation: 2216
It certainly looks like the LV got reassembled properly. Let's see what is actually in there. Post the output from
Code:
dd if=/dev/mapper/VolGroup00-LogVol02 count=5 | hexdump -C
If you somehow don't have hexdump installed, an acceptable substitute would be
Code:
dd if=/dev/mapper/VolGroup00-LogVol02 count=5 | od -tx1z

Last edited by rknichols; 05-03-2015 at 07:24 PM.
 
Old 05-03-2015, 07:28 PM   #73
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
I studied a little the graphical interface of LVM. The physical view shows this SATA disk has 59616 total physical extents. Then there is a choice available to Migrate Selected Extent(s) From Volume. What does that do?
 
Old 05-03-2015, 07:31 PM   #74
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
I have hexdump. So the output is:
00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000040 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000400 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000a00
5+0 records in
5+0 records out
2560 bytes (2.6 kB) copied, 0.0328495 s, 77.9 kB/s

Looks pretty empty to me.
 
Old 05-03-2015, 07:36 PM   #75
vpp
Member
 
Registered: Apr 2015
Posts: 62

Original Poster
Rep: Reputation: Disabled
I afraid I need to remove this SATA disk again from the LVM to be able to boot next time. It is already late here. I gather we can get to this same state easily now?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LVM issue circus78 Linux - Server 5 12-12-2014 01:32 AM
LVM issue call_krushna Linux - Virtualization and Cloud 0 10-30-2012 10:58 AM
LVM issue AndyD236 Linux - General 2 11-24-2009 07:26 AM
LVM Issue bondoq Linux - General 8 05-12-2009 09:35 AM
LVM issue pauloco Linux - Hardware 1 11-14-2006 11:13 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 01:19 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration