Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The top part looked ok but the bottom looks like raid.
md: bind<sda>
md: bind<sda>
md/raid0:md126:looking at sda
md/raid0:md126: comapring sda (60287232 with sda (0287232)
This is exactly double the size its rated at. Its an mlc does that mean its actually a raided memmory drive???
Shows that you do not have any partitions defined, so sda2 does not exist yet. You would first need to partition the drive using a tool such as fdisk, cfdisk, or sfdisk. You should then be able to apply a file system to your partition.
Shows that you do not have any partitions defined, so sda2 does not exist yet. You would first need to partition the drive using a tool such as fdisk, cfdisk, or sfdisk. You should then be able to apply a file system to your partition.
Regards,
Fordeck
Sorry, I was changing things around because it wasnt working and I cleared my partition tables before I ran fdisk -l /dev/sda.(the tables were set the first time I tried)
Now everything shows up but I'm still back to my problem.
Check what partition type you have assigned to your partition types on /dev/sda Or perhaps you can post the output of the current fdisk -l. It sounds like you may left over superblock metadata from having set it up as a raid device at some point.
The partition type you want would be 83/Linux. Partition type fd/Linux raid auto would be what you use only if you want to setup software raid.
Check what partition type you have assigned to your partition types on /dev/sda Or perhaps you can post the output of the current fdisk -l. It sounds like you may left over superblock metadata from having set it up as a raid device at some point.
The partition type you want would be 83/Linux. Partition type fd/Linux raid auto would be what you use only if you want to setup software raid.
Regards,
Fordeck
Thank you very much for your advice.
It was a new drive and the first pc I put it in was my Gentoo pc.
However, I decided to use it in my Windows 7 pc instead and setup a large raid on my gentoo pc in order to make a server.
I was, however, able to get it working by turning off software raid on gentoo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
