[Bug 1063354] Re: Sudden Read-Only Filesystems
Lars Kumbier, as per http://www.dell.com/support/drivers/us/en/04/DriverDetails?driverId=R301708fileId=2731109636 an update is available for your BIOS (A15). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and just provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. ** Tags added: bios-outdated-a15 ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Attachment removed: ubuntu bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+attachment/3936193/+files/ubuntu-bug-report.log ** Attachment removed: lspci output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+attachment/3738793/+files/lspci.txt ** Attachment removed: ubuntu-bug linux-image-3.11.0-15-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+attachment/3937260/+files/bug-report-linux-image-generic_-_System_OK_2_days.txt ** Summary changed: - Sudden Read-Only Filesystems + [Dell Studio XPS 1640] Sudden Read-Only Filesystems ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: [Dell Studio XPS 1640] Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
[Problem probably solved] I changed my fstab and removed the defaults-entry: Probably this was the problem and the defaults-entry puts some mount options, that interfere with the ssd. fatab-NEW: /dev/mapper/vg--myvg-root /ext4noatime,errors=remount-ro 0 1 fstab-OLD: /dev/mapper/vg--myvg-root /ext4 defaults,noatime,errors=remount-ro 0 1 I left the libata option in modprobe and kernel boot options: cat /etc/modprobe.d/options options libata noacpi=1 cat /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT=quiet splash libata.force=noncq libata.noacpi=1 Since two days the system is running without any filesystem-freezes. I am attaching an ubuntu bug-report which can probably help to solve and analyse the problem. The system is up to date as time of writing and all necessary updates are applied. --- I have to add, that I am running a newer version of lvm2 with gives me the option of using TRIM: ii lvm2 2.02.95-4ubuntu1.1~p Linux Logical Volume Manager All necessary entries in crytptab and lvm.conf are done and trim is working (on demand). dmesg | grep libata [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/vg--madagaskar-root ro quiet splash libata.force=noncq libata.noacpi=1 [0.517478] libata version 3.00 loaded. dmesg | grep ata1 [1.400125] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 53 [1.717874] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.719776] ata1.00: FORCE: horkage modified (noncq) [1.719843] ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0BB0Q, max UDMA/133 [1.719848] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (not used) [1.720159] ata1.00: configured for UDMA/133 [12726.396872] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [12726.398974] ata1.00: configured for UDMA/133 [54682.379955] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [54682.382006] ata1.00: configured for UDMA/133 ** Attachment added: ubuntu-bug linux-image-3.11.0-15-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+attachment/3937260/+files/bug-report-linux-image-generic_-_System_OK_2_days.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Unfortunetely with the settings from above i was not lucky this morning. When I turned on the W510 notebook (#3.) it stuck like before. I really think, this is system specific for this laptop, because the other computers with itdentical software are running flawlessly ... 24/7 (via suspend / resume). I also have to add, that all disks run on lvm based cryptsetup! cat /var/log/syslog.1 | grep ata1 | cut -d [ -f2 1.419360] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 53 1.737774] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) 1.741004] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded 1.741014] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out 1.741020] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out 1.741298] ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0BB0Q, max UDMA/133 1.741303] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 1.742899] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded 1.742907] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered ou 1.742913] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out 1.743209] ata1.00: configured for UDMA/133 I will investigate further ** Attachment added: ubuntu bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+attachment/3936193/+files/ubuntu-bug-report.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Hi there,
I am running Ubuntu 12.04 LTS on three machines:
1. An intel xeon with an asus motherboard, 32GB RAM, SSD (SAMSUNG older model)
2. An Lenovo Thinkpad 201s i7, 8GB RAM, SSD (Crucial)
3. An Lenovo Thinkpad W510 i7 720, 8GB RAM, SSD (Samsung EVO)
All systems are running under kernel 3.11 (linux-image-generic-lts-saucy
, 3.11.0.15.14)
/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
/etc/modprobe.d/options: EMPTY
The #3 (W510) randomly freezes with the following errors:
ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 54
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0BB0Q, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata1.00: configured for UDMA/133
[...]
These errors occur up to 5-10 times, then the SSD is set to readonly
state like this:
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
ata1.00: irq_stat 0x0800, interface fatal error
ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
-
i am now trying the following settings:
/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
libata.force=noncq
/etc/modprobe.d/options: options libata noacpi=1
/etc/default/tlp (which was on standard setting until now)
# Hard disk advanced power management level: 1(max saving)..254(off)
# Levels 1..127 may spin down the disk.
# Separate values for multiple devices with spaces.
DISK_APM_LEVEL_ON_AC=254 254
DISK_APM_LEVEL_ON_BAT=254 254
# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=max_performance
I will write ... after further testing.
Please note: system #1. and #2. are running without any problems!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063354
Title:
Sudden Read-Only Filesystems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Hi, I can confirm Rahul Jain's observation: I am also on Mint 15. I had that problem since Mint 14, then not for a long while and yesterday it appeared again. In my case, I am sure, my Hardware is OK, no smart errors on the SSD, and as this is a notebook, I don't think, there are any pin problems on the connectors. I have noticed, that this problem appears every time, ther's heavy SDD activity, and lots of small data-blocks are beeing encrypted and written/read to the SSD. In particular yesterday I was enabling the calendar caching in my thunderbird lightning calendars. This provoked massive writing and reading operations. An other time that happened was again in thunderbird when I synchronized my 12GB IMAP Mailbox. I just tried to verify my theory about many little files/small data-blocks - I used bonnie++ to write many little files in a very fast manner. Result: same dmesg output, ends in kernel panic... This is a vital problem so a fix needs to be found asap. regards and merry Christmas , Felix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Had the same bug running kernel 3.11 on Mint 15 (which is based on Raring). Everything was fine for a long time until suddenly one day while downloading a torrent!!! my filesystem locked to read-only and torrent stopped. Reboot solved it, but two days later, it happened again. Definitely not a hardware issue as Elementary on kernel 3.2 on another partition is running perfectly. No smartctl errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Hi, I had exactly same problem and I solved it. My ubuntu 13.04 is installed on Intel SATA 2 SSD but was connected to the Motherboard on SATA 3 connector (in the past, this drive was for windows partition and no errors with the Marvell chipset SATA 3 with SATA 2 drive). I switch my SSD on SATA 2 connector then no problems I hope this may help you... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Just adding my input. I have the same read only file system problem for the first time this evening. No changes percipitated it. Running debian wheezy. No new info that hasn't already been served. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Just a follow up... My problem is fixed or at least figured out. Although many with this bug have similar log output mine was definitely hardware. SATA hard drives have extremely fragile connectors and the connector to this particular drive with the read only problem was slightly pushed down by another connector. It finally broke the HD plug socket just enough to make a bad connection. It's practically imperceptible until you remove the connector as see the slight movement of the HD plug component. I reconnected the plug and put slight pressure underneath the component, started the computer and it fired right up. The system did a forced fsck and it is working with all data present and permissions corrected. Now I just need to dump all the data to a new HD. This may be an issue for some and not for others but the outcome and the dmesg logs show ata errors on that drive. It would be very easy to miss the breakage since it's a very small variance, and it's bizaar that it causes the read only problem as stated above but nothing else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Update to my previous comment (#111). I installed an HDD (Western Digital Caviar Black) and since (2.5 months) there has been no problem... until just now. Rebooting does not solve it as it happens quickly after. My last installation has been without system encryption. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
O.K. seems many people still have this problem. The original bug report talks about /var/log/syslog. I think there is another bug that I experience and many other people do too. There is no error in the log files. The system suddenly goes read only without writing anything to the logs. As far as my very limited knowledge of linux goes, that means I should check dmesg when this happens? My work around for this bug has been to switch to cinnamon and never shutdown/reboot unless I really must. I suspend the pc and now the read only filesystem only happens every 2 or 3 months. Then fsck still deletes some files on reboot, usually firefox cache files, sometimes icons and rarely other files. Like movies :( and yes my HDD is perfect. I did read that there is a kernel issue for people who frequently shutdown/reboot their system that causes this issue but I can't find it again. Apparently is was a comment made by one of the kernel developers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Dear All, I also encountered the same issue with Ubuntu Server 13.04 while I was trying to checkout all Android projects. Exactly like TeamFahQ (teamfahq1) wrote on 2013-02-22: #99 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I currently dedicate a second Hard Drive to VirtualBox (1. I have a LOT of VM's, 2. I can use my primary HDD at full speed at the same time I am running a VM ) which runs Ext4 and this Read-Only bug only occurs when I run a specific VM. The VM is Windows XP Home Edition SP3 and every time I boot into it, the guest OS starts to give me Delayed Write Failed Errors and at the same time I lose write access to the partition. Haven't discovered any data loss nor does this VM contain any important data, annoying though. Am running the 3.5.0-17 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
'noncq' did not solve it for me either, not for 12.04-2 and not in 12.10. I had to pull my SSD and start a fresh install on an HDD. So far no read-only experience... Intel DX58SO2 motherboard. SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller SSD: Intel 510 120Gb, 6Gbps. Tried going through drive diagnostics, SMART looks fine, even did a low-level surface scan of the drive. Bug experiences on drive using both an ext2 and and ext4 (luks-encrypted and not) filesystem. Sorry I can't test around too much as this computer is critical in my everyday work. ** Attachment added: lspci output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+attachment/3738793/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
'noncq' does not solve the problem for me. I still can't go beyond kernel 3.0.0 without a lockup after a few minutes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I have the same problem on my Acer Aspire TimelineX under Ubuntu 12.04. libata.force=noncq seems to work. Daniel, have you run update-grub ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Hmm. Never mind. I guess I was over eager it was working fine for a couple of hours (after never lasting more than 90 minutes before, and very rarely more than an hour) but now it's not working again. I'm now wondering if I've got a different problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I started having this problem this weekend after I installed 13.04 (previously I was on 12.04, which was fine). Apparantly random filesystem corruption leading to unusable disk. It was happening pretty much every boot, taking 10 - 90 minutes before it went crazy. Adding libata.force=noncq to my grub config does seem to have fixed the problem. Let me know if I can help solve this with any logs or anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
@Rami, Thanks, this helps! :-) My problem looks solved with the solution from Rami: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/comments/105 suggested. I tried it for about two weeks and no problems till now. Before the read-only filesystem occurred about two times a week. /etc/default/grub Code: GRUB_CMDLINE_LINUX=libata.force=noncq -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Also hapenned to me when i upgraded my kernel in ubuntu 12.04 and now with a fresh install on 12.10. Smart runs ok. But my question is, if it's a general kernel problem, why there ins'y more people being affected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1063354] Re: Sudden Read-Only Filesystems
I know a lot of discussion right now is leaning towards dual-boot/multiple
partion disks. Just pointing out that I'm experiencing the error on a
desktop with a single HDD with only one OS.
On 1 March 2013 09:47, djahjah 1063...@bugs.launchpad.net wrote:
Also hapenned to me when i upgraded my kernel in ubuntu 12.04 and now
with a fresh install on 12.10. Smart runs ok. But my question is, if
it's a general kernel problem, why there ins'y more people being
affected?
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1063354
Title:
Sudden Read-Only Filesystems
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After upgrading to ubuntu 12.10, I experience sudden locks of my
filesystems (I have a root and a home partition with ext4), in which
the filesystems suddenly become mounted readonly. /var/log/syslog
shows the following entries:
Oct 7 20:00:42 StudioXPS signond[3510]: signondaemon.cpp 345 init
Failed to SUID root. Secure storage will not be available.
Oct 7 20:02:12 StudioXPS kernel: [ 249.193555] ata1.00: exception
Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Oct 7 20:02:12 StudioXPS kernel: [ 249.193561] ata1.00: irq_stat
0x4001
Oct 7 20:02:12 StudioXPS kernel: [ 249.193565] ata1.00: failed
command: READ FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] ata1.00: cmd
60/20:00:90:6f:53/00:00:1a:00:00/40 tag 0 ncq 16384 in
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] res
41/40:20:98:6f:53/00:00:1a:00:00/40 Emask 0x409 (media error) F
Oct 7 20:02:12 StudioXPS kernel: [ 249.193575] ata1.00: status: { DRDY
ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193578] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193581] ata1.00: failed
command: WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] ata1.00: cmd
61/18:08:18:fb:0e/00:00:2b:00:00/40 tag 1 ncq 12288 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193590] ata1.00: status: { DRDY
ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193593] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193596] ata1.00: failed
command: WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] ata1.00: cmd
61/d8:10:a0:bd:8b/00:00:0d:00:00/40 tag 2 ncq 110592 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193605] ata1.00: status: { DRDY
ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193607] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.196606] ata1.00: configured for
UDMA/100
Oct 7 20:02:12 StudioXPS kernel: [ 249.196622] sd 0:0:0:0: [sda]
Unhandled sense code
Oct 7 20:02:12 StudioXPS kernel: [ 249.196624] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196626] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Oct 7 20:02:12 StudioXPS kernel: [ 249.196628] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196629] Sense Key : Medium
Error [current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196633] Descriptor sense data
with sense descriptors (in hex):
Oct 7 20:02:12 StudioXPS kernel: [ 249.196634] 72 03 11 04 00
00 00 0c 00 0a 80 00 00 00 00 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196642] 1a 53 6f 98
Oct 7 20:02:12 StudioXPS kernel: [ 249.196645] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196648] Add. Sense: Unrecovered
read error - auto reallocate failed
Oct 7 20:02:12 StudioXPS kernel: [ 249.196650] sd 0:0:0:0: [sda] CDB:
Oct 7 20:02:12 StudioXPS kernel: [ 249.196651] Read(10): 28 00 1a 53
6f 90 00 00 20 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196658] end_request: I/O error,
dev sda, sector 441675672
Oct 7 20:02:12 StudioXPS kernel: [ 249.196674] sd 0:0:0:0: [sda]
Unhandled sense code
Oct 7 20:02:12 StudioXPS kernel: [ 249.196676] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196678] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Oct 7 20:02:12 StudioXPS kernel: [ 249.196679] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196681] Sense Key : Medium
Error [current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196683] Descriptor sense data
with sense descriptors (in hex):
Oct 7 20:02:12 StudioXPS kernel: [ 249.196684] 72 03 11 04 00
00 00 0c 00 0a 80 00 00 00 00 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196692] 1a 53 6f 98
Oct 7 20:02:12 StudioXPS kernel: [ 249.196695] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196697] Add. Sense: Unrecovered
read error - auto reallocate failed
Oct 7 20:02:12 StudioXPS
[Bug 1063354] Re: Sudden Read-Only Filesystems
I got my problem circumvented with disabling NCQ, so I don't know if my problem is the same as the one reported. /etc/default/grub Code: GRUB_CMDLINE_LINUX=libata.force=noncq Also connecting through Intel P55 s-ata 3 Gb/s worked, so I suppose my problem is related to Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller (rev 10) http://markmail.org/message/dt7dnl3pubvwcmmm https://bugzilla.kernel.org/show_bug.cgi?id=43160 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550559 http://ubuntuforums.org/showthread.php?t=1396465 http://ubuntuforums.org/showthread.php?t=1480965 system info: ubuntu 12.04 and 13.04 ASUS P7P55D-E PRO mainboard with the Marvell 88SE9123 PCIe SATA 6.0 onboard controller Samsung SSD 840 PRO Series (DXM03BQ0) ssd / 1T WDC WD10EZRX-00A8LB0 (01.01A10) hdd -with the hdd the errors didn't occur so often, once in a week / two weeks, twice a day, dependind, but with the ssd up to several times a day. ** Bug watch added: Linux Kernel Bug Tracker #43160 http://bugzilla.kernel.org/show_bug.cgi?id=43160 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I had the same problem running Kernel 3.5.0-23. After downgrading to 3.5.0-19 the system is running fine for two weeks now. There have been a number of ext4 changes between these version: * ext4: fix unjournaled inode bitmap modification (LP: #1091251) * ext4: remove erroneous ext4_superblock_csum_set() in update_backups() (LP: #1084539) * ext4: race-condition protection for ext4_convert_unwritten_extents_endio (LP: #1084539) * ext4: fix metadata checksum calculation for the superblock (LP: #1084539) * ext4: Checksum the block bitmap properly with bigalloc enabled (LP: #1084539) * ext4: Avoid underflow in ext4_trim_fs() (LP: #1084539) Could any of these changes cause the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Mark Davidson (outdoorshappy) wrote on 2013-02-21:#98 a bad drive. Certainly not in my case. My drive is a brand, spanking new 512GB Samsung 840 Pro and SMART is squeky clean. I realize that without detailed diagnostics When you mean to say wild speculation, please say wild speculation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Hello! Well, recently I upgraded from Kubuntu 12.04 to 12.10 and also
started to experience this issue, it just started to happen since I
upgraded to 12.10, I never experienced it with Precise Pangolin. About
the error message, I don't need to perform a specific task to trigger
it, it has happened when I'm working or when I'm just using the web
browser alike, and there's not a signal to predict when the error is
about occur, and as my computer is my day-to-day working tool, this
issue is very frustrating.
System info:
CPU: Sempron single core 1.8 GHz, 64 bit.
RAM: 3GB
OS: Kubuntu 12.10 (upgraded from 12.04).
Kernel: Linux 3.5.0-25-generic (x86_64)
Nvidia GeForce Go6150 grqphics with nvidia privative controller.
I do dual boot with Windows 7; my /home and / partitions are both in
separated partitions and are formatted as ext4. I ran also fsck test,
and the error has became a bit less frequent, but it persists; also, the
SMART analysis didn't throw any errors.
** Description changed:
After upgrading to ubuntu 12.10, I experience sudden locks of my
filesystems (I have a root and a home partition with ext4), in which the
filesystems suddenly become mounted readonly. /var/log/syslog shows the
following entries:
- Oct 7 20:00:42 StudioXPS signond[3510]: signondaemon.cpp 345 init Failed to
SUID root. Secure storage will not be available.
+ Oct 7 20:00:42 StudioXPS signond[3510]: signondaemon.cpp 345 init Failed to
SUID root. Secure storage will not be available.
Oct 7 20:02:12 StudioXPS kernel: [ 249.193555] ata1.00: exception Emask 0x0
SAct 0x7 SErr 0x0 action 0x0
Oct 7 20:02:12 StudioXPS kernel: [ 249.193561] ata1.00: irq_stat 0x4001
Oct 7 20:02:12 StudioXPS kernel: [ 249.193565] ata1.00: failed command:
READ FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] ata1.00: cmd
60/20:00:90:6f:53/00:00:1a:00:00/40 tag 0 ncq 16384 in
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] res
41/40:20:98:6f:53/00:00:1a:00:00/40 Emask 0x409 (media error) F
Oct 7 20:02:12 StudioXPS kernel: [ 249.193575] ata1.00: status: { DRDY ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193578] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193581] ata1.00: failed command:
WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] ata1.00: cmd
61/18:08:18:fb:0e/00:00:2b:00:00/40 tag 1 ncq 12288 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193590] ata1.00: status: { DRDY ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193593] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193596] ata1.00: failed command:
WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] ata1.00: cmd
61/d8:10:a0:bd:8b/00:00:0d:00:00/40 tag 2 ncq 110592 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193605] ata1.00: status: { DRDY ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193607] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.196606] ata1.00: configured for
UDMA/100
Oct 7 20:02:12 StudioXPS kernel: [ 249.196622] sd 0:0:0:0: [sda] Unhandled
sense code
- Oct 7 20:02:12 StudioXPS kernel: [ 249.196624] sd 0:0:0:0: [sda]
+ Oct 7 20:02:12 StudioXPS kernel: [ 249.196624] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196626] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
- Oct 7 20:02:12 StudioXPS kernel: [ 249.196628] sd 0:0:0:0: [sda]
+ Oct 7 20:02:12 StudioXPS kernel: [ 249.196628] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196629] Sense Key : Medium Error
[current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196633] Descriptor sense data with
sense descriptors (in hex):
- Oct 7 20:02:12 StudioXPS kernel: [ 249.196634] 72 03 11 04 00 00 00
0c 00 0a 80 00 00 00 00 00
- Oct 7 20:02:12 StudioXPS kernel: [ 249.196642] 1a 53 6f 98
- Oct 7 20:02:12 StudioXPS kernel: [ 249.196645] sd 0:0:0:0: [sda]
+ Oct 7 20:02:12 StudioXPS kernel: [ 249.196634] 72 03 11 04 00 00 00
0c 00 0a 80 00 00 00 00 00
+ Oct 7 20:02:12 StudioXPS kernel: [ 249.196642] 1a 53 6f 98
+ Oct 7 20:02:12 StudioXPS kernel: [ 249.196645] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196648] Add. Sense: Unrecovered read
error - auto reallocate failed
- Oct 7 20:02:12 StudioXPS kernel: [ 249.196650] sd 0:0:0:0: [sda] CDB:
+ Oct 7 20:02:12 StudioXPS kernel: [ 249.196650] sd 0:0:0:0: [sda] CDB:
Oct 7 20:02:12 StudioXPS kernel: [ 249.196651] Read(10): 28 00 1a 53 6f 90
00 00 20 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196658] end_request: I/O error, dev
sda, sector 441675672
Oct 7 20:02:12 StudioXPS kernel: [ 249.196674] sd 0:0:0:0: [sda] Unhandled
sense code
-
[Bug 1063354] Re: Sudden Read-Only Filesystems
Just got a dell 6430s computer. It worked fine for a day then started freezing with same errors as previous posters. Can freeze almost at once after login or it works for hours. ( 256 gb ssd disk in comp, done a complete syscheck twice and no errors on disk or other hardware ) Computer is unusable at the moment :-( Since i cant rely on it at work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This may be related to this bug or it may not, but I will add it to the growing data-stream to try to help. My system 12.04 ubuntu, then mythbuntu was showing exactly the same symptoms as this bug describes. It is a dual boot system with Win8 and ubuntu. Win8 was stable, ubuntu was not. Smart diagnostics were fine at first (hint of where we are going ;-) ) After 6 weeks of chasing the problem with multiple crashes, freezes, etc. I the smart diagnostics started coming up with some bad/suspect sectors. These were scattered around the disc in both the win8 and ubuntu partitions.They continued to grow until the drive failed specification--i.e. a bad drive. I realize that without detailed diagnostics saved all through the process, this is total speculation, but perhaps as a hypothesis/place to look is in the handling of bad/failing sectors on the disc. Throughout the process, win8 never lost stability or data, but parts of the ubuntu would periodically crash due to read errors trying to read those nearly failed, intermittent sectors. I don't know enough (nearly nothing) about the back end of this, but that may be a difference here. I replaced the drive 2 weeks ago and have had no further crashes or freezes (at least at this point). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Not sure if this will help anyone on this issue, but I just experienced it as well. For my own personal reasons, I have my android build environment on a separate partition. I opened it and decided to do some work on a project and suddenly all my partitions became read only. I found that after a reboot, I was forced to run fsck, but I also found that if I did not try to change anything in my android partition, that this error would not happen. I also noticed that prior to this error, when I tried to compile any of my android projects, my computer would become very slow and seemingly overloaded. So... After a reboot, I ran fsck /dev/sda3 (my android partition)and now I am read only error free, and I am currently compiling a ROM, listening to youtube videos, typing out this reply and have supertuxcart (I love that game...lol) running in the background with no lag. So, my system is back up and running like it should be. Oh, and for your information: Machine: Acer Aspire 5560 Kernel: Linux 3.5.0-25-generic (x86_64) Distribution: Linux Mint 14 Nadia Processor: 4x AMD A6-3400M APU with Radeon(tm) HD Graphics I know Linux Mint is not Ubuntu, but it is still based on 12.10 I'm sure if this is happening on your main partition (/dev/sda1 for me), you would need to do this from a live cd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This problem was plaguing me lately as well on my primary ext4 partition. I first thought the HDD was failing, but I wasn't getting any SMART errors. Also, the HDD this is happening to is only 8 months old. Just to be safe, I ran a ddrescue dump, and it ran through fine with no errors. I'm running Ubuntu on some old hardware: an ASUS P5N-E SLI motherboard (nForce 650i chipset) with a Core 2 Duo CPU. As suggested, I rebooted and selected an older kernel in GRUB, and have been running fine for almost a week now. This leads me to believe the problem is with the kernel and not my hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Same here with an Ion-nvidia any luck out there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I'm having the same problem. Started on my husbands Gateway laptop with 650GB HDD and then, 3 days later started on mine, while I was in the midst of attempting to determine whether his harddrive was failing or whether a simple re-install would work. The latter seems to have fixed his... and I've told him *not* to update his linux kernel. Debating whether its worth it to do the same to mine now (mine's a Lenovo IdeaPad w/ 500gb hdd, both just over a yr old). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I thought I would say that I too am having the same problem, although am not using SSD. I am using a HDD drive. I am getting the problem on my Ubunto 12.10 partition and on my Mint14 partition. My problems are not happening every day, so it makes it more difficult to be of any help. However,I did get the impression that I would have the problem after using a terminal session and SU. It could be a coincidence, but I thought I would share the information. Intel® Core™2 Duo CPU T7100 @ 1.80GHz × 2 OS 32-bit Not sue where to find the details for kernel version. PhilB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I have been following this bug from close to when it was first posted (because I had the same issue myself) and I am now convinced that this has become a gathering place for people who all have different hardware issues which all end up producing the noticable issue of the hard drive going into read-only mode (because the newer kernels seem to be more picky about filesystem errors now?.. which is good thing). Everybody having issues should do the following things: 1. Make sure you are using good quality 6 Gbps rated SATA cabling. 2. Make sure you have the power cable going directly from the power supply to the back of the HD and also have the SATA cable going directly from the motherboard to back of the HD. (no in-between connectors or hot-swap bracketing) 3. Make sure you have a power supply on your system that is rated at a high enough wattage to handle every card and storage device, etc.. you have connected. 4. Run SMART tests on your affected HD. This means installing smartmontools within Ubuntu and also running tests via your BIOS interface (if your BIOS has that available). This will rule out actual problems with the HD itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Missed an extra step to take if you are using a SSD... make sure you have the most up-to-date firmware (as mentioned by Mark above in this thread). Probably not a bad idea for everyone to check if their motherboard BIOS is up-to-date as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1063354] Re: Sudden Read-Only Filesystems
No, it's not. Hdd here. Am 01.02.2013 06:20 schrieb Mark Mandel 1063...@bugs.launchpad.net: I had much the same thing a while back, and a co-worker suggested I update the firmware on my Crucial M4 SSD drive, and I've not had a problem since. Worth a shot! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1063354] Re: Sudden Read-Only Filesystems
Same here. I'm on an ancient athalon xp machine with sata hdd so...
On Feb 1, 2013 3:25 AM, Lars Scheithauer 1063...@bugs.launchpad.net
wrote:
No, it's not. Hdd here.
Am 01.02.2013 06:20 schrieb Mark Mandel 1063...@bugs.launchpad.net:
I had much the same thing a while back, and a co-worker suggested I
update the firmware on my Crucial M4 SSD drive, and I've not had a
problem since.
Worth a shot!
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1063354
Title:
Sudden Read-Only Filesystems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1063354
Title:
Sudden Read-Only Filesystems
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After upgrading to ubuntu 12.10, I experience sudden locks of my
filesystems (I have a root and a home partition with ext4), in which
the filesystems suddenly become mounted readonly. /var/log/syslog
shows the following entries:
Oct 7 20:00:42 StudioXPS signond[3510]: signondaemon.cpp 345 init
Failed to SUID root. Secure storage will not be available.
Oct 7 20:02:12 StudioXPS kernel: [ 249.193555] ata1.00: exception
Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Oct 7 20:02:12 StudioXPS kernel: [ 249.193561] ata1.00: irq_stat
0x4001
Oct 7 20:02:12 StudioXPS kernel: [ 249.193565] ata1.00: failed
command: READ FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] ata1.00: cmd
60/20:00:90:6f:53/00:00:1a:00:00/40 tag 0 ncq 16384 in
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] res
41/40:20:98:6f:53/00:00:1a:00:00/40 Emask 0x409 (media error) F
Oct 7 20:02:12 StudioXPS kernel: [ 249.193575] ata1.00: status: { DRDY
ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193578] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193581] ata1.00: failed
command: WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] ata1.00: cmd
61/18:08:18:fb:0e/00:00:2b:00:00/40 tag 1 ncq 12288 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193590] ata1.00: status: { DRDY
ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193593] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193596] ata1.00: failed
command: WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] ata1.00: cmd
61/d8:10:a0:bd:8b/00:00:0d:00:00/40 tag 2 ncq 110592 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193605] ata1.00: status: { DRDY
ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193607] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.196606] ata1.00: configured for
UDMA/100
Oct 7 20:02:12 StudioXPS kernel: [ 249.196622] sd 0:0:0:0: [sda]
Unhandled sense code
Oct 7 20:02:12 StudioXPS kernel: [ 249.196624] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196626] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Oct 7 20:02:12 StudioXPS kernel: [ 249.196628] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196629] Sense Key : Medium
Error [current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196633] Descriptor sense data
with sense descriptors (in hex):
Oct 7 20:02:12 StudioXPS kernel: [ 249.196634] 72 03 11 04 00
00 00 0c 00 0a 80 00 00 00 00 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196642] 1a 53 6f 98
Oct 7 20:02:12 StudioXPS kernel: [ 249.196645] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196648] Add. Sense: Unrecovered
read error - auto reallocate failed
Oct 7 20:02:12 StudioXPS kernel: [ 249.196650] sd 0:0:0:0: [sda] CDB:
Oct 7 20:02:12 StudioXPS kernel: [ 249.196651] Read(10): 28 00 1a 53
6f 90 00 00 20 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196658] end_request: I/O error,
dev sda, sector 441675672
Oct 7 20:02:12 StudioXPS kernel: [ 249.196674] sd 0:0:0:0: [sda]
Unhandled sense code
Oct 7 20:02:12 StudioXPS kernel: [ 249.196676] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196678] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Oct 7 20:02:12 StudioXPS kernel: [ 249.196679] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196681] Sense Key : Medium
Error [current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196683] Descriptor sense data
with sense descriptors (in hex):
Oct 7 20:02:12 StudioXPS kernel: [ 249.196684] 72 03 11 04 00
00 00 0c 00 0a 80 00 00 00 00 00
Oct 7 20:02:12 StudioXPS kernel: [
[Bug 1063354] Re: Sudden Read-Only Filesystems
I've also been experiencing this bug. I'm running Ubuntu 12.10 on x64 with an SSD using 3.5.0-22. I'm seeing the issue about twice daily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
this is still a problem? I switched to elementaryOS (3.2.0-36) and don't have any problems. I actually wanted to switch to Xubuntu 12.10 or Linux Mint 14 XFCE, but I'm afraid of this sudden read-only experience again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
SSD I'm wondering if that's the common denominator. I too use SSDs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I had much the same thing a while back, and a co-worker suggested I update the firmware on my Crucial M4 SSD drive, and I've not had a problem since. Worth a shot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Has this problem been rectified? I recently installed Ubuntu 12.10 x64 on a new laptop and I've been running into this. I thought the problem might be the HDD (And was thinking about RMAing the HDD at least). I am currently on the latest kernel (3.5.0.22.28). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I will add my 2 cents if this helps. I am running 12.10 . If I use the 3.3 kernel I never see this problem. With the 3.5, 3.6, 3.7 and 3.8 kernels my ext4 file system will suddenly become read-only. This happens at least once a day. It was happening to both my boot and data partitions, but, I reformatted my boot to ext3 and now this only effects the data. I would reformat that to ext3 as well except it's rather large. So far I have not experienced any data loss, just need to reboot . fdisk -l /dev/sda Device Boot Start End Blocks Id System /dev/sda1 1204016386268 82 Linux swap /dev/sda22041612032764567 83 Linux /dev/sda36121 121601 9275931005 Extended /dev/sda56121 1020032764567 83 Linux Warning: Partition 5 does not end on cylinder boundary. /dev/sda6 10201 1428032764567 83 Linux Warning: Partition 6 does not end on cylinder boundary. /dev/sda7 14281 121601 862047900 83 Linux Warning: Partition 7 does not end on cylinder boundary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Looks like in my case, the issue did end up being hardware.. or 3.5+ kernel fault tolerance. After doing multiple SMART scans and replacing my cabling and still getting corruption (but only in 3.5+ kernels while 3.2 continued to be ok), I finally removed the hard drive from the case bay (which has a bracket adapter where you plug in the power and sata cable) and I am getting no corruption at all anymore in the 3.5+ kernels. In summary, plugging the power cable and SATA cable directly to the power supply and motherboard (with no bracketing connectors between) fixed all my corruption issues in the 3.5+ kernel. (whereas the same bracketing works fine with 3.2 kernel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This has happened for me in both Ubuntu 12.10, running whatever kernel it shipped with after release, and Arch Linux, running 3.6 and 3.7 kernels. It happens about twice a week in my case. I have an Asus zenbook with an ssd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This has happened for me in both Ubuntu 12.10, running whatever kernel it shipped with after release, and Arch Linux, running 3.6 and 3.7 kernels. It happens about twice a week in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This has absolutely nothing to do with Asus motherboards, btw. This issue affects me and I do not use Asus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I don't have an Asus motherboard, as well, and am affected nevertheless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
What a thundering great bug this is. Great advertising for Micro$oft. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Some more information that might help isolating this bug. I have a ASUS P5N-D board with a Pentium processor. It was when I upgraded from 11.10 to 12.10 the trouble started. I seldom get past a complete boot in 12.10, it is very unstable. To make the system work, I have to boot with kernel 3.0.0 from 11.10. This makes me believe the error was introduced in the kernel around 3.1 or 3.2. I haven't seen that other distros have this problem, which probably means it is a local Ubuntu problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
of course it is a local ubuntu problem, n it could be great if the give any solution to this issue, as any solution for other boot problems... n so maybe they will get that 200 million ppl... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I have to imagine this issue is affecting many, many more people. I've tried hundreds of search strings over the past few months on google and this is the first time I ever had a proper hit. Using GoatZilla's errors (the 1-4 post above), I've had all four, but have actually made it past installation- you have to somehow remove the ubiquity-slideshow-*buntu package before installing. Even after that, though, sometimes different packages will fail to install, and the system, when it does actually work, never fully is stable. I've tried numerous different 12.10 variants (currently running xubuntu with the kubuntu packages installed). Using KDE or Gnome over Unity helps alleviate some of the issues, but, as everyone else seems to know, it won't fix them. I thought maybe it was just related to me having an ancient AMD XP2400 based system with the original 80gb SATA 1 drives, but since they don't report errors under any other circumstances EXCEPT after a hiccup or on machines running different OSes, I can kind of rule those out. As also reported, it doesn't really matter what programs are running, the errors/kp's/et cetera are truly random. I don't know what to provide that could be remotely useful, since it seems that no one is actively monitoring the situation... Things are looking desperate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Happens to me as well. It didn't happen after some updates in November, but recently i encountered this problem again, and it's really annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Canonical appears too busy playing with their phones to give this any attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
i think... i have to many errors in my system... also by starting n by anything im doing... ive installed a lot of times... n up now is that not solved with the read only-system such things let me think that ubuntu never gonna get that millions of users that promised mr mark shuttleworth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This bug has occurred to me for the first time hours ago: Mint 13 KDE x86 vmware virtual machine - the virtual hard drives stored in VMDK files residing on a normal (non-ssd) hard disk. I was copying 3 folders and Dolphin asked me if I want to merge the folders with the existing one. Then it asked me to replace or leave an existing file. I chose to rename the new one. Then, suddenly, I started seeing boxes telling me that file X could not be moved. Options were 'Auto skip', 'skip' and 'cancel'. I started skipping one by one before I investigated the reason; read-only file system!!! DATA LOSS OCCURRED as I lost files in (at least) one existing folder (destination partition). This is a dangerous bug as it involves data loss. Linux destiny is at stake! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This seems to happen to me whenever I attempt apt-get dist-upgrade. But not every time - it seems kinda random. I've just noticed that my root file system is ext3 (not ext4) but I'm sure that will not cause any issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I would post some logs - but I lose them every time the system goes read only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I got this bug on Xubuntu 12.10 64bit and also on Linux Mint 14.1 64bit Cinnamon. Motherboard: Gigabyte GA-B75M-D3H. S-ATA HDD ext4 for / and for /home partitions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Ok, after 2-3 days I had some WRITE FPDMA QUEUED error even with 3.2.34 kernel and 3.2.0 too, but *much less* often. So now I think it's a hardware problem, but kernel version 3.5.0 somehow makes it happen much more often. Strange. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I've lost a whole lot of icons. Now menus have about one out of ten as the default purple diamond. Still no error in syslog anymore. How can I track this before I can longer boot... It will happen eventually when the right file gets wrongfully deleted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Confirmed with kernel 3.5.0-20, my motherboard is an old Asus P5K PRO.
The bug is easily reproducible after a few gigabytes transfer (I get
errors and my root is remounted readonly as specified in /etc/fstab).
Pretty often I couldn't even boot!
Sample of dmesg output.
[10188.832037] ata4.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[10188.832043] ata4.00: failed command: WRITE FPDMA QUEUED
[10188.832049] ata4.00: cmd 61/10:00:c4:50:dc/00:00:0b:00:00/40 tag 0 ncq 8192
out
[10188.832049] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4
(timeout)
[10188.832052] ata4.00: status: { DRDY }
[10188.832054] ata4.00: failed command: WRITE FPDMA QUEUED
[10188.832059] ata4.00: cmd 61/08:08:04:88:dc/00:00:0b:00:00/40 tag 1 ncq 4096
out
[10188.832059] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
This bug made me buy a new hard drive, and probably corrupted a bunch of files,
too.
Turned out that the hard drive was not the culprit, most definitely.
No problem with kernel 3.2.34.
Also, IMHO it would be good to provide an older kernel version in 12.10
repository!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063354
Title:
Sudden Read-Only Filesystems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
gunwald, my file has max_performance in it. did you completely delete the line or change it to something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I found a workaround for this bug: I had script to configure some power saving options and this script hat the following line: echo min_power /sys/class/scsi_host/host0/link_power_management_policy Since I deleted this line the problem does not occur anymore. I had this option switched on for one year an the bug occurred since Ubuntu 12.10. That leads me to the conclusion: The bug must have to do something with power saving of the scsi host and there must be a change between linux 3.2 and 3.5 that leads to the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
May be the problem has to do something with ALPM. Could that be? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I now think there are more than one simple bug to trigger Sudden Read-Only Filesystems I've now been getting one where there is no error in the syslog. When using unity it happens anywhere from UI start to several hours later. Using cinnamon it happens maybe once a week. I have no idea on how to get info on the error as the system goes readonly without writing any errors to logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I am trying 3.5.0-20 as well, and while it has not yet gone read-only, I AM still seeing write errors in /var/log/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
6 hours up time. No read-only. No error in /var/log/syslog. Sounds good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
After 13.5 hours, syslog started reporting errors, and disk turned read-only 30 minutes later. Too bad, 3.5.0-20 is not the solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Testing with 3.5.0-20 so far, so good... No issue at this time, while with a previous kernel, it was a matter of minute before turning read-only. I keep you updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Just upgraded to 3.5.0-19; seems to work fine for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Also happens to me. Running 12.10 with 3.5.0-18-generic x86_64. For the record: Hard drive 5400 RPM from Seagate Lenovo is mainboard vendor Happens both on battery and plugged in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
this seems to be a problem with Asus motherboards, I have the same problem on mine. https://bugzilla.redhat.com/show_bug.cgi?id=549981; I also have a Asus (k52Je notebook + SSD). On other computers no problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
After using kernel 3.5.0-19 for 5 days I am still getting file corruption reported in syslog, but not nearly as much as before (or perhaps just seems that way). Going back to 3.4 again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I have the issue with an ASUS P5N-D Motherboard (Nvidia chip) I have another kind of intel Asus Motherboard (Intel ICH10 chip) which seems to have no issue with 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
this seems to be a problem with Asus motherboards, I have the same problem on mine. https://bugzilla.redhat.com/show_bug.cgi?id=549981 ** Bug watch added: Red Hat Bugzilla #549981 https://bugzilla.redhat.com/show_bug.cgi?id=549981 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
May be that he bug occurs only with Asus motherboards. I have tow machines with same Ubuntu and kernel an only the Asus Zenbook has that bug. But I guess, that the problem is related with some power saving options of the kernel. Because it seems only to occur when my computer runs on battery. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
For reference, my hardware configuration: ASUS M4A78T-E, Phenom X4, 16G DDR3, 750M HDD + 1T SATA HDD. I'm using kernel 3.5.0-17 for several days and I have no problem. I'll try to test a newer kernel to see if makes some difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Well, I tested 3.5.0-19 and 3.5.1, and both don't recognize my keyboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I've been using 12.10 but have continued booting with the old 3.4.0 kernel for about 2 weeks now and have had no problems. I just installed the 3.5.0-19 kernel and will see how I do with that... will report back soon. AMD Phenom X4 / ASUS M4A87TD / 16Gig DDR3 / 750M WD SATA HD / NVIDIA GeForce 520GT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Was this issue corrected on 3.5.0-19? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Question: Is it the good place to report this bug since nobody seems to be assigned to it. I wonder if kernel.org may not be the good place? If anybody has a link to this bug on kernel.org I may appreciate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I also had this bug in Xubuntu 12.10 and I don't have SSD. Now I'm using Xubuntu 12.04 and have no problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I have a SSD, but the issue is with my standard HD which is mounted in /home. I actually returned to Ubuntu 12.04 since I could not afford loosing data and/or having my /home becoming read-only after only 2 minutes. I really don't understand why such major bug is not taken seriously and how filesystem corruption and loss of data is not considered as a critical issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Wallo013, I believe there is not a consistent pattern to the issue yet. Read all the posts here and you can see some people not having problems with kernel 3.5.0-17 but do with 3.5.0-18... whereas myself I can't reliably use any 3.5.* kernel it seems. I'm still not convinced that I (and all others posting in this thread) are not just having failing hardware (MB, ram, cabling, HD, connectors, etc..) since the problems reported have so much variation. I recently tried changing my SATA cabling (got high quality 6Gb type) but that didn't help. It is odd that I'm not getting the problem with pre 3.5.* kernels, but maybe I do and just haven't noticed in the logs yet as perhaps older kernels have higher fault tolerance. But what do I know, I'm just taking guesses here. If this is a real bug causing unnoticed and progressive data corruption for everyone, this is indeed HUGE and should be getting top priority. Would be nice to hear opinions from some of the official kernel/ext4 coders here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
The consistent pattern is: it happens with 12.10. I spent the last two nights fiddling with this. 1. Sometimes the installer will crash during installation. 2. Sometimes you can make it through the installation, but it won't fully boot (either hangs at starting X/window manager, or grub acts funny). 3. Sometimes you can fully boot, start an update, and the update crashes (and that's where you can see the read-only filesystem message). 4. Sometimes you can make it all the way through the first update, reboot, and the system won't fully boot (looks like it starts to fire up the window manager then it just sits there). I'm running 32-bit with an AMD system and have tried multiple SATA SSD's and cables. I tried just cutting out the SSD and installing/running on a USB flash key, and that alleviates 1-3, but 4 still happens every time. This looks like a filesystem issue; haven't had a chance to try reformatting root with ext3. Kinda dumped enough time on this as is. Finally, I just gave up, went back to 12.04.1, on the exact same hardware, and everything runs perfectly, first shot. System specs are fairly straightforward: AMD A4-3300 MSI A55M-P33 2GB DDR3 1 SATA Blu-Ray 1 SATA SSD (Tried with two different drives with same results -- Torqx, and OCZ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
AMD-64, GA-880GMA-UD2H (gigabyte). I doubt this is a hardware specific problem. 3.5.0-17 kernel has the same problem. No information to the error in syslog the past 2 times. Sometimes I get the same output as in original bug post. Luckily only firefox files were fixed by fsck I'm fairly sure it started at some point in 12.04. It happens usually once or twice a week but sometimes twice a day (pc is on 16hours a day). I think you would have to test a kernel for a week to be sure. Unfortunately I removed most of the old kernels. I won't do that again. What can I do to get more info on this error? dmesg? I thought it happened only slightly more often when doing a lot of software installs/sudo commands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
This bug drives me crazy because it makes me loosing data! I experienced this bug the first time, when I installed linux 3.5 in Ubuntu 12.04. I could get rid of it by turning back to linux 3.2. Know I am using Ubuntu 12.10 and the problem occurs constantly. But only on computers with SSD hard drives. Actually I running Ubuntu on an Zenbook UX 21. Please fix that bug, its the worst bug Ubuntu ever had. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Seems a lot of people running into this issue are all using SSDs, myself included. Anybody else in this thread having the same thing happen using an old spinner drive? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I'm not using SSD. There is a possibility it happens more with SSDs. I've found the bug happens more often when using unity rather than cinnamon or gnome 3.6. It's weird. I'm thinking of going back to unity to see if I can get info on the bug and what might trigger it but I don't want to lose more files. At ferlantz (fagmj74) suggestion, I've been using 3.5.0-17 kernel to see if that avoids the bug. No problems for the past few days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I also have this problem. I used 12.04 without problems for 6 months and in 12.10 the system ended up with a read-only filesystem and now without booting. I have a intel 120gb SSD with 4 partitions. Ubuntu 12.10 (64bit) is only installed on one partition, including the /home. It also has a boot flag. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
** Tags removed: performing-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Another one bites the dust. Losing data is not ok. This is happening in shorter intervals by now. I have two different hdds, same kind, one in use, the other just for backups. When I first got these errors I've immediately exchanged drives, I thought I was about to witness a spectacular hardware failure. Now the second drive is having the same problems, in shorter intervals. This is the worst bug I've experienced in all my years as a Linux user. Not good at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I just updated from 12.04 to 12.10 (64 Bit) and a few days later, hell broke lose: the computer doesn'T boot corretc, lots of boot failers, disk checks on every boot and after several boot, the login screen appears. But the system is read only. I have an Intel 80 GB SSD with / and /home partitions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
this bug is so annoying, definitely critical since it really makes ubuntu unusable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I hit this same issue after upgrading to 12.10, so decided to downgrade back to 12.04 for the time being (both were fresh installs). After a couple of hours running in 12.04 my file-systems have once again gone into a read-only mode running on the stock 3.2.0 kernel used in 12.04 so at least for me it seems as if it's not just limited to the 3.5.0 kernel used in 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I have the same trouble with kernel 3.5.0-18, 3.5.0-17 works OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Happened again. Seems to happen less using cinnamon rather than unity. I lost the syslog on reboot along with 12 files (1GB) from a single directory I was not using at the time. Usually I only have firefox cache/data and whatever app is open at the time show up as file errors on boot (fsk?) but now it's other files too. ... and yes, My HDD is fine. When your OS starts deleting your files, I think it's a critical bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
Noticed that kernel 3.5.0-18 was included in my updates today so I just tried booting with it. Within minutes I started getting errors in my /var/log/syslog as follows: Nov 6 17:04:31 Woogie kernel: [ 1676.289748] Buffer I/O error on device sda3, logical block 96221046 Nov 6 17:04:31 Woogie kernel: [ 1676.289749] Buffer I/O error on device sda3, logical block 96221047 Nov 6 17:04:31 Woogie kernel: [ 1676.289750] Buffer I/O error on device sda3, logical block 96221048 Nov 6 17:04:31 Woogie kernel: [ 1676.289751] Buffer I/O error on device sda3, logical block 96221049 Nov 6 17:04:31 Woogie kernel: [ 1676.289752] Buffer I/O error on device sda3, logical block 96221050 Nov 6 17:04:31 Woogie kernel: [ 1676.289753] Buffer I/O error on device sda3, logical block 96221051 Nov 6 17:04:31 Woogie kernel: [ 1676.289754] Buffer I/O error on device sda3, logical block 96221052 Nov 6 17:04:31 Woogie kernel: [ 1676.289756] Buffer I/O error on device sda3, logical block 96221053 Nov 6 17:04:31 Woogie kernel: [ 1676.289757] Buffer I/O error on device sda3, logical block 96221054 Nov 6 17:04:31 Woogie kernel: [ 1676.289758] Buffer I/O error on device sda3, logical block 96221055 Nov 6 17:04:31 Woogie kernel: [ 1676.289759] EXT4-fs warning (device sda3): ext4_end_bio:250: I/O error writing to inode 15731887 (offset 342884352 size 524288 starting block 129425402) Nov 6 17:04:31 Woogie kernel: [ 1676.289762] sd 0:0:0:0: [sda] Nov 6 17:04:31 Woogie kernel: [ 1676.289763] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 6 17:04:31 Woogie kernel: [ 1676.289764] sd 0:0:0:0: [sda] Nov 6 17:04:31 Woogie kernel: [ 1676.289765] Sense Key : Aborted Command [current] [descriptor] Nov 6 17:04:31 Woogie kernel: [ 1676.289766] Descriptor sense data with sense descriptors (in hex): Nov 6 17:04:31 Woogie kernel: [ 1676.289767] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 6 17:04:31 Woogie kernel: [ 1676.289771] 3d b7 05 d7 Nov 6 17:04:31 Woogie kernel: [ 1676.289773] sd 0:0:0:0: [sda] Nov 6 17:04:31 Woogie kernel: [ 1676.289773] Add. Sense: No additional sense information Nov 6 17:04:31 Woogie kernel: [ 1676.289775] sd 0:0:0:0: [sda] CDB: Nov 6 17:04:31 Woogie kernel: [ 1676.289775] Write(10): 2a 00 3d b7 05 d7 00 00 20 00 Nov 6 17:04:31 Woogie kernel: [ 1676.289779] end_request: I/O error, dev sda, sector 1035404759 Nov 6 17:04:31 Woogie kernel: [ 1676.289789] ata1: EH complete Nov 6 17:04:31 Woogie kernel: [ 1676.289832] EXT4-fs (sda3): delayed block allocation failed for inode 15731887 at logical offset 84032 with max blocks 4 with error -5 Nov 6 17:04:31 Woogie kernel: [ 1676.289842] EXT4-fs (sda3): This should not happen!! Data will be lost So back to kernel 3.4.0 I go (no errors in my syslog for that). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I tried 3.5-rc5 and got the problem fairly quickly. Went back to 3.5-rc4 and noticed I was getting ext4 buffer write sda errors in syslog for that as well... so it might be that 3.5-rc4 doesn't actually work for me either, although I haven't had rc4 go into read-only mode at all yet. Since yesterday I've gone to using 3.4. Haven't had any sda errors at all in syslog anymore. I should have been paying attention to my syslog previously already instead of just waiting for the fs to go read-only. Unfortunately, I can't be testing any more of these kernels as I'm slowly getting more and more files getting corrupted.. and this is my home office work computer so I can't allow that. Will stay on 3.4 now. Maybe someone else can test 3.5-rc1 thru 3.5-rc3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063354] Re: Sudden Read-Only Filesystems
I just recently found out about the problems with ext4 corruption (as mentioned in http://lwn.net/Articles/521022/ ) and am now wondering if this is all related to that? Except that that bug is only supposed to happen in rare cases, nothing like what I've been seeing. Also don't understand why more people aren't having this issue... is it possible that it is just a failing HD for me as well? I will stay on 3.4 for now and report back here if I see anything suspicious in my syslog at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
