I just bought two of the WD Green 500GB drives to be used in a hardware RAID (Adaptec 2610SA, aka Dell CERC SATA1.5/6ch) on my Ubuntu-based server. I was going to format it in ext3. Will this problem affect me?
You should be immune. It seems that only >640GB drives have this problem. See the affected drives.
I'm happy to see that you saw the stalling disappear as well, it gives me confidence about the cause.
Time will tell if the the lock-ups were caused by the 512b partitioning (I wasn't able to repartition my drives until a few days ago), but it's a bit reassuring to know that I wasn't the only one experiencing these annoying as fsck freezes.
The affected drives on my end are WDC WD10EACS-00ZJB0 and WDC WD10EADS-00L5B
I noticed both a performance hit AND stalling for a minute at a time when there was a lot of HDD activity, so I can confirm part of your experience.
After going with 56 sectors per track as well, the freezing seems to be a thing of the past. The speed is definitely greatly improved.
depmod - program to generate modules.dep and map files
If you mean you want the modules in the.deb file, use the --initrd parameter as well as a script, such as /usr/share/doc/kernel-package/examples/etc/kernel/postrm.d/initramfs /usr/share/doc/kernel-package/examples/etc/kernel/postinst.d/initramfs
...as is mentioned in/usr/share/doc/kernel-package/README.gz
IIRC, the first three numbers could be anything, and the other 7 digits, when added together, had to add up to a multiple of 7. 123-0000007 also worked.
There used to be two types of MS keys, three digits-seven digits and four digits-eight digits.
For both of those types, the keys that worked were
123-1234567
and
1234-12345678.
I'll have to try 123-0000007 and 1234-00000008 at some point though just to see if that would work...
Slashdot Mirror
I just bought two of the WD Green 500GB drives to be used in a hardware RAID (Adaptec 2610SA, aka Dell CERC SATA1.5/6ch) on my Ubuntu-based server. I was going to format it in ext3. Will this problem affect me?
You should be immune. It seems that only >640GB drives have this problem. See the affected drives.
http://www.wdc.com/en/products/advancedformat/
Yes, certain configurations: XP. According to WD, Linux is not affected by this (but that's been proven to be false).
(I think that) It's probably misaligned. LVM uses a 192k sector size for it's metadata. See Theodore Ts'o's post for more information.
I'm happy to see that you saw the stalling disappear as well, it gives me confidence about the cause.
Time will tell if the the lock-ups were caused by the 512b partitioning (I wasn't able to repartition my drives until a few days ago), but it's a bit reassuring to know that I wasn't the only one experiencing these annoying as fsck freezes.
The affected drives on my end are WDC WD10EACS-00ZJB0 and WDC WD10EADS-00L5B
.
The affected drives are listed on Western Digital's site.
I noticed both a performance hit AND stalling for a minute at a time when there was a lot of HDD activity, so I can confirm part of your experience. After going with 56 sectors per track as well, the freezing seems to be a thing of the past. The speed is definitely greatly improved.
Also see this post.
dev/sdd:
Model=WDC WD15EARS-00Z5B1, FwRev=80.00A80, SerialNo=
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
It looks to me that this should *really* be fixed by WD with a firmware update
.
Solution: Instead of fdisk, call it as fdisk -H 224 -S 56 as per Theodore Tso's blog.
This is OT, but:
.deb file, use the --initrd parameter as well as a script, such as
/usr/share/doc/kernel-package/examples/etc/kernel/postrm.d/initramfs
/usr/share/doc/kernel-package/examples/etc/kernel/postinst.d/initramfs
...as is mentioned in /usr/share/doc/kernel-package/README.gz
man depmod
depmod - program to generate modules.dep and map files
If you mean you want the modules in the
Ubuntu is an African word meaning 'I can't configure Debian' -- AC
FYI (in case you didn't know (or care)), this was originally said by Mark Pilgrim.
IIRC, the first three numbers could be anything, and the other 7 digits, when added together, had to add up to a multiple of 7. 123-0000007 also worked.
There used to be two types of MS keys, three digits-seven digits and four digits-eight digits.
For both of those types, the keys that worked were 123-1234567 and 1234-12345678.
I'll have to try 123-0000007 and 1234-00000008 at some point though just to see if that would work...
Windows doesn't look like Windows 3.11 anymore, but this default theme still does. That's an easy fix that should be included in the next version.
I'm sorry but WHAT part of that looks like Windows 3.1?
The real crime is that he made it to college...
...and you *could* run FF2 AND FF3 at the same time as this forum post shows.
I can't upgrade IE.
FWIW You can run IE6 and IE7 on the same machine fairly easily.
See this bug report for ttf-liberation.