Sorry about that, the picture didn't work properly so I'll remove it.<br><br>I've run into superblock issues and have done the following the fix it (I wrote up a doc on my wiki):<br><br><h1><span>
System Hangs at Boot with Size in Superblock error - Fix</span></h1><div><div>
<p>It appears that for some of our servers, someone has attemped to extend a filesystem and forgot to run the resize2fs command.</p><p>This
makes it so that the filesystem is extend for X amount, but the actual
logical volume isn't resized to utilize this extra space. What I've
found so far is some of our x nodes for the mount point:</p><p>/usr/WebSphere70
were extended, but not resized. So if the server crashes and the OS
tries to FSCK the filesystem because it saw an incomplete journal entry
(normal), it will not be able to fix the logical volume. So what you
need to do is the following:</p><p> </p><p>On Boot:</p><p>Console Error Picture Removed</p><p><br></p><p>Then enter the root password and press enter.</p><p>Then
find the name of the logical volume that has the superblock error: In
this case, /usr/WebSphere70. You'll want to find the logical volume
that this corresponds to: cat /etc/fstab | more and you'll see that
mount point is linked to /dev/vg02/lv</p><div style="border-width:1px"><div>
<div><div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><div title="Hint: double-click to select code"><div>
<code>cat /etc/fstab | more</code></div><div><code>....</code></div><div><code>and you'll see that mount point is linked to:</code></div>
<div><code>/dev/vg02/lv_uwas70</code></div></div></td></tr></tbody></table></div></div>
</div></div><p> </p><p>So next, you'll want to fix the superblock and FSCK the disk (if you just fsck the disk, it won't work):</p><div style="border-width:1px"><div>
<div><div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><div title="Hint: double-click to select code"><div>
<code>mke2fs -S /dev/vg02/lv_uwas70 && fsck /dev/vg02/lv_uwas70</code></div></div></td></tr></tbody></table></div></div>
</div></div><p>Then answer yes to repair each item. Once it's finished, you can reboot and see if it comes up cleanly.</p><p> </p><p>OS Boots up, but claims the filesystem does not have a journal and therefore won't mount:</p>
<div style="border-width:1px"><div>
<div><div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><div title="Hint: double-click to select code"><div>
<code>#Make a journal</code></div><div><code>tune2fs -j /dev/vg02/lv_uwas70</code></div><div> </div><div>
<code>#mount the filesystem</code></div><div><code>mount /usr/WebSphere70</code></div></div></td></tr></tbody></table></div></div>
</div></div><p>Then it mounts correctly!</p>
</div></div><br><br><div class="gmail_quote">On Wed, Jun 13, 2012 at 3:03 PM, Andrew Wade <span dir="ltr"><<a href="mailto:andrewiwade@gmail.com" target="_blank">andrewiwade@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Marvin,<br><br>I've run into superblock issues and have done the following the fix it (I wrote up a doc on my wiki):<br>
<br><h1><span>
System Hangs at Boot with Size in Superblock error - Fix</span></h1><div><div>
<p>It appears that for some of our servers, someone has attemped to extend a filesystem and forgot to run the resize2fs command.</p><p>This
makes it so that the filesystem is extend for X amount, but the actual
logical volume isn't resized to utilize this extra space. What I've
found so far is some of our x nodes for the mount point:</p><p>/usr/WebSphere70
were extended, but not resized. So if the server crashes and the OS
tries to FSCK the filesystem because it saw an incomplete journal entry
(normal), it will not be able to fix the logical volume. So what you
need to do is the following:</p><p> </p><p>On Boot:</p><p>Console Error:</p><p><img src="" alt=""></p>
<p><br></p><p>Then enter the root password and press enter.</p><p>Then
find the name of the logical volume that has the superblock error: In
this case, /usr/WebSphere70. You'll want to find the logical volume
that this corresponds to: cat /etc/fstab | more and you'll see that
mount point is linked to /dev/vg02/lv</p><div style="border-width:1px"><div>
<div><div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><div title="Hint: double-click to select code"><div>
<code>cat /etc/fstab | more</code></div><div><code>....</code></div><div><code>and you'll see that mount point is linked to:</code></div>
<div><code>/dev/vg02/lv_uwas70</code></div></div></td></tr></tbody></table></div></div>
</div></div><p> </p><p>So next, you'll want to fix the superblock and FSCK the disk (if you just fsck the disk, it won't work):</p><div style="border-width:1px"><div>
<div><div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><div title="Hint: double-click to select code"><div>
<code>mke2fs -S /dev/vg02/lv_uwas70 && fsck /dev/vg02/lv_uwas70</code></div></div></td></tr></tbody></table></div></div>
</div></div><p>Then answer yes to repair each item. Once it's finished, you can reboot and see if it comes up cleanly.</p><p> </p><p>OS Boots up, but claims the filesystem does not have a journal and therefore won't mount:</p>
<div style="border-width:1px"><div>
<div><div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><div title="Hint: double-click to select code"><div>
<code>#Make a journal</code></div><div><code>tune2fs -j /dev/vg02/lv_uwas70</code></div><div> </div><div>
<code>#mount the filesystem</code></div><div><code>mount /usr/WebSphere70</code></div></div></td></tr></tbody></table></div></div>
</div></div><p>Then it mounts correctly!</p>
</div></div><br><br><div class="gmail_quote">On Wed, Jun 13, 2012 at 2:32 PM, Michael H. Warfield <span dir="ltr"><<a href="mailto:mhw@wittsend.com" target="_blank">mhw@wittsend.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Wed, 2012-06-13 at 13:00 -0400, <a href="mailto:mdkliman@aol.com" target="_blank">mdkliman@aol.com</a> wrote:<br>
<br>
> I'm "The Marvin" who's calling for help.<br>
<br>
> Once upon-a-time I was technical - during the minicomputer era - but<br>
> stopped short of Linux immersion. I understand what I'm reading and<br>
> am grateful for the helpful comments I've received.<br>
<br>
> I'm sure the drives were inaccessible to the system when we tried to<br>
> reboot (red lamps were lighted). They appear to be online now (green<br>
> lamps are lighted). However, I don't know where to go from here. I<br>
> am not conversant with Linux or its utilities.<br>
<br>
</div>Red lamps and green lamps??? What kind of server is this we are talking<br>
about and what kind of drives? Are they external drives? In another<br>
message, I think you made a remark about "rdrives" here:<br>
<div><br>
On Wed, 2012-06-13 at 12:41 -0400, <a href="mailto:mdkliman@aol.com" target="_blank">mdkliman@aol.com</a> wrote:<br>
> Robert,<br>
><br>
> I know the root password, but have no idea what utility to run. The<br>
> system is where it failed, except that the rdrives that couldn't be<br>
> accessed are now back online.<br>
<br>
</div>What are these "rdrives" and how many drives are we talking about???<br>
Are you referring to raid drives? Is this a raid array cabinet?<br>
<br>
Have you rebooted the server since the drives came on-line? I have seen<br>
this in the past where drives were unavailable at boot up due to<br>
(generally brief) power loss or fluctuations. If you haven't, I<br>
seriously doubt you have anything to loose at this point and would go<br>
ahead and reboot the system first, without doing a power down.<br>
<br>
If that works, great. If not, trying powering it all down and bringing<br>
it back up after a few minutes.<br>
<br>
If either of those work, your first order of business is to get your<br>
data OFF that system. There is no way you can trust it going forward.<br>
<br>
There are some recovery applications available such as dd-rescue which<br>
can be used to recover data from a moderately damaged drive and there<br>
are other techniques for use if you've blown a controller board or an<br>
interface. But we would need a lot more information first.<br>
<br>
If someone gets out there (I'm totally unavailable for at least a couple<br>
of weeks) and makes it work, it doesn't mean they "made it all better".<br>
You need to upgrade that system or history will repeat itself and it<br>
will be costly.<br>
<br>
Regards,<br>
Mike<br>
<div><br>
> My programmer took a quick look and insists that I get Admin help to<br>
> get the system back in order. I am seeking someone knowledgeable who<br>
> will come on-site and attempt to "clean up" the file system or<br>
> determine that it's trashed.<br>
><br>
> Glug, glug, glug ...<br>
> Marvin in Norcross, GA<br>
> <a href="tel:%28404%29%20433-0900" value="+14044330900" target="_blank">(404) 433-0900</a><br>
><br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: Jim Lynch <<a href="mailto:ale_nospam@fayettedigital.com" target="_blank">ale_nospam@fayettedigital.com</a>><br>
> To: Atlanta Linux Enthusiasts <<a href="mailto:ale@ale.org" target="_blank">ale@ale.org</a>><br>
> Sent: Wed, Jun 13, 2012 6:55 am<br>
> Subject: Re: [ale] Can't Boot! Need Super Block Wizard<br>
><br>
><br>
> On 06/13/2012 05:32 AM, Matthew wrote:<br>
> I am more curious, Does the Marvin know how to do everything that we<br>
> are suggesting? I rather just go down there and fix it. I just don't<br>
> have time to drive down 10 hours, fix it, and drive back.<br>
</div><div>> e did say he had a programmer that was familiar with Linux but probably<br>
</div><div>> asn't a true sys admin. I'm hoping Marvin can answer your question<br>
</div>> hen he comes online.<br>
> Jim.<br>
<div>> ______________________________________________<br>
> le mailing list<br>
> <a href="mailto:le@ale.org" target="_blank">le@ale.org</a><br>
> ttp://<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">mail.ale.org/mailman/listinfo/ale</a><br>
</div><div>> ee JOBS, ANNOUNCE and SCHOOLS lists at<br>
</div>> ttp://<a href="http://mail.ale.org/mailman/listinfo" target="_blank">mail.ale.org/mailman/listinfo</a><br>
<div>><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
</div><div><div>--<br>
Michael H. Warfield (AI4NB) | <a href="tel:%28770%29%20985-6132" value="+17709856132" target="_blank">(770) 985-6132</a> | mhw@WittsEnd.com<br>
/\/\|=mhw=|\/\/ | <a href="tel:%28678%29%20463-0932" value="+16784630932" target="_blank">(678) 463-0932</a> | <a href="http://www.wittsend.com/mhw/" target="_blank">http://www.wittsend.com/mhw/</a><br>
NIC whois: MHW9 | An optimist believes we live in the best of all<br>
PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!<br>
</div></div><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br>
</blockquote></div><br>