similar to: Ext3 File Corruption issue

Hi Guys, My first post here. I have recently installed RH9 and am having some rather wierd problems that make me suspect file corruption. After some useage the machine locked up hard when trying to use 3d graphics (I have a radeon 7200 with dri enabled). After this happened occasionally the system refuses to boot- it stops at the apm line of the kernel boot process. I tried looking at my hard

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Please CC me on answers, I'm not subscribed] Hi everyone, I have got a hard disk which was damaged by a fall and would like to recover a few files from that. (There is a backup for most of the data, but a handful of recent files are missing. These are important enough to spend some time on them, but not for paying a professional data recovery

On Tue, 31 Jan 2023 at 09:09, Chris Clayton <chris2553 at googlemail.com> wrote: > > Hi again. > > On 30/01/2023 20:19, Chris Clayton wrote: > > Thanks, Ben. > > <snip> > > >> Hey, > >> > >> This is a complete shot-in-the-dark, as I don't see this behaviour on > >> *any* of my boards. Could you try the attached patch

Have you ran a "long" smart test on the drive? Smartctl -t long device I'm not sure what's going on with your drive. But if it were mine, I'd want to replace it. If there are issues, that long smart check ought to turn up something, and in my experience, that's enough for a manufacturer to do a warranty replacement. On Jan 17, 2016 11:00, "Alessandro Baggi"

Dear All, In Redhat 7.2 kick start installation,badblocks check for HDD is working on creating partition. But in Centos badblocks check is not working in kick start installation. Badblocks check command in kickstart file part / --fstype ext3 --badblocks --size 1000 part /home --fstype ext3 --badblocks --size 12000 part /usr --fstype ext3 --badblocks --size 9000 part swap

On Jan 17, 2016, at 9:59 AM, Alessandro Baggi <alessandro.baggi at gmail.com> wrote: > > On sdb there are not problem but with sda: > > 1) First run badblocks reports 28 badblocks on disk > 2) Second run badblocks reports 32 badblocks > 3) Third reports 102 badblocks > 4) Last run reports 92 badblocks. It?s dying. Replace it now. On a modern hard disk, you should

Hi I work on this harddrive for 3 days now ... I had noticed errors in kernel while working on a harddrive (120 gigas) but all continue to work fine (archives/directory).. So i have unmounted the driver and try e2fsck... bad ! e2fsck 1.34 (25-Jul-2003) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/hdc1 So i have tried to create 1 image of this

Dear All, In Redhat 7.2 kick start installation,badblocks check for HDD is working on creating partition. But in Centos badblocks check is not working in kick start installation. Badblocks check command in kickstart file part / --fstype ext3 --badblocks --size 1000 part /home --fstype ext3 --badblocks --size 12000 part /usr --fstype ext3 --badblocks --size 9000 part swap

Hi list, I've a notebook with C7 (1511). This notebook has 2 disk (640 GB) and I've configured them with MD at level 1. Some days ago I've noticed some critical slowdown while opening applications. First of all I've disabled acpi on disks. I've checked disk for badblocks 4 consecutive times for disk sda and sdb and I've noticed a strange behaviour. On sdb there are

On 01/20/2016 01:43 PM, Chris Murphy wrote: > On Wed, Jan 20, 2016, 7:17 AM Lamar Owen <lowen at pari.edu> wrote: > >> The standard Unix way of refreshing the disk contents is with >> badblocks' non-destructive read-write test (badblocks -n or as the >> -cc option to e2fsck, for ext2/3/4 filesystems). > > This isn't applicable to RAID, which is what

Il 17/01/2016 18:46, Brandon Vincent ha scritto: > On Sun, Jan 17, 2016 at 10:05 AM, Matt Garman <matthew.garman at gmail.com> wrote: >> I'm not sure what's going on with your drive. But if it were mine, I'd want >> to replace it. If there are issues, that long smart check ought to turn up >> something, and in my experience, that's enough for a

I decided, after the last discussion of smartd and S.M.A.R.T. disks, to take a look in my /var/log/messages, and I'm seeing fair bit of this: Sep 10 20:11:23 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Offline uncorrectable sectors Sep 10 20:41:23 mhrichter smartd[3361]: Device: /dev/hdb, 21 Currently unreadable (pending) sectors Sep 10 20:41:24 mhrichter smartd[3361]: Device:

On Sun, 19 Feb 2023 at 04:55, Chris Clayton <chris2553 at googlemail.com> wrote: > > > > On 18/02/2023 15:19, Chris Clayton wrote: > > > > > > On 18/02/2023 12:25, Karol Herbst wrote: > >> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton <chris2553 at googlemail.com> wrote: > >>> > >>> > >>> > >>> On

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

On 01/19/2016 06:46 PM, Chris Murphy wrote: > Hence, bad sectors accumulate. And the consequence of this often > doesn't get figured out until a user looks at kernel messages and sees > a bunch of hard link resets.... The standard Unix way of refreshing the disk contents is with badblocks' non-destructive read-write test (badblocks -n or as the -cc option to e2fsck, for

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

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! We have a server still running Debian 3.0 (Woody) that nobody likes to touch for maintenance ... ;) Our home-directories are located on a separate HDD (30GB, 1 large primary ext3 partition) and until yesterday it worked correctly. Because the partition was nearly full we had to enlarge our home-space by moving it to a larger HDD. We decided to try a copy of whole partition by using

Hello, In case anyone is interested, here are the source code for comboot and com32 modules for powering down a computer using APM. I started work on the ACPI version of it, but it will take some time to parse the spec. Regards, Luciano Rocha -- lfr 0/0 -------------- next part -------------- ; **************************************************************************** ; ; apmoff.asm ; ; A

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 harte-lyne.ca> wrote: >>> >>> On Thu, March 9, 2017 09:46, John Hodrien wrote: >>>> >>>> fsck's not good at finding disk