Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to install Debian Squeeze 6.0.5 on a new HP Proliant Microserver N40L with 4 GB RAM and 1.5 GHZ and 2 new Seagate BARRACUDA 2TB HDD (delivered yesterday). The installation stuck at the point of formatting the 2 TB HDD at 33%. I gave him 16 hours, then I aborted the formatting and started the SEATOOLS HDD Utility to check for errors. The HDD passed the check and I freshly ereased both hdd with zero's by the SEATOOLS Utility. Now I restarted the installation and it got stuck again at 33%. How long I need to wait for this formatting?

Partitions of Software-Raid 1: /boot 500MB ext2 / 1995.9 GB ext3 swap 4 GB

With Alt + F4 I can't see any errors in the terminal, because the whole time my USB-Devices appear..., Swichting back to Alt + F1, it keep staying at 33%.

Is there any way to speed up this formatting? The hdd are new, so there is no need of secure deleting etc...


I found now out, that resync is incredible slow: http://up.picr.de/11594927qr.jpg writing with 700 k/sec. How could this happen? -> Estimated time: 30 Days!

I set already echo 50000 >/proc/sys/dev/raid/speed_limit_min without any change...

Thank you very much!

share|improve this question
You can try to format the disks in another computer. – Luis Aug 22 '12 at 10:49
You can try to install on only one HDD and see if at least one of them works. – Bananguin Aug 22 '12 at 11:47

The "formatting" step inside the installation is not entirely precise with percentages (in fact it just divides 100% by the number of partitions to create), so when it appears to hang it might indeed be working properly.

I agree that 16 hours seems excessive, even for the notoriously slow ext3 initialization (writing to block devices happens synchronously, and ext3 initialization requires a lot of data to be written in small chunks spaced far apart, which is about the worst case), however keep in mind that at the same time the RAID initialization is also running with a certain minimum bandwidth (i.e. the disks are thrashing heavily).

Things you can do:

  • think about your partitioning schema:
    • If the / partition is a real partition rather than an LVM volume, there is no need for a separate /boot, and you almost certainly want your swap space in the middle of the disk rather than at the end.
    • a 2 TB / partition is hell, because it takes ages to check if anything ever goes wrong, and you can do nothing about that.
  • initialize the RAID with --assume-clean. This means that the RAID will not initially synchronize the disks, which is fine if you already wrote them as zeros
  • create the file system from the command line (so you see more granular progress).

If you change your partitioning schema, I'd suggest something like

  • partition 1: /boot (500 MB)
  • partition 2: LVM PV
    • LV 1: / (500 MB)
    • LV 2: /usr (8 GB)
    • LV 3: /var (4 GB)
    • LV 4: /home (size according to personal preference, 100 GB is what I use)
    • LV 5: swap
    • LV 6: /srv/ (size according to personal preference and machine purpose)

It is totally okay to leave most of the space unallocated, you can change that later on, when the system is installed, and you can also add additional file systems for specific services that use lots of space, which means that if one of these services malfunctions and starts filling up the disk, it will only fill up its own partition (this is also why you have separate /var -- logging can work when the root partition is full.

share|improve this answer

16 hours is excessive. Something has gone wrong. When you say "the whole time my USB devices appear", do you mean that its spewing messages constantly? If so, what messages? Easy way is to take a screenshot using a phone camera, and just post that. What USB devices do you have connected?

Have you verified your install media is intact? I believe there is a menu option in the installer to check the install media.

Anyway, assuming none of the above is the problem:

First, use ext4, not ext3. There isn't really any good reason to use ext3. Also, consider using enterprise drives in servers (e.g., the Constellation line), depending on the type of duty this server will see. Much more expensive, but better able to handle a constant workload.

Second, you could do the format using mkfs from the command line. Just hit alt-f2, and press enter to get a command prompt. Then mkfs.ext4 -v -L "label" /dev/whatever (add whatever other options you want, see the mke2fs manpage). Then switch back to alt-f1, and get the thing to rescan (by going back to the main menu, etc.). You can then tell it to not format the disk, and just tell it the mount point.

share|improve this answer
Hello, thank you for your response. My USB devices get disconnected and connected the whole time. Just mouse and keyboard is connected by usb. I'm trying now this workround: I remove one HDD and I just created a boot partiotion ext2 with 500 MB and a second partition ext4 / with 10 GB. Now I install debian first and after I try to enlarge my ext4 and add the swap. Finally I insert the second hdd and enable software raid. This should work too or? – heuri Aug 22 '12 at 14:42
That "enable software RAID" step could be painful, if you don't perfectly plan everything out. I'd suggest trying mkfs from the command line over that... Also, ext4 mkfs is much faster than ext3 mkfs. So it may just be fine. – derobert Aug 22 '12 at 14:59
how would the configure command with raid 1 look like? my normal setup was up.picr.de/11589898av.jpg thank you – heuri Aug 22 '12 at 21:14
mkfs is now running since 14 hours: up.picr.de/11593046ae.jpg sadly also stuck at 33% – heuri Aug 23 '12 at 10:43
You could try a newer kernel (e.g., I think the wheezy d-i can be used to install squeeze as well, and then you'll get 3.2 in the installer), or alternatively start hardware troubleshooting. It shouldn't take anywhere near that long, especially for ext4. Or see kmuto.jp/debian/d-i (that has a 3.2 d-i for squeeze) – derobert Aug 23 '12 at 21:03
up vote 1 down vote accepted

Thank you very much for your answers.

The solution was to prepare the installation for raid 1, but just mount one hdd in the raid.

(Active devices: 2, reserved devices: 0, but just SDA and not SDA + SDB)

This solved the problem with resync and the installer worked normally.

After the installation of debian, I simply added the second hdd to my raid:

mdadm --add /dev/md0 /dev/sdb1 (this for every partition)

Result: resync speed increased from 750 k (at the installer) to 70000 k at the running system.

share|improve this answer

I would try two things.

I have noticed for some reason (and whether this is true or not, I'm not sure) that Linux is more sensitive to failing hardware. I have seen this on my home office computer a couple of times.

I've never had much luck with SeaTools. I've always used HDD Regenerator to double check for bad sectors, even on new drives. It isn't free, but it works really well.

The next thing I would try (or the first, since its free) would be a Memtest.

For that I would recommend Ultimate Boot CD. I would let it run a minimum of an hour - overnight preferably.

Out of those two, I would bet a lot of money that something would show up defective - and my money would be on memory.

share|improve this answer

The same thing happen to me when formatting a friend notebook, I tried to install 5 Linux distros and a Windows 7, and the same thing happened on all these O.S. then I discovered that the problem come from the HD, because It was damaged.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.