Ubuntu 18.04.2 RAID Problems?Do I have a raid or not?Deleted Windows Partitions on drive now what do I do?Drive failure in Raid1. Can't replaceBreaking boot-up Raid 1 array into two independent drivesRebuilding a RAID 1 array on a production server (Ubuntu 12.04.2 LTS)How to configure existing raid after upgrading to 14.04 from 11Intel RAID5 array Shows < 50% spaceUbuntu 16.04 LTS unrecognized hard drive — not enough disk space to installExternal Hard Disk not recognised on USB 3 portHow to install grub after fatal error on failed RAID system?

arcpy.GetParameterAsText not passing arguments to script?

Scala list with same adjacent values

Why does my electric oven present the option of 40A and 50A breakers?

Asking for something with different prices

Singlequote and backslash

Creating Fictional Slavic Place Names

Can I ask a publisher for a paper that I need for reviewing

Coding Challenge Solution - Good Range

Cryptography and patents

Have powerful mythological heroes ever run away or been deeply afraid?

Why does the UK have more political parties than the US?

If a massive object like Jupiter flew past the Earth how close would it need to come to pull people off of the surface?

Why is Colorado so different politically from nearby states?

Are there mythical creatures in the world of Game of Thrones?

Do adult Russians normally hand-write Cyrillic as cursive or as block letters?

How to properly maintain eye contact with people that have distinctive facial features?

Looking for an old image of designing a cpu with plan laid out / being edited on a literal floor

What is the intuition behind uniform continuity?

Can a helicopter mask itself from Radar?

Is the capacitor drawn or wired wrongly?

TV show or movie: Diseased people are exiled to a spaceship

Why use water tanks from a retired Space Shuttle?

How should I push back against my job assigning "homework"?

The most awesome army: 80 men left and 81 returned. Is it true?



Ubuntu 18.04.2 RAID Problems?


Do I have a raid or not?Deleted Windows Partitions on drive now what do I do?Drive failure in Raid1. Can't replaceBreaking boot-up Raid 1 array into two independent drivesRebuilding a RAID 1 array on a production server (Ubuntu 12.04.2 LTS)How to configure existing raid after upgrading to 14.04 from 11Intel RAID5 array Shows < 50% spaceUbuntu 16.04 LTS unrecognized hard drive — not enough disk space to installExternal Hard Disk not recognised on USB 3 portHow to install grub after fatal error on failed RAID system?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I installed Ubuntu 18.04.2 a few days ago. It's installed on a 250GB SSD and I also have a RAID0 that I configured through the Intel Rapid Storage BIOS with two 2TB Enterprise drives. Now for some reason the 2 drives show up as sdb and sdc but also the 4TB RAID Volume shows up and I can use it. GParted gives me 2 Errors every time I start it and under fdisk -l there are 16 loop devices. I mean it works but it seems very weird and although a RAID0 is more or less risky anyway I don't want to loose the data only because something is configured wrong.
Is there something I can do to fix this?



The two GParted Errors:



The first error message is german and roughly says "The argument is invalid, while /dev/sdb is positioned to read from"



First Error



Second Error



Output of fdisk -l



Disk /dev/loop0: 3.7 MiB, 3821568 bytes, 7464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 4 MiB, 4218880 bytes, 8240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 3.7 MiB, 3878912 bytes, 7576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 2.3 MiB, 2355200 bytes, 4600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 1008 KiB, 1032192 bytes, 2016 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 89.3 MiB, 93581312 bytes, 182776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 35.3 MiB, 37027840 bytes, 72320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 202.3 MiB, 212099072 bytes, 414256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: EDD8F944-9636-4398-9E93-9279DFA5F3B7

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 500117503 499066880 238G Linux filesystem


Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdb1 1 4294967295 4294967295 2T ee GPT


Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/isw_fffhhebch_Volume1_RAID0: 3.7 TiB, 4000792707072 bytes, 7814048256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: 7059BA95-67D0-4AFC-98AA-6F192E03E2E3

Device Start End Sectors Size Type
/dev/mapper/isw_fffhhebch_Volume1_RAID0p1 2048 7814047743 7814045696 3.7T Linu


Disk /dev/loop8: 14.8 MiB, 15462400 bytes, 30200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 14.5 MiB, 15208448 bytes, 29704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 91 MiB, 95408128 bytes, 186344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 140.7 MiB, 147496960 bytes, 288080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 13 MiB, 13619200 bytes, 26600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 143.5 MiB, 150470656 bytes, 293888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop14: 140.7 MiB, 147496960 bytes, 288080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop15: 34.6 MiB, 36216832 bytes, 70736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop16: 53.7 MiB, 56315904 bytes, 109992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


The Specs of the System: MSI Z97I-AC Motherboard, Intel Pentium G3258, 16GB RAM, GTX 960










share|improve this question




























    0















    I installed Ubuntu 18.04.2 a few days ago. It's installed on a 250GB SSD and I also have a RAID0 that I configured through the Intel Rapid Storage BIOS with two 2TB Enterprise drives. Now for some reason the 2 drives show up as sdb and sdc but also the 4TB RAID Volume shows up and I can use it. GParted gives me 2 Errors every time I start it and under fdisk -l there are 16 loop devices. I mean it works but it seems very weird and although a RAID0 is more or less risky anyway I don't want to loose the data only because something is configured wrong.
    Is there something I can do to fix this?



    The two GParted Errors:



    The first error message is german and roughly says "The argument is invalid, while /dev/sdb is positioned to read from"



    First Error



    Second Error



    Output of fdisk -l



    Disk /dev/loop0: 3.7 MiB, 3821568 bytes, 7464 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop1: 4 MiB, 4218880 bytes, 8240 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop2: 3.7 MiB, 3878912 bytes, 7576 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop3: 2.3 MiB, 2355200 bytes, 4600 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop4: 1008 KiB, 1032192 bytes, 2016 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop5: 89.3 MiB, 93581312 bytes, 182776 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop6: 35.3 MiB, 37027840 bytes, 72320 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop7: 202.3 MiB, 212099072 bytes, 414256 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: EDD8F944-9636-4398-9E93-9279DFA5F3B7

    Device Start End Sectors Size Type
    /dev/sda1 2048 1050623 1048576 512M EFI System
    /dev/sda2 1050624 500117503 499066880 238G Linux filesystem


    Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000

    Device Boot Start End Sectors Size Id Type
    /dev/sdb1 1 4294967295 4294967295 2T ee GPT


    Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/mapper/isw_fffhhebch_Volume1_RAID0: 3.7 TiB, 4000792707072 bytes, 7814048256 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 131072 bytes / 262144 bytes
    Disklabel type: gpt
    Disk identifier: 7059BA95-67D0-4AFC-98AA-6F192E03E2E3

    Device Start End Sectors Size Type
    /dev/mapper/isw_fffhhebch_Volume1_RAID0p1 2048 7814047743 7814045696 3.7T Linu


    Disk /dev/loop8: 14.8 MiB, 15462400 bytes, 30200 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop9: 14.5 MiB, 15208448 bytes, 29704 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop10: 91 MiB, 95408128 bytes, 186344 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop11: 140.7 MiB, 147496960 bytes, 288080 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop12: 13 MiB, 13619200 bytes, 26600 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop13: 143.5 MiB, 150470656 bytes, 293888 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop14: 140.7 MiB, 147496960 bytes, 288080 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop15: 34.6 MiB, 36216832 bytes, 70736 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop16: 53.7 MiB, 56315904 bytes, 109992 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    The Specs of the System: MSI Z97I-AC Motherboard, Intel Pentium G3258, 16GB RAM, GTX 960










    share|improve this question
























      0












      0








      0








      I installed Ubuntu 18.04.2 a few days ago. It's installed on a 250GB SSD and I also have a RAID0 that I configured through the Intel Rapid Storage BIOS with two 2TB Enterprise drives. Now for some reason the 2 drives show up as sdb and sdc but also the 4TB RAID Volume shows up and I can use it. GParted gives me 2 Errors every time I start it and under fdisk -l there are 16 loop devices. I mean it works but it seems very weird and although a RAID0 is more or less risky anyway I don't want to loose the data only because something is configured wrong.
      Is there something I can do to fix this?



      The two GParted Errors:



      The first error message is german and roughly says "The argument is invalid, while /dev/sdb is positioned to read from"



      First Error



      Second Error



      Output of fdisk -l



      Disk /dev/loop0: 3.7 MiB, 3821568 bytes, 7464 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop1: 4 MiB, 4218880 bytes, 8240 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop2: 3.7 MiB, 3878912 bytes, 7576 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop3: 2.3 MiB, 2355200 bytes, 4600 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop4: 1008 KiB, 1032192 bytes, 2016 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop5: 89.3 MiB, 93581312 bytes, 182776 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop6: 35.3 MiB, 37027840 bytes, 72320 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop7: 202.3 MiB, 212099072 bytes, 414256 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier: EDD8F944-9636-4398-9E93-9279DFA5F3B7

      Device Start End Sectors Size Type
      /dev/sda1 2048 1050623 1048576 512M EFI System
      /dev/sda2 1050624 500117503 499066880 238G Linux filesystem


      Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x00000000

      Device Boot Start End Sectors Size Id Type
      /dev/sdb1 1 4294967295 4294967295 2T ee GPT


      Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/mapper/isw_fffhhebch_Volume1_RAID0: 3.7 TiB, 4000792707072 bytes, 7814048256 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 131072 bytes / 262144 bytes
      Disklabel type: gpt
      Disk identifier: 7059BA95-67D0-4AFC-98AA-6F192E03E2E3

      Device Start End Sectors Size Type
      /dev/mapper/isw_fffhhebch_Volume1_RAID0p1 2048 7814047743 7814045696 3.7T Linu


      Disk /dev/loop8: 14.8 MiB, 15462400 bytes, 30200 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop9: 14.5 MiB, 15208448 bytes, 29704 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop10: 91 MiB, 95408128 bytes, 186344 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop11: 140.7 MiB, 147496960 bytes, 288080 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop12: 13 MiB, 13619200 bytes, 26600 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop13: 143.5 MiB, 150470656 bytes, 293888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop14: 140.7 MiB, 147496960 bytes, 288080 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop15: 34.6 MiB, 36216832 bytes, 70736 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop16: 53.7 MiB, 56315904 bytes, 109992 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      The Specs of the System: MSI Z97I-AC Motherboard, Intel Pentium G3258, 16GB RAM, GTX 960










      share|improve this question














      I installed Ubuntu 18.04.2 a few days ago. It's installed on a 250GB SSD and I also have a RAID0 that I configured through the Intel Rapid Storage BIOS with two 2TB Enterprise drives. Now for some reason the 2 drives show up as sdb and sdc but also the 4TB RAID Volume shows up and I can use it. GParted gives me 2 Errors every time I start it and under fdisk -l there are 16 loop devices. I mean it works but it seems very weird and although a RAID0 is more or less risky anyway I don't want to loose the data only because something is configured wrong.
      Is there something I can do to fix this?



      The two GParted Errors:



      The first error message is german and roughly says "The argument is invalid, while /dev/sdb is positioned to read from"



      First Error



      Second Error



      Output of fdisk -l



      Disk /dev/loop0: 3.7 MiB, 3821568 bytes, 7464 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop1: 4 MiB, 4218880 bytes, 8240 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop2: 3.7 MiB, 3878912 bytes, 7576 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop3: 2.3 MiB, 2355200 bytes, 4600 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop4: 1008 KiB, 1032192 bytes, 2016 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop5: 89.3 MiB, 93581312 bytes, 182776 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop6: 35.3 MiB, 37027840 bytes, 72320 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop7: 202.3 MiB, 212099072 bytes, 414256 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier: EDD8F944-9636-4398-9E93-9279DFA5F3B7

      Device Start End Sectors Size Type
      /dev/sda1 2048 1050623 1048576 512M EFI System
      /dev/sda2 1050624 500117503 499066880 238G Linux filesystem


      Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x00000000

      Device Boot Start End Sectors Size Id Type
      /dev/sdb1 1 4294967295 4294967295 2T ee GPT


      Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/mapper/isw_fffhhebch_Volume1_RAID0: 3.7 TiB, 4000792707072 bytes, 7814048256 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 131072 bytes / 262144 bytes
      Disklabel type: gpt
      Disk identifier: 7059BA95-67D0-4AFC-98AA-6F192E03E2E3

      Device Start End Sectors Size Type
      /dev/mapper/isw_fffhhebch_Volume1_RAID0p1 2048 7814047743 7814045696 3.7T Linu


      Disk /dev/loop8: 14.8 MiB, 15462400 bytes, 30200 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop9: 14.5 MiB, 15208448 bytes, 29704 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop10: 91 MiB, 95408128 bytes, 186344 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop11: 140.7 MiB, 147496960 bytes, 288080 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop12: 13 MiB, 13619200 bytes, 26600 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop13: 143.5 MiB, 150470656 bytes, 293888 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop14: 140.7 MiB, 147496960 bytes, 288080 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop15: 34.6 MiB, 36216832 bytes, 70736 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      Disk /dev/loop16: 53.7 MiB, 56315904 bytes, 109992 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes


      The Specs of the System: MSI Z97I-AC Motherboard, Intel Pentium G3258, 16GB RAM, GTX 960







      partitioning hard-drive raid loop-device






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 14 at 14:17









      MarcoMarco

      12




      12




















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133821%2fubuntu-18-04-2-raid-problems%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133821%2fubuntu-18-04-2-raid-problems%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Tamil (spriik) Luke uk diar | Nawigatjuun

          Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

          Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?