LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 01-04-2007, 02:07 AM   #16
moaimullet
LQ Newbie
 
Registered: Jan 2007
Posts: 7

Rep: Reputation: 0

This is an old topic, so I hope this info will get to someone who needs it.. please copy this info somewhere else if it's helpful to you!

Last week I bought 4 cheap 320GB SATA II Seagates to build a RAID 5. Have done much reading of random HOWTOs, most seemingly from last year or older, but finally it looks like I have a software (NOT fakeraid) RAID 5 setup that can be seen in both Ubuntu and Windows XP Pro. This info should work for any other distro that contains the LDM (MS Windows Logical Disk Management) driver to read MS Dynamic Disks. Since kernel version >= 2.5.?? afaik, this driver should be somewhere in the kernel source, so even if it is not enabled by default, you can add it if you build your own kernel.

Note that you'll have to do the Toms Hardware XP Pro hex edits to be able to set up RAID 5 in XP: (http://www.tomshardware.com/2004/11/...raid_5_happen/)


So, here's what I've done and where I am so far:

1. Plugged in the HDDs. My mobo is an Asus A8R32-MVP, so the controller is an ULi model.. can't remember which, but it's not important. This controller isn't supported by dmraid, and I have disabled it in BIOS anyway (I am doing pure software RAID).

2. Booted from Ubuntu 6.10 Desktop CD and installed Ubuntu to the 4th HDD (will be a spare for the RAID, when I'm done). In retrospect, another distro may be more useful, but this is what I had been playing with lately.

3. Made some identical partitions on the first 3 HDDs, similar to how it is explained in the following link, but with different partitions/sizes. The important thing is that I let XP have the first partition on the first disk (/dev/sda1). Windows isn't happy unless it is first. Since the other primary partition(s) are unused, I'll use /dev/sdb1 and /dev/sdc1 to play with distros I haven't tried yet. You could use them for anything else though. (http://www.overclock3d.net/articles....dows_and_linux)

4. Booted back into Windows, and kept going with the guide linked above. I deleted the partitions meant to be used *within* windows (partitions 4, 5, and 6, on the first 3 HDDs), and created the first RAID 5 volume (partition 4 on each). I didn't touch the partitions I'll be using in linux (2 and 3). For me, I will be moving the "Program Files" and "Documents And Settings" windows folders to the first such volume, so it is 120GB. It will be striped across /dev/sda4, sdb4, and sdc4. It took so long for XP to 'create' this volume that I moved on to the next step before creating the rest, just to see if it would work. /sdx2 and /sdx3 are going to be my RAIDed linux volumes, and sdx1 will not be part of the RAID as mentioned above.

5. Booted into Ubuntu, and even though the kernel could see the LDM info (try "dmesg | less" and then search ("/") for "LDM"), both gparted and fdisk reported only one big unrecognized volume for /dev/sda2, and all of /dev/sdb and /dev/sdc. The fact that the partitions were seen by the kernel was a hopeful sign, though, so I went on to try the following commands:

A. I didn't have any /dev/mdX block devices, so I created some:
sudo mknod /dev/md0 b 9 0
sudo mknod /dev/md1 b 9 1
sudo mknod /dev/md2 b 9 2
That's enough for me to create the 2 linux RAID 5 stripes and the first Windows stripe for testing.. though I still need to make md3 and md4 when I'm ready.

B. Create the linux arrays. YMMV on the chunk sizes. If this works, then try making the one for the NTFS stripe:
sudo mdadm --create /dev/md0 --chunk=16 --level=5 --raid-devices=3 /dev/sda2 /dev/sdb2 /dev/sdc2
sudo mdadm --create /dev/md1 --chunk=32 --level=5 --raid-devices=3 /dev/sda3 /dev/sdb3 /dev/sdc3

C. The linux stripes need to be formatted:
mke2fs -j -L number_one /dev/md0
mke2fs -j -L the_larch /dev/md1

D. Mount each of them in turn to double-check the size. They should be (numberOfDrives - 1) * sizeOfPartitionOnEach.
mount /dev/md0 /media/extra
mount /dev/md1 /media/extra2
df -k
Filesystem 1K-blocks Used Available Use% Mounted on
...
/dev/md0 1011800 17672 942732 2% /media/extra
...
/dev/md1 20160892 176288 18960476 1% /media/extra2


So far so good! If you do a "cat /proc/mdstat" at this point, you may see that the RAID stripes are being 'recovered'. This is pretty meaningless since they have just now been created.. so, now we have some confidence to try accessing the NTFS stripe:


6. The Windows NTFS stripe doesn't need to be formatted, as long as you made it in Windows. Here is what it looked like for me, when I ran through all of the above steps:

root@iddqd:/usr/src/linux# mknod /dev/md2 b 9 2
root@iddqd:/usr/src/linux# mdadm --create /dev/md2 --chunk=64 --level=5 --raid-devices=3 /dev/sda4 /dev/sdb4 /dev/sdc4
mdadm: array /dev/md2 started.
root@iddqd:/usr/src/linux# mount -t ntfs /dev/md2 /media/extra
root@iddqd:/usr/src/linux# ls -al /media/extra
total 36
dr-x------ 1 root root 4096 2007-01-01 04:29 .
drwxr-xr-x 8 root root 4096 2006-12-31 19:24 ..
dr-x------ 1 root root 0 2007-01-01 04:29 System Volume Information
root@iddqd:/usr/src/linux# umount /media/extra
root@iddqd:/usr/src/linux# cat /proc/mdstat
Personalities : [raid1] [raid10] [raid5] [raid4]
md2 : active raid5 sdc4[3] sdb4[1] sda4[0]
163846016 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_]
[=>...................] recovery = 6.6% (5458432/81923008) finish=15.7min speed=80909K/sec

