similar to: Error reading block x (Attempt to read block...)

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

Hello, sorry if the question was asked a couple of times before but I couldn't find any useful hinds to this problem using google and the listman search-engine of the archive of this list. Somehow the ext3 filesystem on one of my machines died an after a reboot grub wouldn't come up again. What I did so far: fsck -y /dev/hda4 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004)

I found, under a 64-bit CentOS 5 workstation install, it is possible to modify /etc/inittab and add a couple of lines to prevent root from logging into the console. I found, under a 64-bit RHEL 5 server install, adding the same two lines completely breaks the OS, to the point that a reboot after the lines are added, the OS brings you to a fsck-like prompt, and other things break, too. I

Hi there, I am newbie and recently started using btrfs. Now facing a weird problem. FWIW, I am on archlinux, kenel v3.8.0, having Btrfs v0.20-rc1. After an abnormal reboot, getting these errors while boot: systemd.fsck[289]: checking extents systemd.fsck[289]: checking fs roots systemd.fsck[289]: checking root refs systemd.fsck[289]: found 23728128 bytes used err is 0 systemd.fsck[289]: total

Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ====================================================================

hi, I am working on a file system related project. I want to know whether the fsck utility for ext3 reads data blocks (storing user files,etc) at any stage? thankin you, amol __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hello, tl;dr: it seems like fsck fails to notice when the block device disappears from under it. I have the following setup: * external USB disk * a partition with LUKS in it * ext4 filesystem inside the LUKS block device While doing backups to it I noticed that after some time backups would fail with an error (failed to write, ). In the following log I'm attaching the disk, enabling LUKS

When I use SATA disks heavily on a 5.3-R machine (Athlon) with the SiI3512 disk controller, I get frequent (sometimes one every 1-5 minutes) WRITE_DMA timed out messages (with different blocks and both disks). It also panics with more than one kind of panic, and sometimes doesn't even get to finish the background fsck from the previous panic before dying again. Given that both disks get the

Hi, I'm running kernel 2.6.8-15, lvm2 v2.01.04-5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel:

Hello LINUX GURUS, I am fairly new to LINUX OS, so pardon my ignorance about LINUX OS. I have installed LINUX 7.2 on IBM netfinity 4000R server. OS works fine for few days and start giving me this error message all of a sudden: "kernel: hda: dma_intr: status=0x51 { Driveready SeekComplete Error }" "kernel: hda: dma_intr: status=0x40 { UncorrectableError }, LBAsect=4944861,

My UPS failed and my server took an 'unscheduled outage' a few weeks ago. The only casualty appears to be a volume I used for backup. I usually maintain data on multiple hard disks, but in this case I errantly had some data (of marginal value) on this file system. At this point, the data is not worth enough for me to send the drive out for data recovery, but it's worth enough to

hi All, A fault on our SAN dropped us down to a read-only filesystem and after reboot, we have an "Unexpected Inconsistency" and I am being instructed by the boot to run fsck manually without -a or -p (this was after I think processing around 15% of the filesystem) The specific message is "inode 27344909 has illegal blocks" I recall running fsck some years ago on smaller

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

I want to keep track of how long a task is running. Thinking it wouldn't take that long, I opted not to run time before it. The fact that it is taking a long time, if I revisit the machine in the morning, what would be the best way to find out what time it ended? In this case, I'm using mt to erase an lto3 tape - sudo mt -f /dev/st0 erase. But I'd like to use the knowledge from

Hi, Can anyone point me on howto use fsck to marking the bad block so it won't be use to store a file? I have one hdd with the bad block running on one of my server with this problem. While I rebuild a new server to replace the hdd, I really like to have a temporary solutions for that. Thanks in advances, regards, ijez -- No virus found in this outgoing message. Checked by AVG Free

I have a Fedora Core 3 system at home, that was running fine, but now won't boot. Someone shut the power off on it without doing an orderly shutdown, and also I sometimes apply patches with "yum -y update" without doing a reboot immediately afterward - I suppose either of these could be related to my system not booting. I have a lot of information about the early stages of the

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Thanks for a great file system! I have a two-node cluster working as a HA NFS server. This system has worked fine for almost a year, but recently I found that an ocfs2 file system had been corrupted and needed to be repaired with fsck.ocfs2. Even though I don't think that any data was lost I found that 4 of my 14 ocfs2 partitions had some errors which were corrected by fsck.ocfs2. I then

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message: