Storage drives is causting system crash

Posted by Chad on Stack Overflow See other posts from Stack Overflow or by Chad
Published on 2010-05-08T17:04:06Z Indexed on 2010/05/08 17:08 UTC
Read the original article Hit count: 210

Filed under:
|
|

I'm running Centos 5.4 with 750GB(ntfs) and 2TB drives for storage. Originally I installed the 750, everything seemed fine and then I installed the 2TB drive with NTFS already partitioned. I noticed when I would copy a lot of videos it would crash (no mouse or response from server) about 20min into it. After doing some troubleshooting I noticed the 750 would also crash when doing the same task so I decided that NTFS may be the problem. I unmounted the 2TB drive and tried to partition and format it using ext2 but when using parted it would crash at this point "writing inode tables". Looking at the dmesg logs I believe this is the error "mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining". Any idea as to what could be causing this?

© Stack Overflow or respective owner

Storage drives is causting system crash

Posted by Chad on Server Fault See other posts from Server Fault or by Chad
Published on 2010-05-08T17:04:06Z Indexed on 2010/05/08 17:18 UTC
Read the original article Hit count: 210

Filed under:
|
|

I'm running Centos 5.4 with 750GB(ntfs) and 2TB drives for storage. Originally I installed the 750, everything seemed fine and then I installed the 2TB drive with NTFS already partitioned. I noticed when I would copy a lot of videos it would crash (no mouse or response from server) about 20min into it. After doing some troubleshooting I noticed the 750 would also crash when doing the same task so I decided that NTFS may be the problem. I unmounted the 2TB drive and tried to partition and format it using ext2 but when using parted it would crash at this point "writing inode tables". Looking at the dmesg logs I believe this is the error "mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining". Any idea as to what could be causing this?

© Server Fault or respective owner

Related posts about centos

Related posts about linux