md1 : active raid5 sdc3[2] sdb3[1] sda3[0]
20482560 blocks level 5, 32k chunk, algorithm 2 [3/3] [UUU]

md0 : active raid5 sdc2[2] sdb2[1] sda2[0]
1027968 blocks level 5, 16k chunk, algorithm 2 [3/3] [UUU]

unused devices: <none>


As you can see, the NTFS volume is now also being recovered. Since I had no data on the drive, I can't say whether anything would have been destroyed by this process-- however, I can say that when I let it finish, and rebooted back into Windows, there was no problem accessing it. In other words, although mdadm felt the need to rebuild the NTFS stripe, XP Pro didn't complain when it was done.


Since this time, I have downloaded the 2.6.19 kernel to the NTFS Windows RAID and unpacked it here in Ubuntu. Working great as far as I can tell.

-- Teague
 
Old 01-07-2007, 12:05 AM   #17
moaimullet
LQ Newbie
 
Registered: Jan 2007
Posts: 7

Rep: Reputation: 0
So I have since initialized the 2nd RAID 5 partition in Windows, which is around 75 GB in size all told. Obviously the shortcoming above is that I didn't know whether existing data would be corrupted.

After Windows finished formatting and recovering the stripe, I copied ~50 GB of data onto it, then booted back into Ubuntu. Went through the process of adding the stripe to mdadm, starting from mknod and letting it recover the array like it did with the first RAID 5 stripe. When it finished, I dug around the volume and could find no change to the data.. couldn't find any corruption or change from what it was before.

Rebooted back into Windows, and it didn't even know that Ubuntu had done its own "recovery". I suppose what mdadm calls "recovery" is mostly just verification of the parity (which would account for the speed with which it finished). And that makes sense, if you don't read too much into the actual wording it uses.

I gotta say, though, that I still wish I had the $$ for a pure hardware RAID.. sigh..
 
Old 01-08-2007, 05:01 PM   #18
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
Hey "michaelsanford",

Thanks a bunch for the info on setting up a software raid0 as the boot device! You provided the missing bits of info I needed, and after maybe 20 minutes of struggling with Debian Etch installer's partitioning section, it looks like I'm successful! I still have to finish the installation and hope it boots, but it looks like it's installing to the raid.

Errr, looks like you can install to a SW raid0 but you can't actually use it as a boot device. Oh well, nothing ventured...

Last edited by Quakeboy02; 01-08-2007 at 08:37 PM.
 
Old 04-07-2007, 09:29 PM   #19
fanqi1234
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Rep: Reputation: 0
I have the same problem BUT mkfs will destory my data in /dev/md0
I want to keep them safe

Help me
 
Old 04-07-2007, 10:13 PM   #20
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
"I have the same problem BUT mkfs will destory my data in /dev/md0 "

Did you do an install, or do you just have data on a RAID0? If you did an install and it won't boot, do you have any space on one of the drives that's not part of the array? If you do, then put your /boot directory on that and make the appropriate changes to grub. It should boot after that. I'm afraid that I don't really know how to move a OS to a data drive and make it bootable. I suppose it could be done, but it would be chancy.
 
Old 04-07-2007, 11:35 PM   #21
Electro
Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
In order to boot from a software RAID, grub's files have to be on another partition that is not part of the software RAID array. Also initrd file have to load the require modules, if there are any, in order for software RAID to work or be detected by Linux. Grub does not have dmraid or software RAID capabilities yet. Soon it should and the complexity of the setup will be easier. RAID 0 really should not be used for the OS because it increases the chances that are equal to the amount of disks. RAID 0 will not speed up loading programs. RAID 1 will speed up programs because the array has copies that can cut down accessing times in half or more.

fanqi1234, if you put data on one of the partitions that is part of the array. There is a good possibility that mdadm may have trash your data. If you did not do this but you wrote files to one of the /dev/md device nodes, can get the data back if you use use dd to make an image of the drive. You will have to use a hard drive that is bigger than the array. /dev/mdX have to be formated before you use it for storing data. I recommend after you format it, place a test file and reboot the computer. If the file is there after you reboot, there is agood possibility that any data you place there should always be there every time you boot up the computer.

moaimullet, you could have just buy a hardware controller to make it very, very easy for yourself. Probably there are some files on the NTFS partition that are corrupt. Lucky for you they were not system based and they did not have obscured permissions. RAID 5 needs a lot of processor resources for I/O transactions. However, you may have even higher chance of data corruption or data loss, so I suggest backing up your data.

I would not do it your way because the reliability and stability have to go both ways for good operation. I know Linux is reliable and stable, but Windows is never reliable and stable. I rather pick being in debt for several months after buying a hardware RAID controller like from 3ware instead of doing it your way.

Note:
Using SCSI or SATA hard drives in a software RAID can change from one device node and to the next node. You may have to set the ID or use software labels to make it predictable upon boot up.

BTW, I have not yet setup RAID, but I studied the documentation at every angle.
 
Old 04-08-2007, 01:15 AM   #22
fanqi1234
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Rep: Reputation: 0
in FC6 I created /dev/md0 (raid0 ,hda7 + hdb3) to save some files
yesterday I installed openSUSE10.2 to replace FC6(/dev/hda6)

now,all my backup files is in the /dev/md0
I want /dev/md0 run just like it in FC6 with old data in it.


-*-
ps:I can't speak English well .I hope you can understand me.

Last edited by fanqi1234; 04-08-2007 at 01:16 AM.
 
