search for: badblock

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

...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 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) L...

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

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 *never* see bad sectors, because the drive is busy hiding all the bad sectors i...

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

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 this thread is about. For > RAID, use scrub, that's what is for. The badblocks read/write verification would n...

...t; something, and in my experience, that's enough for a manufacturer to do a >> warranty replacement. > > I agree with Matt. Go ahead and run a few of the S.M.A.R.T. tests. I > can almost guarantee based off of your description of your problem > that they will fail. > > badblocks(8) is a very antiquated tool. Almost every hard drive has a > few bad sectors from the factory. Very old hard drives used to have a > list of the bad sectors printed on the front of the label. When you > first created a filesystem you had to enter all of the bad sectors > from the labe...

...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 unmount relevant filesystem(s) before using badblocks... > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > ++++++++++++++++++++++++++++++++++++++++ Va...

...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 ahead and run a few of the S.M.A.R.T. tests. I can almost guarantee based off of your description of your problem that they will fail. badblocks(8) is a very antiquated tool. Almost every hard drive has a few bad sectors from the factory. Very old hard drives used to have a list of the bad sectors printed on the front of the label. When you first created a filesystem you had to enter all of the bad sectors from the label so that the filesy...

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 ext2/3/4 filesystems). The remap will happen on the writeback of the contents. It's been this way with enterprise SCSI drives for as long as I can remember there being enterprise-class SCSI drives. A...

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 and it is very urgent requirem...

...-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 unmount relevant filesystem(s) before using >> badblocks??? > > You don???t necessarily have to. The default mode of badblocks is a non-invasive read-only test > which is safe to run on a mounted filesystem. > > That said, a read-on...

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 S.Balaji

...'s enough for a manufacturer to >>> do a >>> warranty replacement. >> >> I agree with Matt. Go ahead and run a few of the S.M.A.R.T. tests. I >> can almost guarantee based off of your description of your problem >> that they will fail. >> >> badblocks(8) is a very antiquated tool. Almost every hard drive has a >> few bad sectors from the factory. Very old hard drives used to have a >> list of the bad sectors printed on the front of the label. When you >> first created a filesystem you had to enter all of the bad sectors >&g...

Hi All, I'm currently running an embedded linux system (arm) with a CF card mounted as EXT3. I'll copy some system details below... Anyway, I'm getting some drive errors and I'm wondering if they're due to bad/old drivers, something with EXT3 and CF latency, or something else entirely. These are the errors: hda: write_intr error1: nr_sectors=1, stat=0x51 hda:

...rub menu with a message to press ENTER to continue, and it times out in a few seconds if I don't press ENTER. These messages have been appearing for a long time, at least a couple of years and I've been too lethargic to investigate til now. I see no bad side-effects at runtime. I just did badblocks (read-only) on both sda and sdb (RAID-1 pair) which found no errors. I see nothing obviously related in dmesg, or /var/log/messages. I also have an external box (Venus DS3R Pro-2) with two drives, also RAID-1, that I use for backups. It is seen (after boot) as /dev/sdc. I'd have to pull the...

On 1/19/2016 2:24 PM, Warren Young wrote: > It?s dying. Replace it now. agreed > On a modern hard disk, you should*never* see bad sectors, because the drive is busy hiding all the bad sectors it does find, then telling you everything is fine. thats not actually true. the drive will report 'bad sector' if you try and read data that the drive simply can't read. you

What is the result for each drive? smartctl -l scterc <dev> Chris Murphy

That's strange, I expected the SMART test to show some issues. Personally, I'm still not confident in that drive. Can you check cabling? Another possibility is that there is a cable that has vibrated into a marginal state. Probably a long shot, but if it's easy to get physical access to the machine, and you can afford the downtime to shut it down, open up the chassis and re-seat the

On Mon, Jan 18, 2016, 4:39 AM Alessandro Baggi <alessandro.baggi at gmail.com> wrote: > Il 18/01/2016 12:09, Chris Murphy ha scritto: > > What is the result for each drive? > > > > smartctl -l scterc <dev> > > > > > > Chris Murphy > > _______________________________________________ > > CentOS mailing list > > CentOS at