similar to: smartctl of usb backup drive

Hi all, I used a kickstart script to setup a new machine of mine with RAID 1 (I couldn't get anaconda to create matching partition schemes). So I've now got /dev/sdg1 and /dev/sdh1 as 'bios_grub' (/dev/sd{a-f} are a separate array). 0 root at an-nas02:~# parted /dev/sdg print free Model: ATA ST3000NC000 (scsi) Disk /dev/sdg: 3001GB Sector size (logical/physical):

Il 21/10/2016 17:20, m.roth at 5-cent.us ha scritto: > John R Pierce wrote: >> On 10/21/2016 2:03 AM, Alessandro Baggi wrote: >>> >>> My ssds are failing? >> >> SSD's wear out based on writes per block. they distribute those >> writes, but once each block has been written X number of times, they are >> no longer reliable. >> >>

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

On 23/08/15 17:10, Robert Moskowitz wrote: > After years of delays and side trips, I really am going to dive in and > build my own Samba server. And I have a few questions. > > All of my servers will be ARM. The main hardware will be Cubieboards > (2 and truck). They will be running Centos-7 once the development is > finished. For now I am using Fedora 22 arm. My backup

Hello, after update to 5.1 the smartctl will fail. I get this output: smartctl --all -d ata /dev/sda smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: HDS728080PLA380 Serial Number: XXXXXXXXXXXXXXXX Firmware Version: PF2OA69A User Capacity: 82.348.277.760

We have a system - it's C 7 - that a while back lost three drives of a large array. The other admin here replaced the failed drives, but never went through the MegaRAID replace series of commands. I've just brought it back up and put a new filesystem on it, but here's what's odd: if I do smartctl -a -d megaraid,x /dev/sda, where x=drive number, for all the other drives, I get

Hey, guys See further below extracted output from a daily scrub showing csum errors on sdb, part of a raid1 btrfs. Looking back, it has been getting errors like this for a few days now. The disk is patently unreliable but smartctl's output implies there are no issues. Is this somehow standard faire for S.M.A.R.T. output? Here are (I think) the important bits of the smartctl output for

I've got a 1Tb USB disc that appears to be dying - eg it took about 10 days (!) to run 'badblocks -nsv /dev/sdc' and it only did less than 2% in that time. Read access became _really_ slow. So there's definitely something amiss and I've got it offline. There's no drama about the content as I have other backups and I'm resigned to junking the thing, but I'm curious

I've seen similar cases where a USB drive appears to fail but the SMART reports success. The most recent was a 500 GB disk which had internally a Seagate Barracuda SATA drive. It appeared to work well until I sent it a largish (7GB) tarball. As well as SMART I ran a surface check and exercise, all passed. The tar kept failing. I can't test further, the disk has been broken up for

A few weeks ago, one of my servers started complaining, via smartd, that one drive had one unreadable sector. I umounted it, and ran an fsck -c, then remounted it. Error didn't go away. Now, what's really annoying is that I've gotten back to it today, and it's reporting the problem, as it has for weeks now, every half an hour. However, when I run > smartctl -q errorsonly -H -l

After years of delays and side trips, I really am going to dive in and build my own Samba server. And I have a few questions. All of my servers will be ARM. The main hardware will be Cubieboards (2 and truck). They will be running Centos-7 once the development is finished. For now I am using Fedora 22 arm. My backup file server will be a pogoplug (armv5) with Redsleeve 7.1. My current

thanks for the reply. On 08/23/2015 01:26 PM, Rowland Penny wrote: > On 23/08/15 17:10, Robert Moskowitz wrote: >> After years of delays and side trips, I really am going to dive in >> and build my own Samba server. And I have a few questions. >> >> All of my servers will be ARM. The main hardware will be Cubieboards >> (2 and truck). They will be running

I finally fixed my drive error problem. This has been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a

On 01/13/2015 12:47 PM, Gordon Messmer wrote: >> I'm having an issue getting a C6.6 install to work on a 3 TB dual hard >> drive system, raid 0. I'm hoping that someone here can help. > 1: Is this system booting UEFI or BIOS? > 2: Is the disk partitioned with MBR or GPT? > 3: Is /boot on its own partition? > > 3TB drives are larger than MBR and BIOS properly

I've just installed my first system with a SATA drive and I've noticed that smartctl isn't supported under libata According to the smartmontools home page, SATA will require a patch that is still in development. http://www.linuxjournal.com/article/6983#comment-126714 "The patch is still under development and it is probably best to make sure that the disk is idle before trying

If y'all remember the problem I posted a while back, with a 3TB drive for userspace loosing it on a server, and spitting DRDY errors, but which work on everything else. Well, enough research, and conversation, and I may have found the problem: it's a Caviar Green, meant for a desktop, and the controller in the server has issues, because it uses TLER:

Hi anyone. When I run make trying to compile Dovecot for a network attached storage box and it fails. I have used two variants of configuration: The first ./configure i_cv_epoll_works=no i_cv_inotify_works=no i_cv_posix_fallocate_works=no i_cv_signed_size_t=no i_cv_gmtime_max_time_t=32 i_cv_signed_time_t=yes i_cv_mmap_plays_with_write=yes i_cv_fd_passing=yes i_cv_c99_vsnprintf=yes

OK todays problem. I have a HP N54L Microserver running centos 6.5. In this box I have a 3x2TB disk raid 5 array, which I am in the process of extending to a 4x2TB raid 5 array. I've added the new disk --> mdadm --add /dev/md0 /dev/sdb And grown the array --> mdadm --grow /dev/md0 --raid-devices=4 Now the problem the resync speed is v slow, it refuses to rise above 5MB, in general

I am trying to build a static version of ssh, sshd and sftp, but after banging my head against the wall for the best part of the last 3 days I am about to give up... Since I plan to use this on an embedded device (building dropbear is *NOT* an option!), I've excluded as many openssh configure options as I can but, ultimately, failed. This is my setup: export LDFLAGS=' -pie -z relro -z

Hi. I'm trying to cross compile dovecot. My desktop machine is an AMD64 box with bells and whistles. The ARM based machine is a network attached storage box. When I run "make" always get x86_64 binaries. My OS is Gentoo, so I have been able to build using emerge a variety of other programs from source. What am I doing wrong here. (Gentoo doesn't have Dovecot for the arm) I