https://bugzilla.novell.com/show_bug.cgi?id=371657 User deanjo@sasktel.net added comment https://bugzilla.novell.com/show_bug.cgi?id=371657#c7 --- Comment #7 from Dean Hilkewich <deanjo@sasktel.net> 2008-03-31 20:14:39 MST --- I'm not sure how much more information (or what) I can give you to reproduce the issue. Here is what I do. I simply enable the fakeraid in bios, set the seagates up to a striped setup. I then go into YaST Partitioner, see the mapper device of the raid set and format it to a file system (ext3 or xfs it does not matter) set it to mount to /local/myraid hit apply and that's it. Upon reboot I get the attempt to access beyond end of device on the seagate part of the raid. The Maxtor's like I said before behave as expected and do not give that error nor do I get the message if I setup a pair of older Maxtor 120 Gigs in place of the seagates following the same procedure to get them raided. Now the maxtors are Sata 1 drives and the seagates are Sata 2 drives. Could it perhaps be because the Seagates are NCQ enabled drives? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.