Old 04-08-2007, 01:05 PM   #23
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
Quote:
Electro says: Grub does not have dmraid or software RAID capabilities yet.
Sorry, but you're wrong on this one. My test mule boots just fine into a dmraid on a FastTrak66 that does not have a separate boot partition. OTOH, with mdadm, you do need a separate boot partition.

Quote:
Electro again: BTW, I have not yet setup RAID, but I studied the documentation at every angle.
You are a very bright guy. But, without using these things, it's easy to get it wrong.
 
Old 04-08-2007, 01:19 PM   #24
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
Quote:
in FC6 I created /dev/md0 (raid0 ,hda7 + hdb3) to save some files
yesterday I installed openSUSE10.2 to replace FC6(/dev/hda6)

now,all my backup files is in the /dev/md0
I want /dev/md0 run just like it in FC6 with old data in it.
Quick summary of my understanding. You had FC6 installed on /dev/hda6. You had (and still have) a RAID0 installed to /dev/hda7 and /dev/hdb3. You have just installed openSUSE10.2 to /dev/hda6 and you have lost access to your array. Is that a correct summary?

Assuming this is correct, your data is still there but your installation destroyed your mdadm.conf. Don't panic! You will first need to verify that you have mdadm installed to SUSE. If you don't, install it. Then, do you remember how you created your array? DON'T DO THAT!!! However, you need to do something similar. What you need to do is run the mdadm command using the --assemble option to reassemble the array on your new operating system. Your command will look something like the following:
Code:
mdadm --assemble /dev/md0 --level=0 --raid-devices=2 /dev/hda7 /dev/hdb3
If this properly reassembles your raid, then you will need to recreate the mdadm.conf file as follows:
Code:
echo 'DEVICE /dev/hda7 /dev/hdb3' > mdadm.conf
mdadm --detail --scan >> mdadm.conf
Then take a careful look at that mdadm.conf file and if it is correct, then save it to /etc/mdadm.conf.

One additional note. It is possible that mdadm might create a proper mdadm.conf when you install it. Check that first before you run the above commands.

Last edited by Quakeboy02; 04-08-2007 at 04:49 PM.
 
Old 04-09-2007, 06:29 AM   #25
fanqi1234
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Rep: Reputation: 0
Quakeboy02,you have a good understanding.


now the array is running ok (I think)
but "mount" says "wrong fs type"


