January 17, 201412 yr Author Now I did really type reiserfsck --check /dev/md11 It says: Journal parameters from the superblock does not match to the journal headers ones. It looks like that you created your fs with oldreiserfs progs. Journal header is fixed. And then: Replaying journal: No transactions found Like you can see on the picture. Disk 11 and disk 12 are freshly added empty disks. They both have been written with zero's. They were never part of the array, so I don't understand why it says I created the filesystem with old reiserfsprogs. They showed up unformatted in the GUI some posts ago and that's it. The console seems to be doing nothing now for an hour, what should I do next?
January 17, 201412 yr If the drives have never been added to the array and then formatted then there is no file system and any reiserfsck output should be ignored. This line indicate a BIOS incompatibility. Check for BIOS updates. Jan 9 00:23:16 Tower kernel: res 01/04:00:58:02:04/00:00:00:00:00/40 Emask 0x3 (HSM violation)
January 18, 201412 yr Author Ok, Since there was no data on disk 10 thru 12, I decided to remove them from the array using the New Config Utility. I did this so I could let it Sync Parity with my old disks 1 thru 9, and then later add one disk at a time. Parity-Sync is so much faster now with the MV8! Because my initial question was: Is my power supply to weak?, I now know the answer to that, AND I can see all my other disks in the GUI, (almost) all my questions about that subject are answered. So I guess I can call the subject [sOLVED]. If there are any questions later about adding the extra disks (and the faults on my old md11), I will make a new subject. Thanx everyone for helping me!!
Archived
This topic is now archived and is closed to further replies.