search for: sdc2

.../16 08:19, Leon Fauster wrote: <<>> > check it with: > > blockdev --getalignoff /dev/sd > > (if a '0' is returned, the partition is aligned) > ===> Leon, thank you for reply. ]$ sudo blockdev --getalignoff /dev/sdc1 0 ]$ sudo blockdev --getalignoff /dev/sdc2 0 ]$ sudo blockdev --getalignoff /dev/sdc5 2560 ]$ sudo blockdev --report /dev/sdc1 RO RA SSZ BSZ StartSec Size Device rw 256 512 4096 2048 838860800 /dev/sdc1 ]$ sudo blockdev --report /dev/sdc2 RO RA SSZ BSZ StartSec Size Device rw...

...v to show up /bin/cat: /sys/block/sdc/dev: No such file or directory Device /sys/block/sdc/dev seems to be down. /bin/mknod: missing operand after `b'' Special files require major and minor device numbers. Try `/bin/mknod --help'' for more information. /bin/cat: /sys/block/sdc/sdc2/dev: No such file or directory Waiting 1 seconds for /sys/block/sdc/sdc2/dev to show up /bin/cat: /sys/block/sdc/sdc2/dev: No such file or directory Waiting 2 seconds for /sys/block/sdc/sdc2/dev to show up /bin/cat: /sys/block/sdc/sdc2/dev: No such file or directory Waiting 4 seconds for /sys/...

...'s seems to work)? * If yes, how to fix them? [root at frodo pilpel10]# uname -a Linux frodo 2.6.9-34.0.1.ELsmp #1 SMP Wed May 24 05:28:30 CDT 2006 x86_64 x86_64 x86_64 GNU/Linux Using lvm2 2.02.01-1.3 Thanks in advance, Itay <quote> [root at frodo pilpel10]# vgcreate VGe1 /dev/sdc2 /dev/dm-11: read failed after 0 of 4096 at 5242814464: Input/output error /dev/dm-11: read failed after 0 of 4096 at 0: Input/output error /dev/dm-12: read failed after 0 of 4096 at 54460416: Input/output error /dev/dm-12: read failed after 0 of 4096 at 0: Input/output error /dev/dm-...

...ckup. Lug it back and forth and sync as appropriate. So I wrote myself a little rsync script which grabs all the files I think of as taking work to recreate. Which is given as follows: rsync -avl --stats --progress --timeout=300 --exclude-from "/home/foo/bin/exclude.txt" /home /mnt/sdc2 rsync -avl --stats --progress --timeout=300 --exclude-from "/home/foo/bin/exclude.txt" /etc /mnt/sdc2/beast rsync -avl --stats --progress --timeout=300 --exclude-from "/home/foo/bin/exclude.txt" /srv /mnt/sdc2/beast Since there are, as with any backups, files I don't want...

....git3.1.fc21.x86_64 from rawhide, reboot and try again. The rebalancing works well this time but is, as expected, very slow (about 50GB in half a day). I return home and leave the pc runnung all the night. The morning I find this: Sep 30 23:11:53 tambura kernel: [37787.652143] BTRFS error (device sdc2) in btrfs_create_pending_block_groups:8516: errno=-5 IO failure Sep 30 23:11:53 tambura kernel: [37787.652145] BTRFS info (device sdc2): forced readonly the whole messages.log is here: http://paste.fedoraproject.org/44143/24287138/ N.B: sdc2 is the partition of the new drive that, however, has no...

...clean and working CentOS4.2 install, and I am trying to use an external usb to ide converter to mount it on another workstation with CentOS4.2. I am trying this to better understand how LVM works, in the case of a future disaster/recovery scenario. Simply trying to mount it: mount -t ext3 /dev/sdc2 /share/ mount: wrong fs type, bad option, bad superblock on /dev/sdc2, or too many mounted file systems fdisk -l shows /dev/sdc1 * 1 13 104391 83 Linux /dev/sdc2 14 7476 59946547+ 8e Linux LVM and in fact, /dev/sdc1 is automatically mounted....

...vice sdc: 997759 2048-byte hdwr sectors (2043 MB) kernel: sdc: Write Protect is off kernel: sdc: assuming drive cache: write through kernel: SCSI device sdc: 997759 2048-byte hdwr sectors (2043 MB) kernel: sdc: Write Protect is off kernel: sdc: assuming drive cache: write through kernel: sdc: sdc1 sdc2 kernel: sd 13:0:0:0: Attached scsi removable disk sdc kernel: sd 13:0:0:0: Attached scsi generic sg2 type 0 Before of all, I'm using this software versions: kernel (vanilla): 2.6.19.7 syslinux: 3.36-1 (from syslinux rpm repository) fdisk: util-linux 2.13-pre7 mkdosfs: (don't know how to ob...

...dc 4294967296 ><fs> part-list /dev/sdc [0] = { part_num: 1 part_start: 65536 part_end: 2193555455 part_size: 2193489920 } [1] = { part_num: 2 part_start: 2193555456 part_end: 4294967295 part_size: 2101411840 } ><fs> list-filesystems /dev/sdc1: ext3 /dev/sdc2: ntfs So I have two parititons up to image end, and 64k block at the start. I wanted to shrink the last partition by 1MB (for test, yeah). I shrank the filesystem by 1MB but virt-resize refused to resize to 4095MB image requesting ~2MB more (the numbers you can see in log attached). So I had t...

...logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0009ede7 Device Boot Start End Blocks Id System /dev/sdc1 * 1 103 819200 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdc2 103 230 1024000 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/sdc3 230 2107 15073280 83 Linux /dev/sdc4 2107 121602 959844352 5 Extended /dev/sdc5 2108 42019 320587970+ 83 Li...

On 04/22/2016 09:43 AM, g wrote: > ]$ sudo blockdev --getalignoff /dev/sdc1 > 0 > ]$ sudo blockdev --getalignoff /dev/sdc2 > 0 > ]$ sudo blockdev --getalignoff /dev/sdc5 > 2560 > ]$ sudo blockdev --report /dev/sdc1 > RO RA SSZ BSZ StartSec Size Device > rw 256 512 4096 2048 838860800 /dev/sdc1 > ]$ sudo blockdev --report /dev/sdc2 > RO RA SSZ BSZ...

Hi, I have been attempting to set up a multi-boot USB stick (i.e. multiple bootable ISO images on the one stick) I have had good success by: - processing ISO with isohybrid (with "partok" flag) - dd'ing ISO to primary partitions on the USB stick (e.g /dev/sdc2, /dev/sdc3, /dev/sdc4) - installing grub to USB stick and configuring to chainload to these partitions To remove the limit of 4 partitions, I would like to do the above but utilise logical partitions. All my tests to do this have failed, and generally result in the error message "isolinux.bin...

...changed) /dev/disk/by-id/: lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sdc lrwxrwxrwx 1 root root 10 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_01000000 -> ../../sdb lrwxrwxrwx 1 root root 9 Mar 1 08:09 scsi-0HP_LOGICAL_VOLUME_02000000 -> ../../sda lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_03000000 -> ../../sdd lrwxrwxrwx 1 root root 9 Mar 1 08...

...evel 5 across 4 disks. With Slackware I created the arrays manually like this: # mdadm --create /dev/md1 --level=1 --raid-devices=4 --metadata=0.90 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 # mdadm --create /dev/md2 --level=1 --raid-devices=4 --metadata=0.90 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 # mdadm --create /dev/md3 --level=5 --raid-devices=4 --metadata=0.90 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 Using this setup, I had 650 MB of disk space on /dev/md3. Now I tried to do the same thing with CentOS 7. Everything seemed to work at first, but here's what I got n...

...esh install - use this as a base to create/upgrade new/old machines. I was trying to setup two disks as a RAID1 array, using these lines mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 /dev/sdc2 mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2 /dev/sdb3 /dev/sdc3 then I did a lsblk and realized that I used --level=0 instead of --level=1 (spelling mistake) The SIZE was reported double as I created a striped set by mistake, yet I wanted the mirrored. Here starts my problem, I...

On Fri, 2015-08-14 at 12:39 -0500, Michael Hennebry wrote: > On Thu, 13 Aug 2015, Leon Fauster wrote: > > > Could you provide more context information? > > Appliance setup, Dekstop setup, server setup? > > There exist a lot scenarios where something > > happen automagically? > > It's a Chimera Desktop 2014. > More specifically, I bought the case, the

...a base to create/upgrade new/old machines. > > I was trying to setup two disks as a RAID1 array, using these lines > > mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 > mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 /dev/sdc2 > mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2 /dev/sdb3 /dev/sdc3 > > then I did a lsblk and realized that I used --level=0 instead of --level=1 (spelling mistake) > The SIZE was reported double as I created a striped set by mistake, yet I wanted the mirrored. >...

I want to install Centos Stream on an older server. the Areca ARC-1680 RAID Controller is not supported anymore, so I tried to install on an external USB drive. i did a manual partitioning: sdc1 /boot/efi efi system partition sdc2 /boot ext4 sdc3 / lvm and the system cannot boot - hangs forever. new try: sdc1 /boot/efi, efi system partition sdc2 / xfs at end of install i see 'bootloader install failed'. debug shows 'NOTICE root:83haiku: debug: /dev/sdc1 is not a beFS partiotion: exitin...

...: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdd 8:48 0 931.5G 0 disk ??sdd1 8:49 0 931.5G 0 part ??mpathi (dm-0) 253:0 0 931.5G 0 mpath sdc 8:32 0 931.5G 0 disk ??sdc1 8:33 0 1000M 0 part /boot ??sdc2 8:34 0 31.3G 0 part / ??sdc3 8:35 0 31.3G 0 part [SWAP] ??sdc4 8:36 0 1K 0 part ??sdc5 8:37 0 184.5G 0 part /home ??sdc6 8:38 0 683.6G 0 part /data01 sde 8:64 0 931.5G 0 disk ??s...

...lover > > at the moment there is: > > dc1 is samba ad member but has no installed printer > > client -> dc2 -> printer connect via IP > (client download the driver from dc2) > > what is when dc2 is down? as I understand that right client > cant print because sdc2 is down. > > now my question: > is there a way to do a failover, if dc2 is down use dc1 as > printserver, (without installing a 2nd printer on the client > which connected to dc1) > > On 26.04.2017 15:13, L.P.H. van Belle via samba wrote: > > Just setup a separated pr...

...evel 5 across 4 disks. With Slackware I created the arrays manually like this: # mdadm --create /dev/md1 --level=1 --raid-devices=4 --metadata=0.90 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 # mdadm --create /dev/md2 --level=1 --raid-devices=4 --metadata=0.90 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 # mdadm --create /dev/md3 --level=5 --raid-devices=4 --metadata=0.90 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 Using this setup, I had 650 MB of disk space on /dev/md3. Now I tried to do the same thing with CentOS 7. Everything seemed to work at first, but here's what I got n...