Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I installed a SATA drive this morning, a 500gig Seagate Barracuda. I am using Mandriva 2008 and it recognized it right away. I went to format it as an ext3 partition, and it went throught the process and then at the end popped up a box saying "ext3 formatting of sda1 failed". Why would it fail at the end? Is there a problem with the mount point? I have tried it several times, but to no avail.
Nope. No option to see anything else. When I try to do it again it will run through the whole process in about twenty seconds and that box pops up saying the ext3 formatting of sda1 failed with one button that says ok. I'm not a linux expert, but I'd say thats quite odd.
Okay...no output from the fdisk command...so I ran mkfs here it is...
[root@localhost cory]# fdisk -l /dev/sda
[root@localhost cory]# mkfs.ext3 /dev/sda1
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
30531584 inodes, 122096000 blocks
6104800 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
3727 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: done
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Ok...I zero filled this drive to totally start over. Now I went into diskdrake and decided that maybe if I broke it into two pieces it would maybe work. So I created a partition of about half the size and sent it on its way with an ext3 format. So its about 240 gig that it has to format. How long should this take? Its been running about two hours now and on its little graph it looks to be about a sixth of the way through. Whats the deal with this thing?
I'm not that familiar with diskdrake, but I would assume that the application is configured to automatically check for bad blocks when doing a format. A bad block check takes time and is probably unnecessary since your zero fill already checked for that. To check for bad blocks, it has to read and write data to every block which can take some time.
Ahhh good call on that. I actually ran badblocks last night, and it took quite a while. I couldn't tell you how long because I went to sleep. I found that a little disturbing because I can't figure out what a short read is and I was kind of hoping it would have been caused by a bad block on the drive. I am thinking it has something to do with the file system not being exactly on the partition because of the geometry of the partition on the drive. Maybe the math doesn't work out exactly right? If it is an issue with that then I think cutting it into two smaller partitions should do the trick.
My best guess would be that you had some bad blocks on that drive that were corrected by your zero fill and bad block check. Applications that "repair" bad blocks do so by simply marking them bad so that the hard drive circuitry no longer attempts to write data to that block. Having bad block problems on a new drive is not a good sign. You might want to download Seagate's diagnostic utility iso from their website and run a thorough test on that drive if you haven't done so already. If any problems are reported, contact Seagate support for a warranty replacement.