-f -b 32768 /dev/mapper/VolGroup00-LogVol00"
>
> Paul
>
> - Original Message -
> From: "Ron Croonenberg"
> To: "Paul M. Dyer"
> Cc: "linux-poweredge"
> Sent: Tuesday, June 8, 2010 9:18:30 AM
> Subject: Re: dell 2850 initrd probl
On 2010-06-09 15:33, Paul M. Dyer wrote:
> Sorry for the delay. Been busy with things.
>
> If you believe the other LVOL is a filesystem, you can run e2fsck on it
> also. Yes, the first LVOL may be a swap partition. The "-b 32768"
> parameter is telling e2fsck to use superblock at location
On Wed, 9 Jun 2010, Ron Croonenberg wrote:
> /dev/mapper/VolGroup00-LogVol00 but I thought that was /boot ?
/dev/sda1 was /boot wasn't it? This'll be /, and LogVol01 will be swap.
jh
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://l
block:
"e2fsck -f -b 32768 /dev/mapper/VolGroup00-LogVol00"
Paul
- Original Message -
From: "Ron Croonenberg"
To: "Paul M. Dyer"
Cc: "linux-poweredge"
Sent: Tuesday, June 8, 2010 9:18:30 AM
Subject: Re: dell 2850 initrd problem.
Hi Paul,
I mana
Ron Croonenberg wrote:
> So if I issue:
> "e2fsck -f -b 32768 /dev/mapper/VolGroup00-LogVol01"
>
Hi,
If you're running filesystem checks - I'd strongly suggest running them
on a backup image, or (more easy to achieve and quicker) running them
against a copy-on-write snapshot (see my post of
On 2010-06-08 14:18, Ron Croonenberg wrote:
> Hi Paul,
>
> I managed to move pretty much all data from the 'hosed' machine to
> another place. (there are a few things that I would like to salvage but
> couldn't)
>
> I would like to make an attempt to fix the filesystem and see if I can
> get s
f -b 32768.." on the
> /dev/mapper/volume and try to get a good superblock and correct the
> filesystem.
>
> Paul
>
> - Original Message -
> From: "Ron Croonenberg"
> To: "Bond Masuda"
> Cc: "linux-poweredge"
> Sent: Frid
On 2010-06-04 16:47, Ron Croonenberg wrote:
> Jefferson Ogata wrote:
>> How important is the content of this system. Do you have another system
>> you can image the disk to in case you do something destructive
>
> Well here is the thing. We had a 'standby' server that basically
> would copy eve
On 2010-06-04 19:14, Ron Croonenberg wrote:
> What jefferson says is correct, I can mount the volume with the rescue
> cd, in /mnt/sysimage.
>
> If I browse around (within /mnt/sysimage) I can see 'everything', not
> just etc.
>
> However, /initrd is empty and in /etc there are a bunch of dama
ot;
Sent: Friday, June 4, 2010 12:11:53 PM
Subject: Re: dell 2850 initrd problem.
right,
I am actually thinking about moving the date to another machine and/or
put it on another device.
(the rescue cd gives me the option to activate the network interfaces,
that way I could scp or ftp it to anothe
right,
I am actually thinking about moving the date to another machine and/or
put it on another device.
(the rescue cd gives me the option to activate the network interfaces,
that way I could scp or ftp it to another machine and inspect the
retrieved data before anything else.)
Bond Masu
On Fri, June 4, 2010 13:03, Jefferson Ogata wrote:
> On 2010-06-04 16:58, Robin Bowes wrote:
>> On 04/06/10 17:51, J. Epperson wrote:
>>> On Fri, June 4, 2010 12:08, Jefferson Ogata wrote:
On 2010-06-04 15:42, Ron Croonenberg wrote:
> it says that /dev/sda2 is an LVM volume
In ca
Well,
I seem to have :
/dev/sda1 that is labeled /root
/dev/sda2 labeled something that says LVM
I found that using fdisk -l
But it seems you guys know what you are talking about, I'll follow the
discussion
Robin Bowes wrote:
> On 04/06/10 17:51, J. Epperson wrote:
>
>> On Fri, Ju
What jefferson says is correct, I can mount the volume with the rescue
cd, in /mnt/sysimage.
If I browse around (within /mnt/sysimage) I can see 'everything', not
just etc.
However, /initrd is empty and in /etc there are a bunch of damaged
files, initrd.conf, ldap.conf ... but those are jus
On 2010-06-04 17:17, Ron Croonenberg wrote:
>> In what sense are these systems "fried"? Can you move the RAID
>> controller and disks from one system to another?
>
> Uhm, no. the machine I am talking about now has the hardware repaired,
> by putting in a new raid kit.
> Moving it to another ser
> In what sense are these systems "fried"? Can you move the RAID
> controller and disks from one system to another?
>
Uhm, no. the machine I am talking about now has the hardware repaired,
by putting in a new raid kit.
Moving it to another server (I don't have another 2850, I have a few
m
> Regardless of default install layout, we have a "bad" superblock on
> /dev/sda2 and /dev/sda2 marked as an LVM device. The evidence is strong
> that / is an LV within the PV that is on /dev/sda2. If you tried to
> recover a superblock directly on /dev/sda2 you would wipe out who knows
> what.
>
ata"
Cc: linux-poweredge@dell.com
Sent: Friday, June 4, 2010 12:19:37 PM
Subject: Re: dell 2850 initrd problem.
> Regardless of default install layout, we have a "bad" superblock on
> /dev/sda2 and /dev/sda2 marked as an LVM device. The evidence is
> strong that / is an LV wit
On 2010-06-04 18:57, Paul M. Dyer wrote:
> Actually, you would want to try and recover the superblock from the
> /dev/mapper/.. device.
No, given that he already said he can see /etc, albeit missing important
things, his superblock is almost certainly intact.
__
Jefferson Ogata wrote:
> On 2010-06-04 17:08, Ron Croonenberg wrote:
>
>> Here is what is in /dev/mapper/
>>
>> 10, 63 control
>> 253, 0 VolGroup00-LogVol00
>> 253, 1 VolGroup00-LogVol01
>>
>
> And what do you get from:
>
> e2label /dev/mapper/VolGroup00-LogVol00
> e2label /dev/mapper/Vo
On 2010-06-04 17:43, Ron Croonenberg wrote:
> ok here's what I see:
>
> e2label /dev/mapper/VolGroup00-LogVol00 : nothing, empty line
That's *probably* your root partition. This is the important thing to image.
For future reference, you should always partition your systems
appropriately. Don'
Jefferson Ogata wrote:
> I meant the other way around. If the two backup systems are "fried" but
> you can get their disks running on alternate "non-fried" systems, you
> can recover your data from those.
>
gotcha. well the one machine was not a raid, and one drive is toast,
doesn't even sp
- Original Message -
| Well,
|
| I seem to have :
|
| /dev/sda1 that is labeled /root
| /dev/sda2 labeled something that says LVM
|
| I found that using fdisk -l
|
| But it seems you guys know what you are talking about, I'll follow the
| discussion
|
Ok, here are some commands to h
On 2010-06-04 17:08, Ron Croonenberg wrote:
> Here is what is in /dev/mapper/
>
> 10, 63 control
> 253, 0 VolGroup00-LogVol00
> 253, 1 VolGroup00-LogVol01
And what do you get from:
e2label /dev/mapper/VolGroup00-LogVol00
e2label /dev/mapper/VolGroup00-LogVol01
(or, alternately):
e2label /de
Here is what is in /dev/mapper/
10, 63 control
253, 0 VolGroup00-LogVol00
253, 1 VolGroup00-LogVol01
Jefferson Ogata wrote:
> On 2010-06-04 15:42, Ron Croonenberg wrote:
>
>> it says that /dev/sda2 is an LVM volume
>>
>
> In case it isn't clear to you, BTW, this means that /dev/sda2
On 2010-06-04 16:58, Robin Bowes wrote:
> On 04/06/10 17:51, J. Epperson wrote:
>> On Fri, June 4, 2010 12:08, Jefferson Ogata wrote:
>>> On 2010-06-04 15:42, Ron Croonenberg wrote:
it says that /dev/sda2 is an LVM volume
>>>
>>> In case it isn't clear to you, BTW, this means that /dev/sda2 is
On Fri, 2010-06-04 at 12:47 -0400, Ron Croonenberg wrote:
> Well here is the thing. We had a 'standby' server that basically
> would copy everything every night and in case something bad ever would
> happen to the main server we could run it off that one.
> However that one got fried during t
On 04/06/10 17:51, J. Epperson wrote:
> On Fri, June 4, 2010 12:08, Jefferson Ogata wrote:
>> On 2010-06-04 15:42, Ron Croonenberg wrote:
>>> it says that /dev/sda2 is an LVM volume
>>
>> In case it isn't clear to you, BTW, this means that /dev/sda2 is NOT /.
>>
>
> ?Does it?
Hmm, I queried that
On Fri, June 4, 2010 12:08, Jefferson Ogata wrote:
> On 2010-06-04 15:42, Ron Croonenberg wrote:
>> it says that /dev/sda2 is an LVM volume
>
> In case it isn't clear to you, BTW, this means that /dev/sda2 is NOT /.
>
?Does it?
___
Linux-PowerEdge maili
Jefferson Ogata wrote:
> On 2010-06-04 15:42, Ron Croonenberg wrote:
>
>> Jefferson Ogata wrote:
>>
>>> What does your partition table actually say? Is /dev/sda2 *supposed* to
>>> be a filesystem, or is an LVM physical volume?
>>>
>> it says that /dev/sda2 is an LVM volume
>>
>
On 2010-06-04 15:42, Ron Croonenberg wrote:
> it says that /dev/sda2 is an LVM volume
In case it isn't clear to you, BTW, this means that /dev/sda2 is NOT /.
Check what devices you have under /dev/mapper/.
___
Linux-PowerEdge mailing list
Linux-PowerEd
On 2010-06-04 15:42, Ron Croonenberg wrote:
> Jefferson Ogata wrote:
>> What does your partition table actually say? Is /dev/sda2 *supposed* to
>> be a filesystem, or is an LVM physical volume?
>
> it says that /dev/sda2 is an LVM volume
In that case, I strongly suggest that you *not* follow any
Jefferson Ogata wrote:
> On 2010-06-03 17:38, Ron Croonenberg wrote:
>
>> I already did that.
>>
>> I have /dev/sda1 and /dev/sda2
>>
>> if I run fsck on /dev/sda1 it warns about not finding /etc/fstab but
>> than says that /boot is fine.
>>
>> when I run fsck on /dev/sda2 I get the same fs
On 2010-06-03 17:38, Ron Croonenberg wrote:
> I already did that.
>
> I have /dev/sda1 and /dev/sda2
>
> if I run fsck on /dev/sda1 it warns about not finding /etc/fstab but
> than says that /boot is fine.
>
> when I run fsck on /dev/sda2 I get the same fstab warning but then says
> it can
superblock resides. Then
> use this information to do the recovery on the corrupt system.
>
> Paul
>
> - Original Message -
> From: "Ron Croonenberg"
> To: "Paul M. Dyer"
> Cc: linux-poweredge@dell.com
> Sent: Thursday, June 3, 2010 12:38:49
t;
Cc: linux-poweredge@dell.com
Sent: Thursday, June 3, 2010 12:38:49 PM
Subject: Re: dell 2850 initrd problem.
Hi Paul,
I already did that.
I have /dev/sda1 and /dev/sda2
if I run fsck on /dev/sda1 it warns about not finding /etc/fstab but
than says that /boot is fine.
when I run fsck on /dev/sd
From: linux-poweredge-bounces-Lists On Behalf Of Ron Croonenberg
[r...@depauw.edu]
Sent: Thursday, June 03, 2010 12:38 PM
To: Paul M. Dyer
Cc: linux-poweredge-Lists
Subject: Re: dell 2850 initrd problem.
Hi Paul,
I already did that.
I have /dev/sda1 and /dev/sda2
2 (check the second partition)
>
> Paul
>
> - Original Message -
> From: "Ron Croonenberg"
> To: linux-poweredge@dell.com
> Sent: Thursday, June 3, 2010 11:25:45 AM
> Subject: Re: dell 2850 initrd problem.
>
> is it a good idea to run fsck from the rescue cd fir
ion)
Paul
- Original Message -
From: "Ron Croonenberg"
To: linux-poweredge@dell.com
Sent: Thursday, June 3, 2010 11:25:45 AM
Subject: Re: dell 2850 initrd problem.
is it a good idea to run fsck from the rescue cd first?
do something like fsck -v -y /dev/... (what ever the device is)
is it a good idea to run fsck from the rescue cd first?
do something like fsck -v -y /dev/...(what ever the device is)
or should I just use mkinitrd, and keep my fingers crossed it will
create all the missing stuff again.
(I might need fsck, because, as I mentioned, I saw some messages
Hi Ron,
the typical solution in such a case is: Restore from backup. :-|
On Thu, Jun 03, 2010 at 11:27:42AM -0400, Ron Croonenberg wrote:
> I found the FC3 rescuecd somewhere it is 2.6.12-1.667
> (that was what was initially installed.)
>
>
> btw: I remember, before the reboot with the kern
the
>> right disk is selected.
>>
>>
>> Just trying to make sure replacing the Raid Cache didn't mess up the
>> HDD.
>>
>> Praveen
>>
>>
>> From: linux-poweredge-bounces-Lists On Behalf Of Ron
ux-poweredge-bounces-Lists On Behalf Of Ron Croonenberg
> [r...@depauw.edu]
> Sent: Wednesday, June 02, 2010 4:31 PM
> To: linux-poweredge-Lists
> Subject: dell 2850 initrd problem.
>
> Hello,
>
> I had to replace the raid memory and battery in a Dell 2850, it broke
> so
ts On Behalf Of Ron Croonenberg
> [r...@depauw.edu]
> Sent: Wednesday, June 02, 2010 4:31 PM
> To: linux-poweredge-Lists
> Subject: dell 2850 initrd problem.
>
> Hello,
>
> I had to replace the raid memory and battery in a Dell 2850, it broke
> somehow and the machine w
s selected.
Just trying to make sure replacing the Raid Cache didn't mess up the HDD.
Praveen
From: linux-poweredge-bounces-Lists On Behalf Of Ron Croonenberg
[r...@depauw.edu]
Sent: Wednesday, June 02, 2010 4:31 PM
To: linux-poweredge-Lists
Subject: d
Hello,
I had to replace the raid memory and battery in a Dell 2850, it broke
somehow and the machine was complaining on boot up. That problem went
away, but now I have a problem at bootup.
the msgs I see:
exec of init (/sbin/init) failed!!!: 20
umount /initrd/dev failed 2
kernel panic - not sy
46 matches
Mail list logo
