similar to: Reg:Checking HDD Badblocks on kickstart CentOS installation

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

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

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

Dear All, Currently i am using HP x6600 Server and I have installed RHEL4 Update 4 AS Linux and RHEL4 Update 4 Support Cluster Suite in my server I am new in fence and can any one help me how to configure HP ILO fence in my server and HP ILO Fence Functionality Regards -S.Balaji

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

Dear All, Currently using RHEL6 Linux and Kernel Version is 2.6.32-71.el6.i686 and DRBD Version is 8.3.10 DRBD is build from source and Configured DRBD with 2 Node testing with Simplex Setup Server 1 : 192.168.13.131 IP Address and hostname is primary Server 2 : 192.168.13.132 IP Address and hostname is secondary Finally found that drbd0, drbd1 mount failed problem *Found some error messages

Dear All, I am using CentOS4 Update 3 Cluster Suite for i386 Architecture and my linux kernel version is 2.6.9-34.EL I have configured two node cluster My nodes are primary and secondary and I am using cluster to monitoring scripts During reboot or poweroff i am getting the problem is cman stop failed and I have verified the "/var/log/messages" log file and i getting the

Hi, I've been using an CentOS4.4 version. All was well till 2 days back. Suddenly when the PC was booted-up, it wouldn't bootup. It gets stuck displaying the following message. exec of init (/sbin/init) failed !!!: 80 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! I entered the rescue mode and attempted chroot /mnt/sysimage It spitted an error

Sir, Recently i have buy a HCL ME Laptop with inbuilt webcam support. I have installed the CentOS 6 and its not detected the Bisoncam NB Pro webcam. Is there any driver is required, if its required please send me the driver download link and installation steps. Regards -S.Balaji

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"

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

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

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

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

Chris Murphy wrote: > 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> >> > >> SCT Error Recovery Control command not supported >> > The drive is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/01/16 12:34, J Martin Rushton wrote: > Not new: I can remember seeing DEC engineers cleaning up the > contacts on memory boards for a VAX 11/782 with a pencil eraser > c.1985. It's still a pretty standard first fix to reseat a card or > connector. I used to do that as well. The contacts would come out nice and shiny when you