similar to: Ext3 File corruption question.

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

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

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 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

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

Hi, I run hundreds of Redhat 8.0 boxes and Fedora Core 1 boxes, both Operation systems boxes give me some trouble reporting disk errors like the following (collected from /var/log/messages of each linux boxes by my own script). And a "badblocks" command on some of the related hard drive reports that failed sectors found, while others reports no, false-positive. Any one can give me

Il 17/01/2016 19:36, Alessandro Baggi ha scritto: > 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

I'm getting these messages during boot: error: failure reading sector 0xfc from 'hd4' error: failure reading sector 0xe0 from 'hd4' error: failure reading sector 0x0 from 'hd4' error: failure reading sector 0xfc from 'hd5' error: failure reading sector 0xe0 from 'hd5' error: failure reading sector 0x0 from 'hd5' they pop up soon after the Grub

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 manufacturer to do a > warranty replacement. I agree with Matt. Go

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

This is a A8N32-SLI Deluxe motherboard with a AMD Athlon(tm) 64 X2 Dual Core 4400+ Processor. It freezes and cannot be accessed from the network. Keyboard/mouse/display, everything just stuck. It had an uptime of 17 days after I re-connected all cables and boards after a similar crash. My feeling is, this must be a hardware related problem. I inspected the logs under /var/log, but nothing.

Hello, Having a problem with software RAID that is driving me crazy. Here's the details: 1. CentOS 6.2 x86_64 install from the minimal iso (via pxeboot). 2. Reasonably good PC hardware (i.e. not budget, but not server grade either) with a pair of 1TB Western Digital SATA3 Drives. 3. Drives are plugged into the SATA3 ports on the mainboard (both drives and cables say they can do 6Gb/s). 4.

Hi All, Is there a way to check the harddisk health before CentOS installation.? One way I used to do was by using --badblocks check in ks.cfg file while using RH 7.2. This is not working (atleast not with the same syntax as in RH 7.2) in CentOS. Is there an alternate (correct) syntax or is there a new (better) way to check harddisk health before CentOS installation? Please help me

Hi All, Is there a way to check the harddisk health before CentOS installation.? One way I used to do was by using --badblocks check in ks.cfg file while using RH 7.2. This is not working (atleast not with the same syntax as in RH 7.2) in CentOS. Is there an alternate (correct) syntax or is there a new (better) way to check harddisk health before CentOS installation? --Regards