[EN] [SOLVED] kernel 3.5 towo produces filesystem errors

[hinto]

I updated and rebooted 4 systems this morning.  Three are KDE, one is LXDE, all use ext4.  Running 3.5-0, I find no issues in any of them, FYI.

BTW... do you have a vmplayer patch?
-Hinto

[clubex]

As I appear to be on my own I've purged kernel 3.5-0.towo and maybe reinstall it later although I think I'd rather wait for the next kernel update.

Thanks

[dibl]

BTW... do you have a vmplayer patch?
-Hinto

The vmware modules built for 3.5-0 with no issues.  Which module is failing to build?

[piper]

This has nothing to do with the kernel. To me, it looks like your basic filesystem//journal mismatch, when this happens, your filesystem gets mounted read-only immediately

[piper]

I use reiserfs,  so I had to do a little homework, you can **try** repairing it from a live cd (**warning** backup, **warning** backup)

once booted to live cd

Remove the journal from the filesystem, turning it into ext2:

Code: [Select]

tune2fs -O ^has_journal /dev/sda2
Use fsck it to correct any possible problems (throw in a -y flag to say yes to all repairs, -C for a progress bar):

Code: [Select]

e2fsck /dev/sda2make a new journal which effectively makes the partition an ext3 filesystem again:

Code: [Select]

tune2fs -j /dev/sda2mount the partition as an ext3 partition at this time:

Code: [Select]

mount -t ext3 /dev/sda2 /mnt/fixed

If sda2 is not your active partition change it to what is

This on the other hand might not work period, did I MENTION BACKUP

OppaErich has a good suggestion  also

It may be a failing/failed harddrive also

[clubex]

Thanks piper that's the first thing I've heard that makes sense. Still nothing explains why previous kernels work with no errors but I'll give your suggestion a try later. It'll be a few days as I have the in-laws arriving today for a short stay (but long for me!). I'll let you know.

Edit: I did a approx. 12 hr test of the HD overnight. No problems.

[DeepDayze]

By chance are there any disk hardware issues that may have been uncovered?

[OppaErich]

I have the in-laws arriving today

Have fun mate !  

[hinto]

BTW... do you have a vmplayer patch?
-Hinto

The vmware modules built for 3.5-0 with no issues.  Which module is failing to build?

Just checking to see if I needed one.
Smooth running on my desktop... Thanks.
-Hinto

[clubex]

Back again at long last. OppaErich: Yes the visit was as bad as you thought it would be!

I've reinstalled kernel 3.5 but I still get exactly the same /home partition file system errors on my PATA (IDE) HD.

I could try fixing the errors along the lines suggested by piper but that wouldn't explain why these errors only occur when running kernel 3.5. Anyway thanks piper.

So as nobody seems capable of supplying me with a satisfactory solution I've purged kernel 3.5 again and I shall continue DU-ing until the next kernel upgrade and see what happens then. Disappointing.

[clubex]

As I'm clearly on my own and going to have to help myself I've installed 3.5-0.slh.1-aptosid-amd64 kernel.  Been using it all morning with no file system errors or any other problems.

Comments anyone?

[clubex]

For those who may still be interested.....

The errors start appearing in towo's kernel immediately after the wmi: Mapper is loaded. Contrast this with slh's kernel below which starts the journal cleanly.

towo's kernel 3.5-0:

Jul 23 00:00:15 westfield kernel: [   11.315343] wmi: Mapper loaded
Jul 23 00:00:15 westfield kernel: [  353.888843] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jul 23 00:00:15 westfield kernel: [  353.889210] ata1.00: BMDMA stat 0x64
Jul 23 00:00:15 westfield kernel: [  353.889381] ata1.00: failed command: WRITE DMA
Jul 23 00:00:15 westfield kernel: [  353.889599] ata1.00: cmd ca/00:08:80:d1:e0/00:00:00:00:00/e1 tag 0 dma 4096 out
Jul 23 00:00:15 westfield kernel: [  353.889603]          res 51/84:00:87:d1:e0/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
Jul 23 00:00:15 westfield kernel: [  353.890314] ata1.00: status: { DRDY ERR }
Jul 23 00:00:15 westfield kernel: [  353.890502] ata1.00: error: { ICRC ABRT }
Jul 23 00:00:15 westfield kernel: [  353.890721] ata1: soft resetting link
Jul 23 00:00:15 westfield kernel: [  354.046467] ata1: nv_mode_filter: 0x7f39f&0x7f39f->0x7f39f, BIOS=0x7f000 (0xc7c50000) ACPI=0x7f01f (15:30:0x15)
Jul 23 00:00:15 westfield kernel: [  354.046485] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc7c50000) ACPI=0x1f01f (15:30:0x15)
Jul 23 00:00:15 westfield kernel: [  354.051638] ata1.00: configured for UDMA/133
Jul 23 00:00:15 westfield kernel: [  354.057403] ata1.01: configured for UDMA/66
Jul 23 00:00:15 westfield kernel: [  354.058563] ata1: EH complete
Jul 23 00:00:15 westfield kernel: [  354.058893] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jul 23 00:00:15 westfield kernel: [  354.059237] ata1.00: BMDMA stat 0x64
Jul 23 00:00:15 westfield kernel: [  354.059409] ata1.00: failed command: WRITE DMA

slh's kernel 3.5-0:

Jul 29 11:09:15 westfield kernel: [   11.354688] [drm] Initialized drm 1.1.0 20060810
Jul 29 11:09:15 westfield kernel: [   11.502821] wmi: Mapper loaded
Jul 29 11:09:15 westfield kernel: [   13.018866] kjournald starting.  Commit interval 5 seconds
Jul 29 11:09:15 westfield kernel: [   13.019547] EXT3-fs (sda2): using internal journal
Jul 29 11:09:15 westfield kernel: [   13.019559] EXT3-fs (sda2): mounted filesystem with writeback data mode
Jul 29 11:09:15 westfield kernel: [   14.115061] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 11:09:15 westfield kernel: [   14.202199] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 11:09:15 westfield kernel: [   14.390099] ip6_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 11:09:15 westfield kernel: [   16.462384] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
Jul 29 11:09:15 westfield kernel: [   16.462446] forcedeth 0000:00:07.0: eth1: MSI enabled

Would towo like to comment?

[devil]

If you have a new ATA cable, put that in and check if it still happens. Please do not argue, just do it. It might solve your problem.

greetz
devil

[hinto]

@clubex I've had this work.
At the same time, tho, I've had the south bridge burn out, which caused the SATA control to be flaky, until the south bridge burned out completely.
Check the heat of your motherboard.
BTW... My SB burned out due to a MB defect.  I'll no longer purchase a PC from that particular manufacturer.

-Hinto

[towo]

As i have written before, your problems are not the filesystem errors, the problem are the ata-errors above!
Again, those errors are typical for bad cable, especialy on PATA drives.

But never mind, you can test the recent uploaded kernel, it has the same config, as the slh-kernel.