[linux-lvm] LVM inaccessible after OS reinstall

[linux-lvm] LVM inaccessible after OS reinstall

[Karl Stenerud]

I recently installed Mandrake 9.2 when I discovered my current linux 
install would not support my serial ATA card and drive.

After installing it, I decided to try out LVM.  I created a group using 4 
harddrives (using entire disk, no partitioning), set up a volume, and 
formatted it with reiserfs.
Actually I started with 1 volume on the empty drive, moved the data from a 
full drive over, prepped and added that drive etc.

Unfortunately, Mandrake sucks so bad that it fragged the menus on all 
desktops when I tried to run the system update, leaving me with no shell 
access and such.
I did the ctrl-alt-f8 to get to a console shell and copied my /etc 
directory to another drive, then proceeded to reinstall the OS 
(approximately 40 times before I figured out the magical incantations 
necessary to make it not blow up in my face).
Note that the OS iteself was not on an LVM (hda is a normal, partitioned 
disk). The LVM group is on hde, hdi, hdj, and hdk.

Now that I have Mandrake behaving itself (sort of), I want to mount the LVM 
group again.  Unfortunately I can't seem to get Linux to mount it without 
complaining about not being able to reach a certain sector =(

I activated the group, did a vgscan and pvscan which created the /dev 
entries and some /etc entries, but if I try to mount it (/dev/group1/vol1), 
it sits there and does nothing (I waited 40 minutes before giving up).
If I run fsck.reiserfs on it, it sits busy for about 5-10 minutes and then 
complains about not being able to reach a sector (along with a suggestion 
that my disk has an error on it).


[root@localhost etc]# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE   PV "/dev/ide/host4/bus1/target0/lun0/disc" of VG 
"group1" [74.47 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/ide/host4/bus0/target0/lun0/disc" of VG 
"group1" [93.28 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/ide/host4/bus0/target1/lun0/disc" of VG 
"group1" [149 GB / 0 free]
pvscan -- ACTIVE   PV "/dev/ide/host2/bus0/target0/lun0/disc" of VG 
"group1" [149 GB / 0 free]
pvscan -- total: 4 [465.95 GB] / in use: 4 [465.95 GB] / in no VG: 0 [0]

[root@localhost etc]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "group1"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume group

[root@localhost etc]# fsck.reiserfs /dev/group1/vol1
reiserfsck 3.6.10 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/group1/vol1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Mon Nov  3 09:17:04 2003
###########
Replaying journal..
0 transactions replayed

The problem has occurred looks like a hardware problem.
If you have bad blocks, we advise you to get a new hard
drive, because once you get one bad block that the disk
drive internals cannot hide from your sight, the chances
of getting more are generally said to become much higher
(precise statistics are unknown to us), and this disk drive
is probably not expensive enough for you to risk your time
and data on it. If you don't want to follow that advice,
then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that
means it takes a block it has in reserve and allocates it
for use for requests of that block number).  If it cannot
remap the block, this could be quite bad, as it may mean
that so many blocks have gone bad that none remain in
reserve to allocate.

bread: Cannot read the block (44171264): (Input/output error).

Aborted (core dumped)
[root@localhost etc]# 

Re: [linux-lvm] LVM inaccessible after OS reinstall

[Luca Berra]

On Mon, Nov 03, 2003 at 11:19:34PM +0900, Karl Stenerud wrote:
besides the rant, do you think providing more useful data
would result in people actually helping you?

did you roun vgchange -a y after vgscan?
can you provide a vgdisplay -v?
is there anything in syslog?
L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

Re: [linux-lvm] LVM inaccessible after OS reinstall

[Luca Berra]

uhm,
either there is a problem with the driver for your sata controller, or
your hdj is hosed.
could you test if you can read all of the disks with dd (keeping an eye
on syslog/dmesg)?

Regards,
L.

On Tue, Nov 04, 2003 at 11:06:32AM +0900, Karl Stenerud wrote:
>Sorry if that wasn't useful enough.  I'm not an expert on these commands 
>and the faq didn't seem to offer much assistance in this area.
>
>[root@localhost etc]# vgchange -a y
>vgchange -- volume group "group1" already active
>
>[root@localhost etc]# vgdisplay -v
>--- Volume group ---
>VG Name               group1
>VG Access             read/write
>VG Status             available/resizable
>VG #                  0
>MAX LV                256
>Cur LV                1
>Open LV               0
>MAX LV Size           2 TB
>Max PV                256
>Cur PV                4
>Act PV                4
>VG Size               465.75 GB
>PE Size               32 MB
>Total PE              14904
>Alloc PE / Size       14904 / 465.75 GB
>Free  PE / Size       0 / 0
>VG UUID               QnY93d-dypP-OLTs-5122-BVT4-4Zjk-wGY7rC
>
>--- Logical volume ---
>LV Name                /dev/group1/vol1
>VG Name                group1
>LV Write Access        read/write
>LV Status              available
>LV #                   1
># open                 0
>LV Size                465.75 GB
>Current LE             14904
>Allocated LE           14904
>Allocation             next free
>Read ahead sectors     1024
>Block device           58:0
>
>
>--- Physical volumes ---
>PV Name (#)           /dev/ide/host4/bus1/target0/lun0/disc (3)
>PV Status             available / allocatable
>Total PE / Free PE    2383 / 0
>
>PV Name (#)           /dev/ide/host4/bus0/target0/lun0/disc (4)
>PV Status             available / allocatable
>Total PE / Free PE    2985 / 0
>
>PV Name (#)           /dev/ide/host4/bus0/target1/lun0/disc (2)
>PV Status             available / allocatable
>Total PE / Free PE    4768 / 0
>
>PV Name (#)           /dev/ide/host2/bus0/target0/lun0/disc (1)
>PV Status             available / allocatable
>Total PE / Free PE    4768 / 0
>
>
>
>[root@localhost etc]#
>
>
>
>Here's part of syslog that shows something with reiserfs:
>
>Nov  3 08:04:55 localhost kernel: reiserfs: found format "3.6" with 
>standard journal
>Nov  3 08:04:59 localhost kernel: reiserfs: using ordered data mode
>Nov  3 08:04:59 localhost kernel: reiserfs: checking transaction log 
>(device ide0(3,3)) ...
>Nov  3 08:04:59 localhost kernel: for (ide0(3,3))
>Nov  3 08:05:00 localhost kernel: ide0(3,3):Using r5 hash to sort names
>Nov  3 08:08:10 localhost kernel: hdj: dma_timer_expiry: dma status == 0x61
>Nov  3 08:09:27 localhost kernel: hdj: dma_timer_expiry: dma status == 0x61
>Nov  3 08:12:43 localhost kernel: hdj: dma_timer_expiry: dma status == 0x61
>Nov  3 08:16:18 localhost last message repeated 2 times
>Nov  3 08:17:51 localhost kernel: hdj: dma_timer_expiry: dma status == 0x61
>Nov  3 08:18:01 localhost kernel: hdj: error waiting for DMA
>Nov  3 08:18:01 localhost kernel: hdj: dma timeout retry: status=0xd1 { 
>Busy }
>Nov  3 08:18:01 localhost kernel:
>Nov  3 08:18:01 localhost kernel: hdi: DMA disabled
>Nov  3 08:18:01 localhost kernel: hdj: DMA disabled
>Nov  3 08:18:01 localhost kernel: ide4: reset: success
>Nov  3 08:18:09 localhost kernel: blk: queue c0181fac, I/O limit 4095Mb 
>(mask 0xffffffff)
>Nov  3 08:18:16 localhost kernel: hdj: read_intr: status=0x59 { DriveReady 
>SeekComplete DataRequest Error }
>Nov  3 08:18:16 localhost kernel: hdj: read_intr: error=0x40 { 
>UncorrectableError }, LBAsect=103350672, high=6, low=2687376, 
>sector=103350672
>Nov  3 08:18:16 localhost kernel: end_request: I/O error, cmd 0 dev 38:40 
>(hdj), sector 103350672
>Nov  3 08:18:20 localhost kernel: hdj: dma_intr: status=0x51 { DriveReady 
>SeekComplete Error }
>Nov  3 08:18:20 localhost kernel: hdj: dma_intr: error=0x40 { 
>UncorrectableError }, LBAsect=103350676, high=6, low=2687380, 
>sector=103350674
>Nov  3 08:18:20 localhost kernel: end_request: I/O error, cmd 0 dev 38:40 
>(hdj), sector 103350674
>Nov  3 08:18:24 localhost kernel: hdj: dma_intr: status=0x51 { DriveReady 
>SeekComplete Error }
>Nov  3 08:18:24 localhost kernel: hdj: dma_intr: error=0x40 { 
>UncorrectableError }, LBAsect=103350676, high=6, low=2687380, 
>sector=103350676
>Nov  3 08:18:24 localhost kernel: end_request: I/O error, cmd 0 dev 38:40 
>(hdj), sector 103350676
>Nov  3 08:18:54 localhost kernel: hdj: dma_intr: status=0x51 { DriveReady 
>SeekComplete Error }
>Nov  3 08:18:54 localhost kernel: hdj: dma_intr: error=0x40 { 
>UncorrectableError }, LBAsect=108855680, high=6, low=8192384, 
>sector=108855680
>Nov  3 08:18:54 localhost kernel: end_request: I/O error, cmd 0 dev 38:40 
>(hdj), sector 108855680 low=8192384, sector=108855680
>Nov  3 08:18:54 localhost kernel: end_request: I/O error, cmd 0 dev 38:40 
>(hdj), sector 108855680
>Nov  3 09:01:00 localhost CROND[2241]: (root) CMD (nice -n 19 run-parts 
>/etc/cron.hourly)
>Nov  3 09:17:57 localhost kernel: hdj: dma_timer_expiry: dma status == 0x41
>Nov  3 09:18:04 localhost proftpd[2258]: localhost 
>(main.internal[192.168.10.10]) - FTP session opened.
>Nov  3 09:18:53 localhost kernel: hdj: dma_intr: status=0x51 { DriveReady 
>SeekComplete Error }
>Nov  3 09:18:53 localhost kernel: hdj: dma_intr: error=0x40 { 
>UncorrectableError }, LBAsect=40960394, high=2,low=7405962, sector=40960384
>Nov  3 09:18:53 localhost kernel: end_request: I/O error, cmd 0 dev 38:40 
>(hdj), sector 40960384
>

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \