search for: sdg1

...0x70000 Nov 9 01:10:40 kasse kernel: end_request: I/O error, dev sdg, sector 37479 Nov 9 01:13:08 kasse kernel: SCSI error : <12 0 0 0> return code = 0x70000 Nov 9 01:13:08 kasse kernel: end_request: I/O error, dev sdg, sector 37487 Nov 9 01:13:08 kasse kernel: Buffer I/O error on device sdg1, logical block 4678 Nov 9 01:13:08 kasse kernel: lost page write due to I/O error on sdg1 Nov 9 01:13:08 kasse kernel: Aborting journal on device sdg1. Nov 9 01:13:13 kasse kernel: ext3_abort called. Nov 9 01:13:13 kasse kernel: EXT3-fs error (device sdg1): ext3_journal_start_sb: Detected abo...

...% /bricks/sdd1 /dev/sde1????????????????????????? 7.3T? 657G? 6.7T?? 9% /bricks/sde1 /dev/sde1????????????????????????? 7.3T? 658G? 6.7T?? 9% /bricks/sde1 /dev/sdf1????????????????????????? 7.3T? 711G? 6.6T? 10% /bricks/sdf1 /dev/sdf1????????????????????????? 7.3T? 711G? 6.6T? 10% /bricks/sdf1 /dev/sdg1????????????????????????? 7.3T? 756G? 6.6T? 11% /bricks/sdg1 /dev/sdg1????????????????????????? 7.3T? 756G? 6.6T? 11% /bricks/sdg1 /dev/sdh1????????????????????????? 7.3T? 753G? 6.6T? 11% /bricks/sdh1 /dev/sdh1????????????????????????? 7.3T? 753G? 6.6T? 11% /bricks/sdh1 [root at st-srv-03 ~]# df -h...

Hi, I have a 'little' issue with my bootable USB keys... The following used to work (isolinux 3.11-4): Device Boot Start End Blocks Id System /dev/sdg1 * 1 3 23126 6 FAT16 /dev/sdg2 4 1023 7873380 83 Linux mkfs.vfat -n BOOT /dev/sdg1 mkfs.ext2 -m 0 -b 4096 -L DATA /dev/sdg2 syslinux -s /dev/sdg1 cd /media/BOOT cp -rv /mnt/cdrom/isolinux syslinux mv syslinux/isolinux.cfg syslinux/syslinu...

...oking for devices for /dev/md0 mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 0. mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot -1. mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 2. mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 3. mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 4. mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot -1. mdadm: no uptodate device for slot 1 of /dev/md0 mdadm: added /dev/sde1 to /dev/md0 as 2 mdadm: added /dev/sdf1 to /dev/md0 as 3 mdadm: added /dev/sdg1 to /dev/md0 as 4 mdadm: no uptodate...

...two logical volumes (named "root" and "swap"), containing the root file system and a base 1G swap area. So far so good. On the Marvell controller are 4 1.5GB disks arranged as a RAID10 array: [heller at ravel ~]$ cat /proc/mdstat Personalities : [raid10] md1 : active raid10 sdg1[3] sdf1[2] sde1[1] sdd1[0] 2930270208 blocks 512K chunks 2 far-copies [4/4] [UUUU] unused devices: <none> [heller at ravel ~]$ sudo /sbin/mdadm --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Tue Jun 21 19:04:19 2011 Raid Level : raid10 Array Size :...

...c1 is identified as a member of >> /dev/md0, slot 0. >> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot -1. >> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 2. >> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 3. >> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 4. >> mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot -1. >> mdadm: no uptodate device for slot 1 of /dev/md0 >> mdadm: added /dev/sde1 to /dev/md0 as 2 >> mdadm: added /dev/sdf1 to /dev/md0 as 3 >> mdadm: added...

...9168 512-byte hdwr sectors (750156 MB) sdg: Write Protect is off sdg: Mode Sense: 10 00 00 00 sdg: assuming drive cache: write through SCSI device sdg: 1465149168 512-byte hdwr sectors (750156 MB) sdg: Write Protect is off sdg: Mode Sense: 10 00 00 00 sdg: assuming drive cache: write through sdg: sdg1 sd 27:0:0:0: Attached scsi disk sdg sd 27:0:0:0: Attached scsi generic sg6 type 0 usb-storage: device scan complete [root at kasse ~]# pvcreate /dev/sdg1 Physical volume "/dev/sdg1" successfully created [root at kasse ~]# vgcreate testgroup /dev/sdg1 Volume group "testgroup&quo...

Hallo, I''d like to get some explanations ... # btrfs filesystem show Label: ''MMedia'' uuid: 120b036a-883f-46aa-bd9a-cb6a1897c8d2 Total devices 3 FS bytes used 3.80TB devid 1 size 1.82TB used 1.29TB path /dev/sdg1 devid 3 size 1.81TB used 1.29TB path /dev/sdc1 devid 2 size 1.81TB used 1.28TB path /dev/sdb1 Btrfs Btrfs v0.19 # btrfs filesystem df /srv/MM Data, RAID0: total=3.83TB, used=3.80TB System, RAID1: total=16.00MB, used=248.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=16.25GB,...

...r than where I started looking...) Brought it up, RAID not working. I finally found that I had to do an mdadm --stop /dev/md0, then I could do an assemble, then I could add the new drive. But: it's now cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 : active (auto-read-only) raid5 sdg1[8](S) sdh1[7] sdf1[4] sde1[3] sdd1[2] sdc1[1] 23441313792 blocks super 1.2 level 5, 512k chunk, algorithm 2 [7/5] [_UUUU_U] bitmap: 0/30 pages [0KB], 65536KB chunk unused devices: <none> and I can't mount it (it's xfs, btw). *Should* I make it readwrite, or is there some...

I'm having problems installing CentOS via a USB drive. First, I tried using Unetbootin, but with no avail. The 8MB netinstall doesn't work, and the big DVD image doesn't work either. http://lubi.sourceforge.net/unetbootin.html Then I tried this http://www.pendrivelinux.com/usb-centos-5-live-install-via-windows/ with a CentOS DVD file, and that did not work (just hangs). I tried

...>> /dev/md0, slot 0. >>>> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot -1. >>>> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 2. >>>> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 3. >>>> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 4. >>>> mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot -1. >>>> mdadm: no uptodate device for slot 1 of /dev/md0 >>>> mdadm: added /dev/sde1 to /dev/md0 as 2 >>>> mdadm: added /dev/sdf1 to /dev...

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

.../dev/sdd1 is identified as a member of /dev/md0, slot -1. >>>>>> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot >>>>>> 2. >>>>>> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 3. >>>>>> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 4. >>>>>> mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot -1. >>>>>> mdadm: no uptodate device for slot 1 of /dev/md0 >>>>>> mdadm: added /dev/sde1 to /dev/md0 as 2 >>>>>&g...

I've run into a rather odd problem. It seems that I can format and make bootable CF/SD cards and USB Flashdrives under Windows 98SE and MS-DOS 6.22 that will boot to a A: prompt on my system. But when I try making the same CF/SD cards and USB Flashdrives bootable under linux using syslinux I get nothing, not even a error message. It's like the syslinux bootloader doesn't even

...: >>>>>>>> /dev/sde1 is identified as a member of /dev/md0, slot >>>>>>>> 2. >>>>>>>> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot >>>>>>>> 3. >>>>>>>> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot >>>>>>>> 4. >>>>>>>> mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot >>>>>>>> -1. >>>>>>>> mdadm: no uptodate device for slot 1 of /dev/md0 >&g...

...ut --force), fails with the message: ??? mdadm: Found some drive for an array that is already active: /dev/md127 ??? mdadm: giving up I found with some digging that I needed to change the UUID of the drive to be able to mount it separately from the existing array.? I used "sgdisk -G /dev/sdg1" to do this.? It worked, but gave quite a few scary warning messages in the process.? A better idea would have been to use uuidgen to generate a random uuid and then start the array like this: ??? mdadm --assemble /dev/md99 --update=uuid --uuid=<newuuid> /dev/sdg1 (might require --fo...

I've noticed that once I right click on my flash drive icon and umount it, in order to remount it I have to unplug it and then plug it back in. Is there a command that will accomplish the same task without the unplug and plug back in physics? Thanks. mhr

Hi, I tried to convert my working 5.3 USB bootable key to 5.4 and I apparently cannot get syslinux to find/read its configuration file anymore... I followed the same process as before: mkfs.vfat -n BOOT /dev/sdg1 syslinux -s /dev/sdg1 cd /media/BOOT cp -rv /mnt/cdrom/isolinux syslinux mv syslinux/isolinux.cfg syslinux/syslinux.cfg rm -f syslinux/isolinux.bin vi syslinux/syslinux.cfg dd if=/usr/lib/syslinux/mbr.bin of=/dev/sdg I get: syslinux: cannot find kernel linux I tried to copy sysli...

On my Centos box with: uname -r 2.6.18-164.6.1.el5 I tried to mount my 2T external drive with: mount -t ntfs /dev/sdg1 /mnt/wd and I get: mount: unknown filesystem type 'ntfs' Thanks in advance for your help. Mike.

...v/md0 > mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 0. > mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot -1. > mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 2. > mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 3. > mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 4. > mdadm: /dev/sdh1 is identified as a member of /dev/md0, slot -1. > mdadm: no uptodate device for slot 1 of /dev/md0 > mdadm: added /dev/sde1 to /dev/md0 as 2 > mdadm: added /dev/sdf1 to /dev/md0 as 3 > mdadm: added /dev/sdg1 to /dev/md...