Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't recognize my raid5 array #9

Open
harvey-git opened this issue Aug 14, 2021 · 4 comments
Open

Can't recognize my raid5 array #9

harvey-git opened this issue Aug 14, 2021 · 4 comments

Comments

@harvey-git
Copy link

harvey-git commented Aug 14, 2021

Array information:
480G SanDisk sata ssd x3
Each ssd has only one partition, which is aligned from 8mb-100% sectors;
Then build raid5 to /dev/md0 in mdadm with sda1, sdb1, sdc1, and then formatted md0 as btrfs. It works well under ubuntu. I have restored the previous 300g game data from the backup, and the speed of btrfs scrub is Stable at 1.1g per second.
However, under win11, even if winmd and winbtrfs are installed, any md volume will not appear.
I have tried to change the gpt partition ID of sd[a-c]1 to 0700, fd00, and 8300, but there is no change except that 0700 will cause three unformatted drive letters.
In fact, before using three ssd as raid5, I used sda2 and sdb2 in two of them to make raid1 with mdadm, but the ntfs formatted at that time can be recognized and used under win10, the 300g game The data is backed up from the ntfs volume of the md of this raid1.

@FluorescentGreen5
Copy link

I find that WinMD doesn't support raided partitions and only works with entire raided disks.

@maharmstone
Copy link
Owner

@FluorescentGreen5 - it's been a while since I wrote it, but my recollection is that the opposite is true.

@mark0n
Copy link

mark0n commented Jun 14, 2022

I'm running into similar problems. I built master, signed and installed successfully. On Linux I created a RAID-0 using the following commands:

sudo mdadm --create /dev/md0 --auto md --level=0 --raid-devices=2 /dev/sdf /dev/sdg
sudo mkfs.exfat /dev/md0

For starters I used a Windows filesystem to avoid problems with the filesystem (I'm planning to try Linux filesystems once I get WinMD working). I verified the superblock is compatible with WinMD by running

sudo mdadm --detail /dev/md0

After connecting the two disks to my Windows machine I don't see the WinMD driver loaded for them in device manager:
image

I also tried creating a GPT partition table with one partition on each disk and using these to create the RAID-0:

$ sudo parted /dev/sda
GNU Parted 3.4
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel GPT
(parted) mkpart primary 65535s 100%
(parted) align-check optimal 1
1 aligned
(parted) q
Information: You may need to update /etc/fstab.

$ sudo sgdisk -t 1:fd00 /dev/sda

Rinse and repeat for /dev/sdb, then create the RAID and the file system:

$ sudo mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sda1 /dev/sdb1
$ sudo mkfs.vfat /dev/md0

No luck either. Am I missing something?

@mark0n
Copy link

mark0n commented Jun 27, 2022

I noticed that when I download the binary package everything works fine but when I build the driver ("v0.1" tag) from source it installs happily but doesn't seem to load (disk created as described above). I opened #11 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants