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
[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:
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 /
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
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
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
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
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
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
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
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
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.
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
'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,
'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
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
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
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
@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.
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,
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
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
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
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.
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
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
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
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
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
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:
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
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
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
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
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
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
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
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,
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
--
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
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
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
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.
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
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
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:
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
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
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
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
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
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
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:
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.
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:
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.
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,
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.
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.
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
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.
--
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
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
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
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:
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
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
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
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
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
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
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
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.
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
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
** 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:
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
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
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
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
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
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
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
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
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
1 - 100 of 126 matches
Mail list logo
