The file systems on several of our guest OSs running RHEL4 have suddenly started becoming read-only. ESX is 3.0.0. The two file systems that are usually / and /var. Both systems are HP DL385 with Qlogic 2430 cards. Any ideas what might be causing this?
The VMware solutions is to use BusLogic instead to LSI, and fewer months ago VMware send us a patched drivers.
To be safer, now we are migrating Linux VM to the BusLogic and installing new one with BusLogic instead of LSI.
Giovanni Coa
Not a very good "solution" for RHEL users since Redhat hasn't shipped the Buslogic driver since RHEL3 since it's mostly unsupported and hasn't had vendor support in years. Still, recent versions of RHEL (RHEL4.5 and newer, and RHEL5.1) include fixes in the LSI Logic driver (mptscsih) for this issue so it shouldn't be a problem any longer. If you need to run older update versions due to internal certification requirements then VMware has patched drivers available and the patches on my site still work fine for pretty much any distro, including those not officially supported like Fedora or Ubuntu.
Later,
Tom
We've had this problem occur on the current RHEL 5.3 with kernel 2.6.18-128.el5. Updating SAN firmware didn't help.
Today I compiled the latest stable kernel (2.6.28.3) from kernel.org
Still having errors as below:
Feb 4 16:47:36 rsync kernel: sd 0:0:3:0: timing out command, waited 360s~ Feb 4 16:47:36 rsync kernel: sd 0:0:3:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK Feb 4 16:47:36 rsync kernel: end_request: I/O error, dev sdd, sector 589741855 Feb 4 16:47:36 rsync kernel: Buffer I/O error on device sdd1, logical block 73717724 Feb 4 16:47:36 rsync kernel: lost page write due to I/O error on sdd1 ~
Hello,
Moved to Virtual Machine and Guest OS forum.
This is actually a bug in the GUest OS. There have been several reported patches for LSILogic SCSI drivers.
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast
According to the vmware kb an upgrade to 5.1 should be enough but I still have the same problem with a RHEL5.2 (kernel 2.6.18-92)
Please refer the artcile which talks about detailed setps to investigate about this issue.
http://www.vmwarearena.com/2013/04/redhat-linux-virtual-machine-file.html
Here is another article pleas have a look..
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=51306
If you read the below post, I have linked lot of articles which talks about the same issue
http://www.vmwarearena.com/2013/04/redhat-linux-virtual-machine-file.html