Outline · [ Standard ] · Linear+ bad sectors?

[Red Squirrel]

We had a power outage this morning and I was in bed so I only woke up when my PC shut off, and it's the only way to shut off the server, which has a bit longer backup time.

Simply put, the server did not shut down properly, and now I'm getting all these "bad inodes" errors when I boot. What is this?! I know it has to do with the hard drive since it shows it at the part where it goes /32432 blocks or whatever and shows that it's full of errors.

This is my new hard drive too.

What exactly does all this mean anyway?

[Andy]

We had a power outage this morning and I was in bed so I only woke up when my PC shut off, and it's the only way to shut off the server, which has a bit longer backup time. 

Simply put, the server did not shut down properly, and now I'm getting all these "bad inodes" errors when I boot.  What is this?!  I know it has to do with the hard drive since it shows it at the part where it goes /32432 blocks or whatever and shows that it's full of errors.

This is my new hard drive too.

What exactly does all this mean anyway?

What this means is you need to backup any data that you can and reformat you Hard disk what you have is a Software Bad sector that can be fixed with a format. once your don't reload you software (that works) and you'll notice the Problem gone

This post has been edited by Andy: Nov 9 2004, 09:38 PM

[Red Squirrel]

I went to another forum and this error does not involve physical damage so I'm good. I rather loose all my data then the hard drive, less expensive that way, since I backup anyway.

[Andy]

I went to another forum and this error does not involve physical damage so I'm good.  I rather loose all my data then the hard drive, less expensive that way, since I backup anyway.

See like i said just a format would fix your problem. Its software Sector Problem's that are annoying but easy to fix.

[megaspaz]

why do you insist on using ext2 as the filesystem? reformat and reinstall linux. when you reinstall linux, use ext3 for the filesystem. you can continually turn off the power if you like and the journalling will keep you from having bad inodes and sectors. for the love of god, stop using ext2.

[Red Squirrel]

I just used whatever the default is. What is the big difference anyway? According to fdisk it's just "linux"

CODE

[root@localhost root]# fdisk -l

Disk /dev/hdc: 255 heads, 63 sectors, 24321 cylinders
Units = cylinders of 16065 * 512 bytes

  Device Boot    Start       End    Blocks   Id  System
/dev/hdc1             1     24321 195358401   83  Linux

Disk /dev/hda: 255 heads, 63 sectors, 14946 cylinders
Units = cylinders of 16065 * 512 bytes

  Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1      1305  10482381   83  Linux
/dev/hda2          1306     14815 108519075   83  Linux
/dev/hda3         14816     14946   1052257+  82  Linux swap

[megaspaz]

I just used whatever the default is.  What is the big difference anyway?  According to fdisk it's just "linux"

CODE

[root@localhost root]# fdisk -l

Disk /dev/hdc: 255 heads, 63 sectors, 24321 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 1 24321 195358401 83 Linux

Disk /dev/hda: 255 heads, 63 sectors, 14946 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 1305 10482381 83 Linux
/dev/hda2 1306 14815 108519075 83 Linux
/dev/hda3 14816 14946 1052257+ 82 Linux swap

i just told you what the big difference is. ext3 is a journalling file system. it's basically an ext2 filesystem with journalling. the benefit being you don't get a corrupted filesystem when you have a power failure or hot power off. if you want to keep having these problems, then by all means continue using ext2. i'll gladly leave all filesystem topics from now on and let you go about breaking your uber-boxen.

[Red Squirrel]

What about the file system "linux" is that ex2 or 3? I forget what the command was to format it but it has ext3 in it, so I don't know why it did not make it ext3...

I'm not going to reinstall for something silly like this though, but I can probably just use partition magic or similar program to convert it.

But that's not what the issue was, it was the bad inode things. I wanted to know if it meant bad clusters. As long as there's no physical damage on the drive, then all is good. I'm also going to make a script of some sort that can shut down the server if accessed through http, so I can install the UPS software in windows and make it execute the script, so this won't happen again.

[megaspaz]

where did you see this bad inode thing? was it just something like "cleaned up 'X amount' orphaned inodes" or was it something like a boot failure due to corrupt inodes? if it's something like the first, the ignore it. if you are using ext3 but decided to let fsck run, then it's most likely fsck cleaning up orphaned inodes. if it's the latter, then it's reinstall linux time, which most likely meant you didn't use ext3 for the file system. and by the way, you can't use partition magic to convert an ext2 file system to ext3. partition magic can't do conversions on partitions that are already formatted in a linux filesystem. so you best stop with the thinking partition magic can do this and that with your linux paritition, because you're just looking to fsck you computer to hell.

http://anythingforums.com/forums/index.php?showtopic=921

[Red Squirrel]

It was the first, said it was clearing inodes but it was the first time I see that, and there was quite a few, about a screen full. Is it physical damage? Or is it just like when scandisk finds lost clusters and makes a bunch of .chk files?

At the time the power went out, it was most likely in the middle of a transfer, since I have a few backup routines that run at around that time so it might of been during one of them.

[megaspaz]

if it's the first and that's the only time you've seen it, then it's ok. i guess you could akin it to scandisk doing whatever it is it does with file fragments....

[Red Squirrel]

Well that's good to know then. So it does not cost me 200 bucks to fix.

I just need to setup an auto shutdown system for next time the power goes out. Should be easy to do with a php script in an ackward http folder with a password or something. Just need to duplicate the packet and go from there to automate it.