Type: Posts; User: CooLGeeK; Keyword(s):

Search: Search took 0.01 seconds.

  1. Replies

    [ubuntu] Re: Fresh Install - getting raid back

    Yes, you're are probably right that you can spot the problem from:

    What this means is that mdadm found an md superblock on the disk itself (i.e. /dev/sdb and /dev/sdc) aside from the raid...
  2. Replies

    [all variants] Re: /dev/sdc1 is not created

    I had a similar problem before.
    The problem started when I created a new array using disks or linux raid partitions from an old (and should have been deleted) raid array.

    I discovered that an md...
  3. Replies

    [ubuntu] Re: delete mdadm volume info from disk

    By default, mdadm automatically scans disk partitions if they contain md superblocks and then continues to assemble raid arrays based on the info gathered.
    Configuration file: /etc/mdadm/mdadm.conf...
  4. [ubuntu] Re: Software RAID (mdadm) problems after updates

    Ok guys, I figured out why there are missing device nodes OR device file (i.e. no /dev/sdb1 even if /dev/sdb exists and there is a partition inside it) pertaining to my Linux raid partitions...
  5. [all variants] Re: Moving Raid Archive - fsck died with exit status 8

    Can you try checking each partition if they are part of a RAID array?
    For example, checking partition /dev/sdc1 ...

    sudo mdadm --examine /dev/sdc1

    Try doing the check for all your partitions....
  6. Replies

    [all variants] Re: Samba file access problem

    Is there any permission difference between the two (2) folders?

    I solved some of my Samba problems just by setting the right permission.
    Don't know if it will help you.
  7. [ubuntu] Software RAID (mdadm) problems after updates

    I just wanted to share my experience in case somebody encounters the same problems I had to face.

    I created a RAID 5 array with 3 devices.
    (/dev/md0 is composed of /dev/sdb1 /dev/sdc1 and...
  8. [all variants] Re: Moving Raid Archive - fsck died with exit status 8

    Looking at the logs /dev/md0 seems to be mounted (to a directory).
    Check /etc/mtab to be sure.
    Unmount it (sudo umount /dev/md0) and run fsck again (sudo fsck /dev/md0).
  9. [ubuntu] Re: mdadm RAID 5 - is there something wrong here?

    Looking at the output of: sudo mdadm --detail /dev/md0 you will see the lines:

    Raid Devices : 5
    Total Devices : 4

    This means that your RAID device is a RAID 5 type.
    Unfortunately one of...
Results 1 to 9 of 9