similar to: Errors on an SSD drive

To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4 if you manage to get the drive working again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com

On 08/09/2017 01:48 PM, hw wrote: > Robert Moskowitz wrote: >> I am building a new system using an Kingston 240GB SSD drive I pulled >> from my notebook (when I had to upgrade to a 500GB SSD drive). >> Centos install went fine and ran for a couple days then got errors on >> the console. Here is an example: >> >> [168176.995064] sd 0:0:0:0: [sda] tag#14

what file system are you using?? ssd drives have different characteristics that need to be accomadated (including a relatively slow write process which is obvious as soon as the buffer is full), and never, never put a swap partition on it, the high activity will wear it out rather quickly.? might also check cables, often a problem particularly if they are older sata cables being run at a possibly

If it's a bad sector problem, you'd write to sector 17066160 and see if the drive complies or spits back a write error. It looks like a bad sector in that the same LBA is reported each time but I've only ever seen this with both a read error and a UNC error. So I'm not sure it's a bad sector. What is DID_BAD_TARGET? And what do you get for smartctl -x <dev> Chris

Robert Moskowitz wrote: > I am building a new system using an Kingston 240GB SSD drive I pulled from my notebook (when I had to upgrade to a 500GB SSD drive). Centos install went fine and ran for a couple days then got errors on the console. Here is an example: > > [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > [168177.004050]

I have yet to see a SSD read\write error which wasn't related to disk issues like a bad sector but the controller might have an issue with the drive. To verify it you will need to burn some read\write IOPS of the drive but if it's under warranty then it's better to verify it now then later. Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email:

On 08/09/2017 10:46 AM, Chris Murphy wrote: > If it's a bad sector problem, you'd write to sector 17066160 and see if the > drive complies or spits back a write error. It looks like a bad sector in > that the same LBA is reported each time but I've only ever seen this with > both a read error and a UNC error. So I'm not sure it's a bad sector. > > What is

On 08/09/2017 10:44 PM, mad.scientist.at.large at tutanota.com wrote: > what file system are you using? ssd drives have different characteristics that need to be accomadated (including a relatively slow write process which is obvious as soon as the buffer is full), and never, never put a swap partition on it, the high activity will wear it out rather quickly. might also check cables, often a

On Wed, Aug 9, 2017, 11:55 AM Mark Haney <mark.haney at neonova.net> wrote: > To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a > couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4 if you manage to get the drive working again. > Sounds like a hardware problem. Btrfs is explicitly optimized for SSD, the maintainers worked

Hello We were attempting to use scsi-target-utils, hosted on a xen dom0 vm using localhost, and running into some problems. I was not able to reproduce this on a centos 7.2 server using the default kernel. (From dmesg) Apr 4 11:18:42 funk kernel: [ 596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv

By natively, I take it using kernel /vmlinuz (vs kernel /xen) Not yet, but working on setting up such an environment. (At this time, I was using virt-install to reproduce the problem, and the original server we are testing on did not support kvm but the 2nd server does). On 2016-04-12 03:26 AM, George Dunlap wrote: > On Mon, Apr 11, 2016 at 9:14 PM, Nathan Coulson <nathan at

Ok, got a quickie. I have an eSATA drive, a 750GB Seagate in an eSATA external enclosure, and a Silicon Image sil3132 ExpressCard controller for my laptop. The disk and controller work great in CentOS 5 (or F7, for that matter), if I specifically mount it. This is not how I want to have to use this drive, however. I want to hotplug it; that is, plug the controller into the laptop, and then

I am trying to copy(~7TB of data using rsync) between two server in same data center in the backend its using EMC VMAX3 After copying ~30-40GB of data multipath start failing Dec 15 01:57:53 test.example.com multipathd: 360000970000196801239533037303434: Recovered to normal mode Dec 15 01:57:53 test.example.com multipathd: 360000970000196801239533037303434: remaining active paths: 1 Dec 15

Hi everyone, I have one OCFS2 issue. The OS is Ubuntu, using linux kernel is 3.2.50. There are three node in the OCFS2 cluster, and all the node is using the iSCSI SAN of HP 4330 as the storage. As the storage restarted, there were two node restarted for fence without heartbeating writting on to the storage. But the last one does not restart, and it still write error message into syslog as below:

I had a busy mailserver fail on me the other day. Below is what was printed in dmesg. We first suspected a hardware failure (raid controller or something else), so we moved the drives to another (identical hardware) machine and ran fsck. Fsck complained ("short read while reading inode") and asked if I wanted to ignore and rewrite (which I did). After booting up again, the problem came

Hello! I''ve a ubuntu server running over a HVM DomU. After a hang, the domU doesn''t start again. The domU was not able to mount the virtual machine disk so I started with a live cd and I tried to mount the disk root part / with no success so I ran fsck.ext3 and it gave me input/output error in the domU and in dom0 the kernel says: Feb 14 18:22:28 scofield last message

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hello, My server is running kernel 3.10.0-1062.12.1 in a CentOS Linux release 7.7.1908. Since some weeks ago, server is restarting after XFS errors. Logs in /var/crash reported this information: [...] [443804.295916] sd 0:0:0:0: [sda] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [443804.295919] sd 0:0:0:0: [sda] CDB: Read(10) 28 00 04 53 e8 b0 00 00 28 00 [443804.295922]

Hi, Doing some extensive benchmarks on BTRFS, I encountered a kernel bug in BTRFS (as reported in dmesg) Maybe the information below can help you making btrfs better. Situation Doing an intensive sequential write on a SAS 3TB disk drive (SEAGATE ST33000652SS) with 128 threads with Sysbench. Device is connected through an HBA. Blocksize was 256k ; Kernel is 3.3.0 (x86_64) ; Btrfs is version

I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of my Ubuntu machines without success. It keeps giving errors like this: [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 frozen [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED [ 9.115556] ata9.00: cmd 60/04:00: d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in [ 9.115557]