From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: Guido Villa <piribillo@yahoo.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error with Sil3112A SATA controller and Maxtor 300GB HDD
Date: Sat, 12 Mar 2005 18:22:23 +0100 [thread overview]
Message-ID: <4233254F.3000509@roarinelk.homelinux.net> (raw)
In-Reply-To: <20050312160704.22527.qmail@gg.mine.nu>
Hi,
Guido Villa wrote:
> Hello,
>
> I have an error as described in subject.
> I couldn't find a previous report for this kind of error, so maybe you are
> interested in it.
>
> Motherboard: ASUS TUV4X, BIOS rev. 1005
> SATA controller: Silicon Image 3112A, bios rev. 4.2.50
> Hard disk: Maxtor Maxtor 6B300S0 (300GB, SATA)
>
> This is the only HDD attached to the controller. It is not the boot device,
> I have other HDDs on the IDE channels, but I don't think it matters.
I happen to have a SiI 3112A controller and a Maxtor 6B300S0 attached to
it, formatted with ext2. Never had any problems. I just copied
200GB of data to it, worked flawlessly. (Vanilla 2.6.11)
Maybe its the Motherboard?
> Kernels: 2.6.9, 2.6.10, 2.6.11.2
> I also patched the 2.6.11.2 by adding this Maxtor disk to the sata_sil.c
> blacklist (once with the SIL_QUIRK_MOD15WRITE and once with the
> SIL_QUIRK_UDMA5MAX), but the behaviour did not change.
>
> Problem:
> I create a single partition on the hard disk, I format it with ext2, I mount
> it, I begin writing onto the partition. After seconds (or minutes) of
> copying, I get this error:
>
> EXT2-fs error (device sda1): ext2_new_block: Allocating block in system zone
> - block = 22413316
>
> I have also tried with ext3, in this case it prints more error messages:
>
> EXT3-fs error (device sda1): ext3_new_block: Allocating block in system zone
> - block = 61997060
> Aborting journal on device sda1.
> EXT3-fs error (device sda1) in ext3_prepare_write: Journal has aborted
> __journal_remove_journal_head: freeing b_committed_data
> __journal_remove_journal_head: freeing b_frozen_data
> __journal_remove_journal_head: freeing b_committed_data
> __journal_remove_journal_head: freeing b_frozen_data
> __journal_remove_journal_head: freeing b_committed_data
> __journal_remove_journal_head: freeing b_frozen_data
> __journal_remove_journal_head: freeing b_committed_data
> __journal_remove_journal_head: freeing b_frozen_data
> __journal_remove_journal_head: freeing b_frozen_data
> ext3_abort called.
> EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
> Remounting filesystem read-only
> EXT3-fs error (device sda1) in start_transaction: Journal has aborted
--
Manuel Lauss
next prev parent reply other threads:[~2005-03-12 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 16:07 Guido Villa
2005-03-12 17:22 ` Manuel Lauss [this message]
2005-03-12 18:55 ` Guido Villa
2005-03-12 19:03 ` Jeff Garzik
2005-03-12 19:14 ` Guido Villa
2005-03-16 18:45 ` Guido Villa
2005-03-16 19:00 ` Jeff Garzik
2005-03-20 19:48 ` Manuel Lauss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4233254F.3000509@roarinelk.homelinux.net \
--to=mano@roarinelk.homelinux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piribillo@yahoo.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®