search for: sdj

I have 4 ST2000DL003-9VT166 (2Tbyte) disks in a RAID 5 array. Because of the size I built them as a GPT partitioned disk. They were originally built on a CentOS 5.x machine but more recently plugged into a CentOS 6.2 machine where they were detected just fine e.g. % parted /dev/sdj print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdj: 2000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 3 2097kB 2000GB 2000GB Linux RAID raid The MBR is empty except for the s...

...d the place in the OS where there is the information about LUN mappings to /dev/ devices. For example on array level I have an exported LUN with number 8. I see it on one of the servers with lsscsi as: # lsscsi | grep '7\:0\:0\:8' [7:0:0:8] disk SUN LCSM100_F 0735 /dev/sdj As I said I need to perform migration of the OS to Centos 5.9 x86_64 and am curious where from does the mapping scsi device 7:0:0:8 <-> /dev/sdj come? I have some complex logical volume (Veritas Volume Manager) setup based on /dev/ disks (which are derived from LUNs imported from the arr...

...t this array will pull through with most or all of my data. Background info about the machine /dev/md0 is a RAID1 consisting of /dev/sda1 and /dev/sda2 /dev/md1 is a RAID1 consisting of /dev/sda2 and /dev/sdb2 /dev/md2 (our special friend) is a RAID5 consisting of /dev/sd[c-j] /dev/sdi and /dev/sdj were the drives that detached from the array and were marked as faulty. I did the following things that in hindsight were probably VERY BAD Step 1 (Misassign drives to wrong array): I could probably have had things going again in a tenth of a second if I hadn't typed this: mdadm --manage...

...2513 6360229587 sdf? ? ? ? ? ? ? 52.20? ? ? 2031.17? ? ?10682.06 1209216701 6359354331 sdg? ? ? ? ? ? ? 52.62? ? ? 2033.22? ? ?10684.17 1210437080 6360606756 sdh? ? ? ? ? ? ? 52.57? ? ? 2031.21? ? ?10684.17 1209242746 6360606756 sde? ? ? ? ? ? ? 51.67? ? ? 2033.17? ? ?10682.06 1210408935 6359354331 sdj? ? ? ? ? ? ? 51.90? ? ? 2031.13? ? ?10684.48 1209191501 6360795559 sdi? ? ? ? ? ? ? 52.47? ? ? 2033.16? ? ?10684.48 1210399262 6360795559 sdk? ? ? ? ? ? ? 52.09? ? ? 2033.15? ? ?10684.36 1210396915 6360724971 sdl? ? ? ? ? ? ? 51.95? ? ? 2031.20? ? ?10684.36 1209235241 6360724971 md127? ? ? ? ? ?138...

...862.17 0.15 5.56 40.94 5.37 7.27 19.73 sdk 0.03 0.58 0.22 27.10 0.03 11.40 857.01 1.60 58.49 36.20 58.67 7.17 19.58 sdb 0.02 0.52 0.15 27.43 0.03 11.40 848.37 0.02 0.78 42.84 0.55 7.07 19.50 sdj 0.02 0.55 0.15 27.11 0.03 11.40 858.28 0.62 22.70 41.97 22.59 7.43 20.27 sdg 0.03 0.68 0.22 27.76 0.03 11.40 836.98 0.76 27.10 34.36 27.04 7.33 20.51 sde 0.03 0.48 0.22 26.99 0.03...

On 2016-05-25 19:13, Kelly Lesperance wrote: > Hdparm didn?t get far: > > [root at r1k1 ~] # hdparm -tT /dev/sda > > /dev/sda: > Timing cached reads: Alarm clock > [root at r1k1 ~] # Hi Kelly, Try running 'iostat -xdmc 1'. Look for a single drive that has substantially greater await than ~10msec. If all the drives except one are taking 6-8msec, but one is very

...0.15 5.56 40.94 5.37 7.27 19.73 >sdk 0.03 0.58 0.22 27.10 0.03 11.40 857.01 1.60 58.49 36.20 58.67 7.17 19.58 >sdb 0.02 0.52 0.15 27.43 0.03 11.40 848.37 0.02 0.78 42.84 0.55 7.07 19.50 >sdj 0.02 0.55 0.15 27.11 0.03 11.40 858.28 0.62 22.70 41.97 22.59 7.43 20.27 >sdg 0.03 0.68 0.22 27.76 0.03 11.40 836.98 0.76 27.10 34.36 27.04 7.33 20.51 >sde 0.03 0.48 0.22 26.99...

...blk/queue/max_hw_sectors_kb` ? ??????? printf "%-18s: %-37s %-15s %-18s\n" $sysblk "$name" $max_sectors_kb $max_hw_sectors_kb done The boot volume is identified by the multipath wwid 3600144f00000000000005a2769c70001. It's underlying device nodes are: sda, sdd, sde, sdk and sdj. Running the script after boot for the boot device I get this: # max_sectors_kb | grep -e 3600144f00000000000005a2769c70001 -e sda -e sdd -e sde -e sdk -e sdj -e max Sys Block Node??? : Device??????????????????????????????? max_sectors_kb? max_hw_sectors_kb /sys/block/dm-1?? : 3600144f000000000000...

...ing an image to an sd card via a reader, I got the following bug. The system also has a btrfs root, and a whole swath of processes went into uninterruptable sleep. I was able to poke around via ssh and sysrq, and already had netconsole set up to capture the bug. Root fs is on /dev/sdi1, and /dev/sdj2 is the card reader which was the target of the untar. [29571.448889] sd 11:0:0:0: [sdj] Assuming drive cache: write through [29571.451153] sdj: unknown partition table [29572.047390] sd 11:0:0:0: [sdj] Assuming drive cache: write through [29572.048149] sdj: sdj1 sdj2 [29602.642175] device fsid...

...ke to replace the ide disks with scsi disks or sata disks (these also recognized as scsi in the kernel). but we can't boot from it. the problem are twofold. first in the normal case the first scsi host scsi0 id the 3ware card, but grub only see the first 8 disk so if the system disk are sdi and sdj the one can't boot from it. on the other hand if one disk is removed from the 3ware card or the kernel reorder the scsi disk and sdi become sdh which is also a problem both for the bios and for the kernel. if i change the order in bios, the kernel still use as 3ware scsi0. if i use scsihosts ke...

Hi All Currently i'm setting up a 5.4 server and try to create a 3rd raid device, when i run: $mdadm --create /dev/md2 -v --raid-devices=15 --chunk=32 --level=raid6 /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo /dev/sdp /dev/sdq the device file "md2" is created and the raid is being configured. but somehow /dev/md2 is flushed when i reboot the system , same story if i create the file by mknod or MAKEDEV. does anyone know a way to solve this issue and...

...0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 sde ONLINE 0 0 0 sdf ONLINE 0 0 0 sdg ONLINE 0 0 0 sdh ONLINE 0 0 0 sdi ONLINE 0 0 0 sdj ONLINE 0 0 0 sdk ONLINE 0 0 0 spares sdl INUSE currently in use but when I try zpool replace export1 /dev/sdb1, it says, nope, invalid vdev specification use '-f' to override the following errors: /dev/sdb1 is part of active pool ...

...tached scsi disk sdi at scsi3, channel > > 0, id 0, lun 8 > > [ 69.143037] Vendor: DotHill Model: SANnet II FC > > Rev: 327R > > [ 69.143421] Type: Direct-Access > > ANSI SCSI revision: 03 > > [ 69.144036] SCSI device sdj: 2097152 512-byte hdwr > > sectors (1074 MB) > > [ 69.144635] SCSI device sdj: drive cache: write through > > [ 69.145044] SCSI device sdj: 2097152 512-byte hdwr > > sectors (1074 MB) > > [ 69.145640] SCSI device sdj: drive cache: write through > > [...

...tached scsi disk sdi at scsi3, channel > > 0, id 0, lun 8 > > [ 69.143037] Vendor: DotHill Model: SANnet II FC > > Rev: 327R > > [ 69.143421] Type: Direct-Access > > ANSI SCSI revision: 03 > > [ 69.144036] SCSI device sdj: 2097152 512-byte hdwr > > sectors (1074 MB) > > [ 69.144635] SCSI device sdj: drive cache: write through > > [ 69.145044] SCSI device sdj: 2097152 512-byte hdwr > > sectors (1074 MB) > > [ 69.145640] SCSI device sdj: drive cache: write through > > [...

...sdo devid 10 size 931.51GB used 90.50GB path /dev/sdn devid 9 size 931.51GB used 90.50GB path /dev/sdm devid 8 size 931.51GB used 90.50GB path /dev/sdl devid 7 size 931.51GB used 91.50GB path /dev/sdk devid 6 size 931.51GB used 91.49GB path /dev/sdj devid 5 size 931.51GB used 91.33GB path /dev/sdi devid 4 size 931.51GB used 91.50GB path /dev/sdh devid 2 size 931.51GB used 91.33GB path /dev/sdf devid 1 size 931.51GB used 90.52GB path /dev/sde Also tried to again remove (physical) the disk drive, b...

Hi, I have compiled xen-unstable (using hg clone http://xenbits.xensource.com/xen-unstable.hg). I have successfully booted into the dom0 kernel. output of xm list: Name ID Mem VCPUs State Time(s) Domain-0 0 932 1 r----- 591.2 But whenever I xm create, I get: # xm create /etc/xen/domu1 Using config file

...er, whenever I have more than 4 drives, it seems that anaconda ignores my --ondisk, and lays out /dev/md0 somewhat randomly across the drives. In particular, with 8 drives (sda..sdh), with the exact same kickstart file, it lays out /dev/md0 on drives sda, sdb, sdg and sdh. with 10 drives (sda..sdj), with the exact same kickstart file, it lays out /dev/md0 on drives sda, sdh, sdi, sdj. Does this make sense to anybody? Any help would be appreciated greatly. Thanks! Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/...

Hello ! I''m trying to run Xen on a EC2 AMI debian-6.0-squeeze-base-x86_64-20110417 (ami-35b68141) Following this how-to http://www.howtoforge.com/paravirtualization-with-xen-4.0-on-debian-squeeze-amd64 After installing the packages, I get : uname -a Linux ip-10-241-22-60 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux uname -r 2.6.32-5-xen-amd64 Then I do :

...; Subscribe now so you don''t miss out. > > http://xenproject.org/subscribe.html > > Russell Pavlicek > Xen Project Evangelist > > > > ------------------------------ > > Message: 4 > Date: Fri, 11 Oct 2013 12:50:21 -0600 > From: Shane Johnson <sdj@rasmussenequipment.com> > To: Russ Pavlicek <russell.pavlicek@xenproject.org> > Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>, > xen-api@lists.xen.org > Subject: Re: [Xen-users] Subscribe today to the Xen Project Newletter > Message-ID: > <C...

...er the mount point specified. If I remove the drive and insert it back in after a while, the drive doesn't mount, even though I have the required entry in fstab. `mount -a` doesn't seem to work and provides me the following output, mount: wrong fs type, bad option, bad superblock on /dev/sdj, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so If I restart my server, the drive gets mounted in the correct mount point and works fine. Can someone please shed some light on why a restart is required...