Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory MDADM Failure - where it came from? Post 302926584 by Sunghost on Tuesday 25th of November 2014 10:12:52 AM
Old 11-25-2014
Hi,
i got this everytime i want to add a disk to the array. Meanwhile i think its a problem with the marvel chipset on the sata controller and perhaps smart. this seems to crash the disks if they under heavy load.
 

10 More Discussions You Might Find Interesting

1. Programming

ld failure

Hi, I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies

2. Linux

mdadm - Swapping 500GB disks for 1TB

Hi, I have a three disk raid 5, with 500GB disks. This is close to being full, and whilst I can just add another disk and rebuild to add another 500GB, I would prefer to replace with 1TB disks. So i have some questions. Can I replace these disks one by one with bigger disks? I... (1 Reply)
Discussion started by: snoop2048
1 Replies

3. Virtualization and Cloud Computing

is mdadm --incremental --rebuild --run --scan destructive?

Hello Unix Community: My task to figure out how to add a 20G volume to an existing EBS Array (RAID0) at AWS. I haven't been told that growing the existing volumes isn't an option, or adding another larger volume to the existing array is the way to go. The client's existing data-store is... (0 Replies)
Discussion started by: Habitual
0 Replies

4. Emergency UNIX and Linux Support

mdadm unable to fail a resyncing drive?

Hi All I have a RAID 5 array consisting of 4 drives that had a partial drive failure in one of the drives. Rebooting shows the faulty drive as background rebuilding and mdadm /dev/ARRAYID shows three drives as in sync with the fourth drive as spare rebuilding. However the array won't come... (9 Replies)
Discussion started by: Bashingaway
9 Replies

5. UNIX for Advanced & Expert Users

mdadm question

Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result? cat /proc/mdstat Personalities : md126 : inactive sdb sdc sdd sde 1953536528 blocks super external:-md127/0 md127 : inactive sdd(S) sde(S) sdb(S) sdc(S) 9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies

6. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies

7. Red Hat

mdadm for / and /boot

had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running.. created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda trying to use mdadm to create RAID1 .. I cannot even do it in "rescue" mode, I wonder if it can be done.. it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies

8. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

9. UNIX for Advanced & Expert Users

USB RAID 5 Problem on Joli OS 1.2 (Ubuntu) using mdadm

Hi All, I have been trying to create a USB RAID 5 using mdadm tool on Joli OS 1.2 (Ubuntu) but with no luck. I cannot even get pass the creation of array device (/dev/md0) and superblock. I am using 3 USB keys (2 16.4 GB kingston and 1 16GB sandisk). My steps are: ... (5 Replies)
Discussion started by: powelltallen
5 Replies

10. UNIX for Advanced & Expert Users

How to fix mistake on raid: mdadm create instead of assemble?

Hi guys, I'm new to RAID although I've had a server running raid5 for a while. It was delivered preinstalled like this and I never really wondered how to monitor and maintain it. This quick introduction just to let you understand why I'm such an idiot asking such a silly question. Now what... (0 Replies)
Discussion started by: chebarbudo
0 Replies
sata(7D)							      Devices								  sata(7D)

NAME
sata - Solaris SATA framework DESCRIPTION
Serial ATA is an interconnect technology designed to replace parallel ATA technology. It is used to connect hard drives, optical drives, removable magnetic media devices and other peripherals to the host system. For complete information on Serial ATA technology, visit the Serial ATA web site at http://www.serialata.org. Up to 32 SATA devices may be plugged directly to each SATA HBA supported by the Solaris SATA framework. The actual number of pluggable devices my be lower, and is limited by a number of device ports on the SATA HBA. The maximum data rate is either 1.5Gb/sec. or 3.0Gb/sec., depending on the capability of a SATA device and SATA HBA controller. The Solaris SATA framework adheres to the Serial ATA 1.0a specification and supports SATA-2 signaling speed 3.0Gb/sec. SATA devices that are connected to SATA HBAs controlled by a SATA framework-compliant HBA driver are treated by the system as SCSI devices. The Solaris SCSI disk driver (sd(7D)) is attached as a target driver for each device node created by the SATA framework. You can use the cfgadm(1M) utility to manage hot plugged and unplugged SATA devices. FILES
/kernel/misc/sata 32-bit ELF kernel module (x86). /kernel/misc/amd64/sata 64-bit ELF kernel module (x86). ATTRIBUTES
See attributes(5) for descriptions of the following attribute: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWckr | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), prtconf(1M), cfgadm_sata(1M), attributes(5), ahci(7D), marvell88sx(7D), nv_sata(7D), sd(7D), si3124(7D) Serial ATA 1.0a Specification -- Serial ATA International Organization. Serial ATA II (Extension to Serial ATA 1.0.a.) -- Serial ATA International Organization. http://www.sun.com/io DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are presented in one of the following formats and are followed by the diagnostic message: sata: WARNING: <controller/devices/.. path>: or: sata: NOTICE: <controller/devices/.. path>: ...where <controller/devices/.. path> identifies a specific SATA HBA issuing a diagnostic message shown below. SATA port X: link lost. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost. SATA port X: link established. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been established. SATA port X: device reset. The device plugged to the specified SATA device port has been reset. The reset may be due to a communication or command error, command timeout, or an explicit request from the host. SATA port X failed. The specified SATA device port failed and is in an unusable state. You can change the port state by deactivating the port and activat- ing it again using cfgadm SATA hardware-specific commands (see cfgadm_sata(1M)). SATA port X error. An error was detected in specified SATA device port operations. SATA device detached at port X. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost and could not be re-established. The SATA framework assumes that the device is unplugged from the specified SATA device port. SATA device detected at port X. Communication( via serial link) between the HBA and the device plugged to the specified empty SATA device port has been established. The SATA framework assumes that the new device is plugged to the specified SATA device port. SATA disk device at port X. This message is followed by a disk description specifying the disk vendor, serial number, firmware revision number and the disk capa- bilities. SATA CD/DVD (ATAPI) device at port X. This message is followed by a SATA CD/DVD description specifying the DVD vendor, serial number, firmware revision number and the DVD capabilities. SATA device at port X cannot be configured. Application(s) accessing previously attached device have to release it before newly inserted device can be made accessible. The port cannot be configured because there is application using the previous attached device, so the application must release it, then the newly inserted device can be configured. Application(s) accessing previously attached SATA device have to release it before newly inserted device can be made accessible. The target node remained and it belongs to a previously attached device. This happens when the file was open or the node was waiting for resources at the time the associated device was removed. Instruct event daemon to retry the cleanup later. sata: error recovery request for non-attached device at cport X. When error recovery is requested, the device is not yet attached. SATA device at port X will not be power-managed. When property "pm-capable" on the target device node setting fails, the SATA device won't be power-managed. SATA disk device at port X does not support LBA. The disk device plugged into specified SATA device port does not support LBA addressing and cannot be used. Cannot identify SATA device at port X - device will not be attached. IDENTIFY (PACKET) DEVICE data cannot be retrieved successfully after the device is attached to the SATA port. sata: <HBA driver name><instance number>:hba attached failed. The SATA HBA instance attach operation failed. This HBA instance cannot be configured and is not available. sata: invalid ATAPI cdb length<command cdb length>. The length of the command cdb is greater than that the device can support. sata: invalid sata_hba_tran version X for driver <HBA driver name>. The specified SATA HBA driver and the SATA framework are incompatible. The driver cannot attach and SATA HBAs controlled by this driver (and devices plugged to this SATA HBA ports) are not available. sata_hba_attach: cannot create SATA attachment point for port X. The specified SATA device port cannot be configured in the system and a device plugged to this port could not be not be configured and used. sata_create_target_node: cannot create target node for device at port X. The device target node for the device plugged to the specified SATA device port could not be created. As a result, the device cannot be configured and used. SunOS 5.11 5 Sep 2007 sata(7D)
All times are GMT -4. The time now is 08:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy