similar to: filesystem corruption?

On Mon, April 6, 2015 4:37 pm, m.roth at 5-cent.us wrote: > Got an older server here, running CentOS 6.6 (64-bit). Suddenly, at > 0-dark-30 yesterday morning, we had failures to connect. > > After several tries to reboot and get working, I tried yum update, and > that failed, complaining of an python krb5 error. With more investigation, > I discovered that logins were failing as

Hi, I have a 20GB partition on a hard disk that just developed bad blocks. Fortunately, I had backups for the most important data on it, but I'd like to recover some files that were too large to backup. When running 'e2fsck /dev/hdc3', I get the following message: e2fsck 1.27 (8-Mar-2002) Group descriptors look bad... trying backup blocks... e2fsck: Invalid argument while checking

Linux debian1 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u1 i686 GNU/Linux it is serving as file server for a few windows pcs in a satellite office. I am trying to join the machine to a AD Domain in our main office. tried[b] net join -U duper%5HaveLefT -d5[/b] debug results:[code]INFO: Current debug levels: all: 5 tdb: 5 printdrivers: 5 lanman: 5 smb: 5 rpc_parse: 5 rpc_srv: 5 rpc_cli: 5

Though quiet at the moment, my desktop sometimes sometimes makes a noise that I attribute to either a disk or a fan on its last legs. I'm looking for suggestions for distinguishing. For the disk, I expect I should use either hdparm of fsck. Even after reading the man page, I'm not sure how I would use hdparm. If I use fsck, what should I take as evidence of a bad drive? A good drive? Is

Hi list, I'm looking for advice/help in tracking down a problem with a new system I've purchased. I have a beige box server with a Gigabyte GA-M51GM-S2G motherboard. It has the nVidia MCP51 SATA controller with 3 250 gig Western Digital hard drives attached to it. It seems that when doing a considerable amount of file writing, the filesystem will become read-only. See attached dmesg

Hi, I'm using CentOS 5 on all my computers here (work + home) and I'm very satisfied with it. Some time ago I purchased a 300 GB external hard drive to store films, music, pictures and documents. Since there's no Windows machine around here (small South French village, town hall and public library use Linux :o)), I replaced the FAT filesystem on the disk by an ext2 filesystem.

On Fri, March 10, 2017 9:52 am, Warren Young wrote: > On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >> >> On Thu, March 9, 2017 09:46, John Hodrien wrote: >>> >>> fsck's not good at finding disk errors, it finds filesystem errors. >> >> If not fsck then what? > > badblocks(8). And I definitely will

Hi folks, I have come sort of corruption on my hard disk, but it is difficult to find documentation on how to deal with it. The system is an old AMD K6/400 running Redhat 7.2 with 2.4.9. Disk is clipped to 33Mb due to old disk controller, and is running ext3. Some time back I suffered a number of cases where the machine hard locked up and I had to power cycle it to get control back. However, I

On Thu, March 9, 2017 09:46, John Hodrien wrote: > On Thu, 9 Mar 2017, James B. Byrne wrote: > >> This indicated that a bad sector on the underlying disk system might >> be the source of the problem. The guests were all shutdown, a >> /forcefsck file was created on the host system, and the host system >> remotely restarted. > > fsck's not good at finding

Has anyone been seeing IO lockup problems on EL4? I've tried multiple IO scheduler options (elevator=) in the boot... I'm seeing the same behavior regardless. Independent of hardware. Whitebox ATA, HA enclosure with dedicated SCSI, megaraid RAID hardware, Dell 2850s... same behavior: A semi-busy system will suddenly go into some kind of IO la-la land where nothing can be written

Dear all, Due to the power failure, so i need to restart my redhat linux server. but i got below error messages, pls everybody can help/teach me fix the problem by return mail. ------------------------------------------------------------------------------------------------------------------------------------------------ Yours system appears to have shut down uncleanly Press Y within 1 seconds

Hi I have a Firewire connected Micronet 1.5TB RAID with a single large ext3 filesystem on one partition on a dual Xeon system. I am checking out from an extremely large cvs repository (don't ask) to this drive over the course of many days, and intermittently I get bad blocks and the filesystem goes read-only. This is not related to any power failure or anything similar. The RAID is currently

Hi Andre, ext3 folk, It would be really great if you could help me out here, I'm not sure if this is a hardware issue, a driver issue, an ext3 issue or some combination of them... I have a KT133A motherboard with an on-board promise controller, and an ACARD ATP865 in a PCI slot. I'm running 2.4.19-ac4 with the lvm 1.0.5 patches. The acard has two drives, hde and hdg attached to it, both

I get up around 0630, u can come anytime after that. I want to hit the range that morning but if I KNEW when you are arriving, I could plan around that... > On Mar 10, 2017, at 9:28 AM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: >> >> >> On Fri, March 10, 2017 9:52 am, Warren Young wrote: >>> On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at

Hi, Our virtual machines have some filesystem corruption problems. The filesystem is being mounted on read-only mode. When running fsck command, everything goes ok. Our configuration Dom0 : RHEL4 Update 3 Xen : 3.0.2.2, compiled from sources. Linux Xen kernel : 2.6.16 File-System : ext3 w/ LVM DomU : Fedora Core 4 ou 6 Xen : 3.0.2.2, compiled from sources. Linux Xen Kernel : 2.6.16

Dear all, I'm trying to find a way to automate checkdisk every 1 month on a weekend. in other words i want checkdisk to run every saturday morning. i can of course change the default mount/count though that wont let me control WHEN it will happen. so i need your expert opinion with the following if possible: 1. reboot into single user mode 2. start checkdisk for all disks 3. once done,

On 2015-06-02 11:00, samba-request at lists.samba.org wrote: > From: Rowland Penny <rowlandpenny at googlemail.com> > Precedence: list > MIME-Version: 1.0 > To: samba at lists.samba.org > References: <39f4efa684c5c13791542c12a0427582 at rh5.afts.com> > In-Reply-To: <39f4efa684c5c13791542c12a0427582 at rh5.afts.com> > Date: Tue, 02 Jun 2015 10:22:47 +0100

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

the facts: i've got an ext3 partition that system didn't correctly unmont due to a power failure while i was downloading a huge file. at the reboot the other ext3 partition (the /) got checked and fixed perfectly, but fsck was needed for the one where the file was downloading to. here's the problem: the system completely freeze during the check, approximately always at the same

Hi all, I have a bunch of mail servers running postfix (external smtp), qmail (LDA) and courier IMAP/POP. Frequently, Ext3 filesystem goes into read-only mode forcing recovery using fsck. Below are the errors we have seen so far on these systems and those systems config. The ext3 errors are common in many cases. 1. Red Hat Enterprise Linux Server release 5.2 (Tikanga) 2.6.18-92.1.10.el5