SUSE :
Code:
fans:~ # mdadm -D /dev/md1
/dev/md1:
        Version : 00.90.03
  Creation Time : Thu Nov 23 22:59:44 2006
     Raid Level : raid0
     Array Size : 27342400 (26.08 GiB 28.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Sun Apr  8 00:49:18 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 64K

           UUID : b9797994:aafe06f3:2e202443:55de9527
         Events : 0.3

    Number   Major   Minor   RaidDevice State
       0       3        7        0      active sync   /dev/hda7
       1       3       67        1      active sync   /dev/hdb3
fans:~ #




and my personal log for FC6:
Code:
# mdadm -D /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Thu Nov 23 22:59:44 2006
     Raid Level : raid0
     Array Size : 27342400 (26.08 GiB 28.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Nov 23 22:59:44 2006
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 64K

           UUID : b9797994:aafe06f3:2e202443:55de9527
         Events : 0.1

    Number   Major   Minor   RaidDevice State
       0       3        8        0      active sync   /dev/hda8
       1       3       67        1      active sync   /dev/hdb3


hda8 now called hda7
(because of some partition change when I was installing SUSE)
(is this a problem?)
 
Old 04-09-2007, 06:41 AM   #26
fanqi1234
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Rep: Reputation: 0
Code:
fans:~ # cat /proc/mdstat 
Personalities : [raid0] 
md0 : active raid0 hda7[0] hdb3[1]
      27342400 blocks 64k chunks
      
unused devices: <none>
Code:
fans:~ # cat /etc/mdadm.conf 
DEVICE /dev/hda* /dev/hdb*
Code:
fans:~ # fdisk -l /dev/hda

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        1942    15599083+   7  HPFS/NTFS
/dev/hda2            1943        5257    26627737+   7  HPFS/NTFS
/dev/hda3            5258       14593    74991420    f  W95 Ext'd (LBA)
/dev/hda5            9240       14593    43005973+   7  HPFS/NTFS
/dev/hda6            7476        7537      497983+  82  Linux swap / Solaris
/dev/hda7            7538        9239    13671283+  fd  Linux raid autodetect
/dev/hda8            5258        6144     7124764+  83  Linux
/dev/hda9            6145        7475    10691226   83  Linux

Partition table entries are not in disk order
Code:
fans:~ # fdisk -l /dev/hdb

Disk /dev/hdb: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1   *           1          36      289138+  82  Linux swap / Solaris
/dev/hdb2              37          98      498015   82  Linux swap / Solaris
/dev/hdb3              99        1800    13671315   fd  Linux raid autodetect
/dev/hdb4            1801        2434     5092605   83  Linux

Code:
fans:~ # mount /dev/md0 /mnt/md0
mount: you must specify the filesystem type
Code:
fans:~ # mount /dev/md0 /mnt/md0 -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/md0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

fans:~ #
 
Old 04-09-2007, 12:56 PM   #27
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
Code:
fans:~ # mount /dev/md0 /mnt/md0 -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/md0,
I think you make a mistake. On your new system, the array is /dev/md1 isn't it? And not /dev/md0? Will it mount if you use /dev/md1?

Also, I believe that you have to run this line in order that you won't have to manually assemble the array when you next boot. I could be wrong, of course.

Code:
mdadm --detail --scan >> /etc/mdadm.conf
Note carefully that there are two right arrows ">>" and not just one so that it appends to the file, and doesn't replace the data in the file.
 
Old 04-09-2007, 02:50 PM   #28
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
While I was playing with software arrays, mdadm started insisting on building some arrays that I hadn't defined as a result of using the generic DEVICE statement like you have. I would change it, if I were you, to have only the devices actually used in the array as follows:
Code:
DEVICE /dev/hda7 /dev/hdb3
Of course, it will also probably need the line generated by the detail scan (see prior post) as well.

Last edited by Quakeboy02; 04-09-2007 at 02:52 PM.
 
Old 04-09-2007, 09:55 PM   #29
fanqi1234
LQ Newbie
 
Registered: Apr 2007
Posts: 8

Rep: Reputation: 0
no ,it's not a mistake. I just -assemble /dev/md1 to try again.

I think array is running, but "mount" says "wrong fs type"

Should I use "fsck.ext3 -y " or "mkfs.ext3 -S" ?


# fsck.ext3 -n /dev/md0 > ./fsck.txt

fsck.txt :
Code:
Couldn't find ext2 superblock, trying backup blocks...
Resize inode not valid.  Recreate? no

/dev/md0 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 7, i_blocks is 89944, should be 88184.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #1 (29650, counted=0).
Fix? no

Free blocks count wrong for group #2 (32254, counted=0).
Fix? no

Free blocks count wrong for group #3 (31229, counted=0).
Fix? no

Free blocks count wrong for group #4 (32254, counted=2).
Fix? no

Free blocks count wrong for group #5 (31229, counted=0).
Fix? no

Free blocks count wrong for group #6 (32254, counted=2).
Fix? no

Free blocks count wrong for group #7 (31229, counted=4).
Fix? no

Free blocks count wrong for group #8 (32254, counted=3).
Fix? no

Free blocks count wrong for group #9 (31229, counted=0).
Fix? no

Free blocks count wrong for group #10 (32254, counted=0).
Fix? no

Free blocks count wrong for group #11 (32254, counted=0).
Fix? no

Free blocks count wrong for group #12 (32254, counted=0).
Fix? no

Free blocks count wrong for group #13 (32254, counted=1).
Fix? no

Free blocks count wrong for group #14 (32254, counted=0).
Fix? no

Free blocks count wrong for group #15 (32254, counted=5583).
Fix? no

Free blocks count wrong for group #16 (32254, counted=0).
Fix? no

Free blocks count wrong for group #17 (32254, counted=0).
Fix? no

Free blocks count wrong for group #18 (32254, counted=0).
Fix? no

Free blocks count wrong for group #19 (32254, counted=0).
Fix? no

Free blocks count wrong for group #20 (32254, counted=0).
Fix? no

Free blocks count wrong for group #21 (32254, counted=0).
Fix? no

Free blocks count wrong for group #22 (32254, counted=0).
Fix? no

Free blocks count wrong for group #23 (32254, counted=0).
Fix? no

Free blocks count wrong for group #24 (32254, counted=0).
Fix? no

Free blocks count wrong for group #25 (31229, counted=0).
Fix? no

Free blocks count wrong for group #26 (32254, counted=0).
Fix? no

Free blocks count wrong for group #27 (31229, counted=0).
Fix? no

Free blocks count wrong for group #28 (32254, counted=0).
Fix? no

Free blocks count wrong for group #29 (32254, counted=0).
Fix? no

Free blocks count wrong for group #30 (32254, counted=0).
Fix? no

Free blocks count wrong for group #31 (32254, counted=0).
Fix? no

Free blocks count wrong for group #32 (32254, counted=0).
Fix? no

Free blocks count wrong for group #33 (32254, counted=0).
Fix? no

Free blocks count wrong for group #34 (32254, counted=0).
Fix? no

Free blocks count wrong for group #35 (32254, counted=0).
Fix? no

Free blocks count wrong for group #36 (32254, counted=0).
Fix? no

Free blocks count wrong for group #37 (32254, counted=0).
Fix? no

Free blocks count wrong for group #38 (32254, counted=0).
Fix? no

Free blocks count wrong for group #39 (32254, counted=0).
Fix? no

Free blocks count wrong for group #40 (32254, counted=0).
Fix? no

Free blocks count wrong for group #41 (32254, counted=0).
Fix? no

Free blocks count wrong for group #42 (32254, counted=0).
Fix? no

Free blocks count wrong for group #43 (32254, counted=0).
Fix? no

Free blocks count wrong for group #44 (32254, counted=0).
Fix? no

Free blocks count wrong for group #45 (32254, counted=0).
Fix? no

Free blocks count wrong for group #46 (32254, counted=0).
Fix? no

Free blocks count wrong for group #47 (32254, counted=0).
Fix? no

Free blocks count wrong for group #48 (32254, counted=0).
Fix? no

Free blocks count wrong for group #49 (31229, counted=0).
Fix? no

Free blocks count wrong for group #50 (32254, counted=0).
Fix? no

Free blocks count wrong for group #51 (32254, counted=0).
Fix? no

Free blocks count wrong for group #52 (32254, counted=0).
Fix? no

Free blocks count wrong for group #53 (32254, counted=0).
Fix? no

Free blocks count wrong for group #54 (32254, counted=0).
Fix? no

Free blocks count wrong for group #55 (32254, counted=0).
Fix? no

Free blocks count wrong for group #56 (32254, counted=0).
Fix? no

Free blocks count wrong for group #57 (32254, counted=0).
Fix? no

Free blocks count wrong for group #58 (32254, counted=0).
Fix? no

Free blocks count wrong for group #59 (32254, counted=0).
Fix? no

Free blocks count wrong for group #60 (32254, counted=0).
Fix? no

Free blocks count wrong for group #61 (32254, counted=0).
Fix? no

Free blocks count wrong for group #62 (32254, counted=0).
Fix? no

Free blocks count wrong for group #63 (32254, counted=0).
Fix? no

Free blocks count wrong for group #64 (32254, counted=0).
Fix? no

Free blocks count wrong for group #65 (32254, counted=0).
Fix? no

Free blocks count wrong for group #66 (32254, counted=0).
Fix? no

Free blocks count wrong for group #67 (32254, counted=0).
Fix? no

Free blocks count wrong for group #68 (32254, counted=0).
Fix? no

Free blocks count wrong for group #69 (32254, counted=0).
Fix? no

Free blocks count wrong for group #70 (32254, counted=0).
Fix? no

Free blocks count wrong for group #71 (32254, counted=17212).
Fix? no

Free blocks count wrong for group #72 (32254, counted=17463).
Fix? no

Free blocks count wrong for group #73 (32254, counted=28561).
Fix? no

Free blocks count wrong for group #74 (32254, counted=8153).
Fix? no

Free blocks count wrong for group #75 (32254, counted=26451).
Fix? no

Free blocks count wrong for group #76 (32254, counted=14418).
Fix? no

Free blocks count wrong for group #77 (32254, counted=14928).
Fix? no

Free blocks count wrong for group #78 (32254, counted=12429).
Fix? no

Free blocks count wrong for group #79 (32254, counted=18435).
Fix? no

Free blocks count wrong for group #80 (32254, counted=21523).
Fix? no

Free blocks count wrong for group #81 (31229, counted=15887).
Fix? no

Free blocks count wrong for group #82 (32254, counted=9941).
Fix? no

Free blocks count wrong for group #83 (32254, counted=17835).
Fix? no

Free blocks count wrong for group #84 (32254, counted=10916).
Fix? no

Free blocks count wrong for group #85 (32254, counted=11957).
Fix? no

Free blocks count wrong for group #86 (32254, counted=11708).
Fix? no

Free blocks count wrong for group #87 (32254, counted=10508).
Fix? no

Free blocks count wrong for group #88 (32254, counted=3247).
Fix? no

Free blocks count wrong for group #89 (32254, counted=13080).
Fix? no

Free blocks count wrong for group #90 (32254, counted=0).
Fix? no

Free blocks count wrong for group #91 (32254, counted=1).
Fix? no

Free blocks count wrong for group #92 (32254, counted=0).
Fix? no

Free blocks count wrong for group #93 (32254, counted=0).
Fix? no

Free blocks count wrong for group #94 (32254, counted=1).
Fix? no

Free blocks count wrong for group #95 (32254, counted=0).
Fix? no

Free blocks count wrong for group #96 (32254, counted=0).
Fix? no

Free blocks count wrong for group #97 (32254, counted=1).
Fix? no

Free blocks count wrong for group #98 (32254, counted=0).
Fix? no

Free blocks count wrong for group #99 (32254, counted=0).
Fix? no

Free blocks count wrong for group #100 (32254, counted=0).
Fix? no

Free blocks count wrong for group #101 (32254, counted=9990).
Fix? no

Free blocks count wrong for group #102 (32254, counted=11396).
Fix? no

Free blocks count wrong for group #103 (32254, counted=13674).
Fix? no

Free blocks count wrong for group #104 (32254, counted=17815).
Fix? no

Free blocks count wrong for group #105 (32254, counted=16617).
Fix? no

Free blocks count wrong for group #106 (32254, counted=0).
Fix? no

Free blocks count wrong for group #107 (32254, counted=20000).
Fix? no

Free blocks count wrong for group #108 (32254, counted=25045).
Fix? no

Free blocks count wrong for group #109 (32254, counted=22451).
Fix? no

Free blocks count wrong for group #110 (32254, counted=23833).
Fix? no

Free blocks count wrong for group #111 (32254, counted=21397).
Fix? no

Free blocks count wrong for group #112 (32254, counted=17972).
Fix? no

Free blocks count wrong for group #113 (32254, counted=12716).
Fix? no

Free blocks count wrong for group #114 (32254, counted=4217).
Fix? no

Free blocks count wrong for group #115 (32254, counted=449).
Fix? no

Free blocks count wrong for group #116 (32254, counted=0).
Fix? no

Free blocks count wrong for group #117 (32254, counted=4706).
Fix? no

Free blocks count wrong for group #118 (32254, counted=3966).
Fix? no

Free blocks count wrong for group #119 (32254, counted=0).
Fix? no

Free blocks count wrong for group #120 (32254, counted=4).
Fix? no

Free blocks count wrong for group #121 (32254, counted=0).
Fix? no

Free blocks count wrong for group #122 (32254, counted=0).
Fix? no

Free blocks count wrong for group #123 (32254, counted=0).
Fix? no

Free blocks count wrong for group #124 (32254, counted=0).
Fix? no

Free blocks count wrong for group #125 (31229, counted=0).
Fix? no

Free blocks count wrong for group #126 (32254, counted=0).
Fix? no

Free blocks count wrong for group #127 (32254, counted=3).
Fix? no

Free blocks count wrong for group #128 (32254, counted=1326).
Fix? no

Free blocks count wrong for group #129 (32254, counted=3208).
Fix? no

Free blocks count wrong for group #130 (32254, counted=14078).
Fix? no

Free blocks count wrong for group #131 (32254, counted=22093).
Fix? no

Free blocks count wrong for group #132 (32254, counted=25066).
Fix? no

Free blocks count wrong for group #133 (32254, counted=8988).
Fix? no

Free blocks count wrong for group #134 (32254, counted=12452).
Fix? no

Free blocks count wrong for group #135 (32254, counted=14663).
Fix? no

Free blocks count wrong for group #136 (32254, counted=19517).
Fix? no

Free blocks count wrong for group #137 (32254, counted=21958).
Fix? no

Free blocks count wrong for group #138 (32254, counted=19716).
Fix? no

Free blocks count wrong for group #139 (32254, counted=15474).
Fix? no

Free blocks count wrong for group #140 (32254, counted=10005).
Fix? no

Free blocks count wrong for group #141 (32254, counted=2483).
Fix? no

Free blocks count wrong for group #142 (32254, counted=5409).
Fix? no

Free blocks count wrong for group #143 (32254, counted=1615).
Fix? no

Free blocks count wrong for group #144 (32254, counted=1670).
Fix? no

Free blocks count wrong for group #145 (32254, counted=6011).
Fix? no

Free blocks count wrong for group #146 (32254, counted=14941).
Fix? no

Free blocks count wrong for group #147 (32254, counted=3535).
Fix? no

Free blocks count wrong for group #148 (32254, counted=197).
Fix? no

Free blocks count wrong for group #149 (32254, counted=2085).
Fix? no

Free blocks count wrong for group #150 (32254, counted=5577).
Fix? no

Free blocks count wrong for group #151 (32254, counted=13581).
Fix? no

Free blocks count wrong for group #152 (32254, counted=7882).
Fix? no

Free blocks count wrong for group #153 (32254, counted=1739).
Fix? no

Free blocks count wrong for group #154 (32254, counted=5413).
Fix? no

Free blocks count wrong for group #155 (32254, counted=3729).
Fix? no

Free blocks count wrong for group #156 (32254, counted=8997).
Fix? no

Free blocks count wrong for group #157 (32254, counted=1403).
Fix? no

Free blocks count wrong for group #158 (32254, counted=8037).
Fix? no

Free blocks count wrong for group #159 (32254, counted=5294).
Fix? no

Free blocks count wrong for group #160 (32254, counted=5697).
Fix? no

Free blocks count wrong for group #161 (32254, counted=4927).
Fix? no

Free blocks count wrong for group #162 (32254, counted=15906).
Fix? no

Free blocks count wrong for group #163 (32254, counted=4509).
Fix? no

Free blocks count wrong for group #164 (32254, counted=8935).
Fix? no

Free blocks count wrong for group #165 (32254, counted=11659).
Fix? no

Free blocks count wrong for group #166 (32254, counted=1911).
Fix? no

Free blocks count wrong for group #167 (32254, counted=0).
Fix? no

Free blocks count wrong for group #168 (32254, counted=0).
Fix? no

Free blocks count wrong for group #169 (32254, counted=0).
Fix? no

Free blocks count wrong for group #170 (32254, counted=3).
Fix? no

Free blocks count wrong for group #171 (32254, counted=4).
Fix? no

Free blocks count wrong for group #172 (32254, counted=3).
Fix? no

Free blocks count wrong for group #173 (32254, counted=0).
Fix? no

Free blocks count wrong for group #174 (32254, counted=3).
Fix? no

Free blocks count wrong for group #175 (32254, counted=3).
Fix? no

Free blocks count wrong for group #176 (32254, counted=1).
Fix? no

Free blocks count wrong for group #177 (32254, counted=0).
Fix? no

Free blocks count wrong for group #178 (32254, counted=0).
Fix? no

Free blocks count wrong for group #179 (32254, counted=0).
Fix? no

Free blocks count wrong for group #180 (32254, counted=0).
Fix? no

Free blocks count wrong for group #181 (32254, counted=0).
Fix? no

Free blocks count wrong for group #182 (32254, counted=0).
Fix? no

Free blocks count wrong for group #183 (32254, counted=0).
Fix? no

Free blocks count wrong for group #184 (32254, counted=0).
Fix? no

Free blocks count wrong for group #185 (32254, counted=0).
Fix? no

Free blocks count wrong for group #186 (32254, counted=0).
Fix? no

Free blocks count wrong for group #187 (32254, counted=0).
Fix? no

Free blocks count wrong for group #188 (32254, counted=0).
Fix? no

Free blocks count wrong for group #189 (32254, counted=0).
Fix? no

Free blocks count wrong for group #190 (32254, counted=0).
Fix? no

Free blocks count wrong for group #191 (32254, counted=0).
Fix? no

Free blocks count wrong for group #192 (32254, counted=4).
Fix? no

Free blocks count wrong for group #193 (32254, counted=0).
Fix? no

Free blocks count wrong for group #194 (32254, counted=4164).
Fix? no

Free blocks count wrong for group #195 (32254, counted=2355).
Fix? no

Free blocks count wrong for group #196 (32254, counted=0).
Fix? no

Free blocks count wrong for group #197 (32254, counted=0).
Fix? no

Free blocks count wrong for group #198 (32254, counted=0).
Fix? no

Free blocks count wrong for group #199 (32254, counted=0).
Fix? no

Free blocks count wrong for group #200 (32254, counted=4).
Fix? no

Free blocks count wrong for group #201 (32254, counted=3).
Fix? no

Free blocks count wrong for group #202 (32254, counted=4).
Fix? no

Free blocks count wrong for group #203 (32254, counted=4).
Fix? no

Free blocks count wrong for group #204 (32254, counted=0).
Fix? no

Free blocks count wrong for group #205 (32254, counted=0).
Fix? no

Free blocks count wrong for group #206 (32254, counted=0).
Fix? no

Free blocks count wrong for group #207 (32254, counted=0).
Fix? no

Free blocks count wrong for group #208 (19342, counted=0).
Fix? no

Free blocks count wrong (6684091, counted=864742).
Fix? no

Free inodes count wrong for group #4 (16384, counted=15451).
Fix? no

Free inodes count wrong for group #6 (16384, counted=15958).
Fix? no

Free inodes count wrong for group #7 (16384, counted=15665).
Fix? no

Free inodes count wrong for group #8 (16384, counted=16204).
Fix? no

Free inodes count wrong for group #12 (16384, counted=16353).
Fix? no

Directories count wrong for group #12 (0, counted=1).
Fix? no

Free inodes count wrong for group #13 (16384, counted=16015).
Fix? no

Free inodes count wrong for group #14 (16384, counted=16352).
Fix? no

Free inodes count wrong for group #15 (16384, counted=11299).
Fix? no

Directories count wrong for group #15 (0, counted=454).
Fix? no

Free inodes count wrong for group #16 (16384, counted=15343).
Fix? no

Directories count wrong for group #16 (0, counted=1041).
Fix? no

Free inodes count wrong for group #17 (16384, counted=15271).
Fix? no

Directories count wrong for group #17 (0, counted=1041).
Fix? no

Free inodes count wrong for group #18 (16384, counted=15005).
Fix? no

Directories count wrong for group #18 (0, counted=1041).
Fix? no

Free inodes count wrong for group #19 (16384, counted=15876).
Fix? no

Directories count wrong for group #19 (0, counted=465).
Fix? no

Free inodes count wrong for group #20 (16384, counted=16325).
Fix? no

Free inodes count wrong for group #29 (16384, counted=16018).
Fix? no

Free inodes count wrong for group #30 (16384, counted=15976).
Fix? no

Free inodes count wrong for group #31 (16384, counted=11661).
Fix? no

Free inodes count wrong for group #32 (16384, counted=15186).
Fix? no

Free inodes count wrong for group #35 (16384, counted=15606).
Fix? no

Free inodes count wrong for group #41 (16384, counted=15656).
Fix? no

Free inodes count wrong for group #42 (16384, counted=15176).
Fix? no

Free inodes count wrong for group #45 (16384, counted=16372).
Fix? no

Free inodes count wrong for group #46 (16384, counted=16166).
Fix? no

Free inodes count wrong for group #47 (16384, counted=16162).
Fix? no

Free inodes count wrong for group #59 (16384, counted=16383).
Fix? no

Directories count wrong for group #59 (0, counted=1).
Fix? no

Free inodes count wrong for group #63 (16384, counted=16383).
Fix? no

Directories count wrong for group #63 (0, counted=1).
Fix? no

Free inodes count wrong for group #67 (16384, counted=16355).
Fix? no

Free inodes count wrong for group #69 (16384, counted=15740).
Fix? no

Free inodes count wrong for group #70 (16384, counted=15421).
Fix? no

Free inodes count wrong for group #71 (16384, counted=15631).
Fix? no

Directories count wrong for group #71 (0, counted=1).
Fix? no

Free inodes count wrong for group #72 (16384, counted=14938).
Fix? no

Free inodes count wrong for group #73 (16384, counted=15854).
Fix? no

Free inodes count wrong for group #74 (16384, counted=15731).
Fix? no

Directories count wrong for group #74 (0, counted=14).
Fix? no

Free inodes count wrong for group #75 (16384, counted=15472).
Fix? no

Directories count wrong for group #75 (0, counted=18).
Fix? no

Free inodes count wrong for group #76 (16384, counted=15827).
Fix? no

Free inodes count wrong for group #77 (16384, counted=16174).
Fix? no

Free inodes count wrong for group #78 (16384, counted=16025).
Fix? no

Free inodes count wrong for group #79 (16384, counted=16084).
Fix? no

Free inodes count wrong for group #80 (16384, counted=16012).
Fix? no

Free inodes count wrong for group #81 (16384, counted=15712).
Fix? no

Free inodes count wrong for group #82 (16384, counted=15994).
Fix? no

Free inodes count wrong for group #83 (16384, counted=15894).
Fix? no

Free inodes count wrong for group #84 (16384, counted=15707).
Fix? no

Free inodes count wrong for group #85 (16384, counted=16212).
Fix? no

Free inodes count wrong for group #86 (16384, counted=16092).
Fix? no

Free inodes count wrong for group #87 (16384, counted=16135).
Fix? no

Free inodes count wrong for group #88 (16384, counted=16138).
Fix? no

Free inodes count wrong for group #89 (16384, counted=16046).
Fix? no

Free inodes count wrong for group #90 (16384, counted=16001).
Fix? no

Free inodes count wrong for group #91 (16384, counted=15893).
Fix? no

Free inodes count wrong for group #92 (16384, counted=15559).
Fix? no

Free inodes count wrong for group #93 (16384, counted=16196).
Fix? no

Free inodes count wrong for group #94 (16384, counted=15936).
Fix? no

Free inodes count wrong for group #95 (16384, counted=16221).
Fix? no

Free inodes count wrong for group #96 (16384, counted=15878).
Fix? no

Free inodes count wrong for group #97 (16384, counted=16084).
Fix? no

Free inodes count wrong for group #98 (16384, counted=16282).
Fix? no

Free inodes count wrong for group #99 (16384, counted=16079).
Fix? no

Free inodes count wrong for group #100 (16384, counted=15930).
Fix? no

Free inodes count wrong for group #101 (16384, counted=16065).
Fix? no

Free inodes count wrong for group #102 (16384, counted=16105).
Fix? no

Free inodes count wrong for group #103 (16384, counted=16285).
Fix? no

Free inodes count wrong for group #104 (16384, counted=16249).
Fix? no

Free inodes count wrong for group #105 (16384, counted=16191).
Fix? no

Free inodes count wrong for group #106 (16384, counted=16203).
Fix? no

Free inodes count wrong for group #107 (16384, counted=16037).
Fix? no

Free inodes count wrong for group #108 (16384, counted=16147).
Fix? no

Free inodes count wrong for group #109 (16384, counted=16165).
Fix? no

Free inodes count wrong for group #110 (16384, counted=16186).
Fix? no

Free inodes count wrong for group #111 (16384, counted=16243).
Fix? no

Free inodes count wrong for group #112 (16384, counted=16203).
Fix? no

Free inodes count wrong for group #113 (16384, counted=16252).
Fix? no

Free inodes count wrong for group #114 (16384, counted=16180).
Fix? no

Free inodes count wrong for group #115 (16384, counted=16153).
Fix? no

Free inodes count wrong for group #116 (16384, counted=16380).
Fix? no

Free inodes count wrong for group #117 (16384, counted=16241).
Fix? no

Free inodes count wrong for group #118 (16384, counted=15766).
Fix? no

Free inodes count wrong for group #120 (16384, counted=16270).
Fix? no

Free inodes count wrong for group #124 (16384, counted=16369).
Fix? no

Free inodes count wrong for group #126 (16384, counted=16281).
Fix? no

Free inodes count wrong for group #127 (16384, counted=16019).
Fix? no

Free inodes count wrong for group #128 (16384, counted=15918).
Fix? no

Free inodes count wrong for group #129 (16384, counted=15942).
Fix? no

Free inodes count wrong for group #130 (16384, counted=16200).
Fix? no

Free inodes count wrong for group #131 (16384, counted=16234).
Fix? no

Free inodes count wrong for group #132 (16384, counted=16262).
Fix? no

Free inodes count wrong for group #133 (16384, counted=15360).
Fix? no

Free inodes count wrong for group #134 (16384, counted=16212).
Fix? no

Free inodes count wrong for group #135 (16384, counted=16203).
Fix? no

Free inodes count wrong for group #136 (16384, counted=16179).
Fix? no

Free inodes count wrong for group #137 (16384, counted=16292).
Fix? no

Free inodes count wrong for group #138 (16384, counted=16295).
Fix? no

Free inodes count wrong for group #139 (16384, counted=16210).
Fix? no

Free inodes count wrong for group #140 (16384, counted=16263).
Fix? no

Free inodes count wrong for group #141 (16384, counted=16236).
Fix? no

Free inodes count wrong for group #142 (16384, counted=16163).
Fix? no

Free inodes count wrong for group #143 (16384, counted=16280).
Fix? no

Free inodes count wrong for group #144 (16384, counted=16251).
Fix? no

Free inodes count wrong for group #145 (16384, counted=16038).
Fix? no

Free inodes count wrong for group #146 (16384, counted=16249).
Fix? no

Free inodes count wrong for group #147 (16384, counted=16169).
Fix? no

Free inodes count wrong for group #148 (16384, counted=16259).
Fix? no

Free inodes count wrong for group #149 (16384, counted=11949).
Fix? no

Directories count wrong for group #149 (0, counted=469).
Fix? no

Free inodes count wrong for group #150 (16384, counted=15175).
Fix? no

Directories count wrong for group #150 (0, counted=120).
Fix? no

Free inodes count wrong for group #151 (16384, counted=16241).
Fix? no

Free inodes count wrong for group #152 (16384, counted=16166).
Fix? no

...
-*-*-*-*-
post TOO LONG 
post TOO LONG 
post TOO LONG 
-*-*-*-*-
...

Free inodes count wrong for group #200 (16384, counted=15905).
Fix? no

Free inodes count wrong for group #201 (16384, counted=15799).
Fix? no

Free inodes count wrong for group #202 (16384, counted=15634).
Fix? no

Free inodes count wrong for group #203 (16384, counted=15833).
Fix? no

Free inodes count wrong (3424245, counted=3354264).
Fix? no


/dev/md0: ********** WARNING: Filesystem still has errors **********

/dev/md0: 11/3424256 files (31218.2% non-contiguous), 151509/6835600 blocks
 
Old 04-09-2007, 10:04 PM   #30
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,238

Rep: Reputation: 121Reputation: 121
"no ,it's not a mistake. I just -assemble /dev/md1 to try again."

Did you actually try "mount /dev/md1 /mnt" (without the fs type) after you reassembled it? I can't see what you're doing, so you have to be very specific when you tell me what you do. I cannot tell whether you have actually tried mounting without the fs type with the way it is assembled.
 
  


Reply

Tags
fs, md0, mdadm, mount, type


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
RAID5 using mdadm, how to mount /dev/md0? ggduff Linux - Software 4 11-14-2007 01:59 AM
can not mount RAID 0 /dev/md0 dysenteryduke Linux - Software 3 09-15-2005 03:19 PM
help me setup software raid 1 on slackware with mdadm xrado Slackware 2 03-02-2005 05:50 AM
Software RAID with mdadm problems... robbow52 Debian 2 04-19-2004 07:06 PM
mdadm mail with software RAID brucehohl Linux - Software 1 12-20-2003 06:17 AM


All times are GMT -5. The time now is 02:43 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration