similar to: forcing device to USB HDD

I think I have solved my issue and would like some input from anyone who has done this for pitfalls, errors, or if I am just wrong. Centos 5.x, software raid, 250gb drives. 2 drives in mirror, one spare. All same size. 2 devices in the mirror, one boot (about 100MB), one that fills the rest of disk and contains LVM partitions. I was thinking of taking out the spare and adding a 500gb drive. I

Hi, I do have an iscsi storage with two raidsets. I'm logged in to the target and get two devices: /dev/sdb and /dev/sdc. After formatting the devices with ext4 I realised, that I had used a wrong label, so I tried to relabel the devices. But now I'm confused: doing a e2label /dev/sdb or /dev/sdc returns always the same label name for both devices. so I did "e2label /dev/sdb

Hi, i have a system with /dev/sda - System Hard Drive /dev/md0 - SoftwareRaid 5 for Data with /dev/sdb /dev/sdc /dev/sdd Now i have one more in a removeable frame for Backup /dev/sde /dev/md0 is forwarded to an Samba-Domain for Data service in the network. What''s the best way to sync the data from /dev/md0 to /dev/sde ? is a domain hotplug able ? So when i plug in /dev/sde,

Basically the issue comes down to my Volume Groups not being found by this initrd, causing good ole kernel panic. initrd-2.6.12.6-xen3_12.1_rhel4.1.img [root@xen01 lvm]# uname -a Linux xen01.inside.***.com 2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:13:01 EST 2006 i686 i686 i386 GNU/Linux [root@xen01 lvm]# cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 2) Everything

On Thu, Feb 28, 2019 at 05:19:49PM +0100, Nicolas Kovacs (info at microlinux.fr) wrote: > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > > I want to lock in the SDA/SDB/SDC for my drives > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. I **KNOW** how to use UUID's ... this is NOT the reason why I am doing this! I *NEED* the order of the disks to be

Dear All I needed to clone my disk to another hard drive . I did it as the following : #dd if=/dev/sdb of=/dev/sdc But after a while, the procedure ended with the "writing to /dev/sdc input/output error" message. Can you please let me know how can I overcome this as the fdisk now returns as " #fdisk /dev/sdc "I do not know how to handle files with mode 81a4 must set

Trying to setup a volume group with puppet lvm and this:- volume_group { "my_vg": ensure => present, physical_volumes => "/dev/sdb /dev/sdc /dev/sdd", require => [ Physical_volume["/dev/sdb"], Physical_volume["/dev/sdc"], Physical_volume["/dev/sdd"] ] } Fails with this in the debug

So if you have a mount command that doesn''t use /etc/mtab then it will spit out a different device for the mounted device. So say we have SCRATCH_DEV_POOL="/dev/sda /dev/sdb /dev/sdc" we will turn this into SCRATCH_DEV="/dev/sda" SCRATCH_DEV_POOL="/dev/sdb /dev/sdc" and then when you mkfs this you do _scratch_mkfs $SCRATCH_DEV_POOL which turns into this

Hi， 在 2015年06月16日 20:56, Pino Toscano 写道: > On Tuesday 16 June 2015 17:10:09 Cao jin wrote: >> Also modified a public function: analyze_line, make it more flexible > > The addition of the parameter to analyze_line should be in an own > patch. Can you please decouple it? > OK >> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com> >> --- >>

[root@btrfs progs-unstable]# btrfsctl -A /dev/sdb ioctl returns 0 [root@btrfs progs-unstable]# btrfsctl -A /dev/sdc ioctl returns 0 /dev/sdb has a btrfs, while /dev/sdc is blank. What''s that output supposed to mean ? Is it a bug ? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info

Hello, I have a server working on centos 5.7-64 minimal installation. I have 3 separate physical drives: 120 gb ssd, 2x 3tb disks for storage. My linux installation is on ssd disk, and I want to make raid 1 for these two 3tb disks and store data, like under /mnt/data. Can you please tell me the path how this is possible? Thanks for your help! Best regards, Here are some output of commands I

Greetings, I have a system x3100 m4 system with 64GB SSD for OS and 2x2tb for data as MD device (software RAID). It had Fedora 17 with EFI/ I tried to install centos 6. deleting the existing partitions on the SSD /dev/sdc. sda and sdb are the 2x2tb md device mounted on /home. no joy. googling Questions: 1. Where do I locate the boot loader? /dev/sdc? is MBR (the default with Centos) enough

I?ve posted this on the forums at https://www.centos.org/forums/viewtopic.php?f=47&t=57926&p=244614#p244614 - posting to the list in the hopes of getting more eyeballs on it. We have a cluster of 23 HP DL380p Gen8 hosts running Kafka. Basic specs: 2x E5-2650 128 GB RAM 12 x 4 TB 7200 RPM SATA drives connected to an HP H220 HBA Dual port 10 GB NIC The drives are configured as one large

I can't seem to figure out how to partition for install. I've tried both CentOS 8 and 7.7 netinstalls. I've got 3 disks: sda (big hardware RAID array), sdb (SSD), and sdc (internal SD card for booting). I want to put /boot on sdc, /usr on sdb, and / on sda. I don't care what format is used on sdb and sdc, whatever will let it boot. I want LVM on sda so that I can use

All of our Kafka clusters are fairly write-heavy. The cluster in question is our second-heaviest ? we haven?t yet upgraded the heaviest, due to the issues we?ve been experiencing in this one. Here is an iostat example from a host within the same cluster, but without the RAID check running: [root at r2k1 ~] # iostat -xdmc 1 10 Linux 3.10.0-327.13.1.el7.x86_64 (r2k1) 05/27/16 _x86_64_ (32 CPU)

Hi, I added a new drive to an existing RAID 0 array. Every attempt to rebalance the array fails: # btrfs filesystem balance /share/bd8 ERROR: error during balancing ''/share/bd8'' - Input/output error # dmesg | tail btrfs: found 1 extents btrfs: relocating block group 10752513540096 flags 1 btrfs: found 5 extents btrfs: found 5 extents btrfs: relocating block group 10751439798272

I have a machine that's been configured as follows using its BIOS tools: SATA-0 is a 160 GiB drive used as boot SATA-1 and SATA-2 are both 500 GiB drives and were configured as a RAID-1 in BIOS. When the system boots up, BIOS reports 1 160 GiB SATA drive, and 1 Logical volume as RAID-1 ID#0 500 GiB, which is what I would expect it to report, as the two drives are now raided

Hi I have read instructions for udev, I also found many example on how to do this. I want to lock in the SDA/SDB/SDC for my drives and I came up with a rule like this KERNEL=="sd?", SUBSYSTEM=="block", ENV{ID_SERIAL}=="ST500DM002-1BC142_W2A56H8A", NAME="sda", RUN+="/usr/bin/logger ID_SERIAL=$ENV{ID_SERIAL} set to /dev/sda ",

Hi there, I have a system with the following: # fdisk -l Disk /dev/sda: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 9471 75971385 83 Linux /dev/sda3

thanks for the reply, Phil It would, were udev not inserting USB and/or eSATA drives at /dev/sdb1 and/or /dev/sdc1 and exposing the array to the udev rule intended to handle only removable devices (at sdc or sdd). The array then mounts unpredictably in /media/xxx-sdc1 or sdd1 - not what is wanted - depend on how many removable devices are plugged at the time of rebooting. Of course, a single