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 Kernel
Packages, 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 Kernel
Packages, which is subscribed to linux
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
13 matches
Mail list logo
