I have a new Vertex2 Solid State Drive. When I try to install any distributions using EXT4 (or LUKS with EXT4). My hard drive times out during the 'file copy' process. (OpenSUSE 11.2 for example would crash after the 2nd file of X11. Other distros get a bit into the install before it gets 'read-only' errors.)
DISTRO'S ATTEMPTED:
Ubuntu 10 - x64
Debian 5 - x64
PCLinuxOS 9 - x32
CentOS 5.4 - x64
OpenSUSE 11.2 (Linux 2.6.31) - x64
OpenSUSE 11.3 - Build 0625 (Linux 2.6.34) - x64
Attempts:
-If I use my Seagate 1TB drive I can install just fine to any EXT4 partition. (Same SATA cable and SATA controller port)
-If I use the EXT2 filesystem on my Verex2 SSD I can install any distro.
-Windows 2003/NTFS also installs fine to the Vertex2 SSD.
-Writing random 'dd' data to the entire SDD returns no errors.
-Upgraded EVGA motherboard BIOS to latest version (P33) didn't help.
-Installing the OpenSUSE 11.2 OS to my HDD, and then copying files from the HDD to the Vertex2 causes the same I/O timout/remount in read only errors.
-----------------
Mobo: EVGA 122-CK-NF68
BIOS: P33
CPU: Intel Core2 6600 2.40GHz
Vid: GeForce 9600 GT
HDD: Vertex2 50GB - SeagateNS 1TB
OS: OpenSuse 11.2 - 2.6.31.12-0.2-desktop
OpenSUSE 11.2 linux 2.6.31.5-0.1-desktop x86_64 x
00:0e.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
# hwinfo --disk
Hardware Class: disk
Model: "OCZ-VERTEX2"
Revision: "1.00"
Driver: "sata_nv", "sd"
Driver Modules: "sata_nv"
Device File: /dev/sda
Device Files: /dev/sda, /dev/block/8:0, /dev/disk/by-id/ata-OCZ-VERTEX2_f0aa20408, /dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_f0aa20408, /dev/disk/by-path/pci-0000:00:0e.2-scsi-0:0:0:0, /dev/disk/by-id/edd-int13_dev80
Device Number: block 8:0-8:15
BIOS id: 0x80
Geometry (Logical): CHS 6081/255/63
Size: 97696368 sectors a 512 bytes
Geometry (BIOS EDD): CHS 96921/16/63
Size (BIOS EDD): 97696368 sectors
Geometry (BIOS Legacy): CHS 1023/255/63
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #30 (IDE interface)
# badblocks -v /dev/sda
Checking blocks 0 to 48848183
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found.
#dmesg
[ 310.151946] EXT4-fs (dm-0): barriers enabled
[ 310.374777] EXT4-fs warning (device dm-0): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
[ 310.374798] EXT4-fs warning (device dm-0): ext4_clear_journal_err: Marking fs in need of filesystem check.
[ 310.374823] kjournald2 starting: pid 4571, dev dm-0:8, commit interval 5 seconds
[ 310.375067] EXT4-fs (dm-0): warning: mounting fs with errors, running e2fsck is recommended
[ 310.375220] EXT4-fs (dm-0): internal journal on dm-0:8
[ 310.375228] EXT4-fs (dm-0): delayed allocation enabled
[ 310.375234] EXT4-fs: file extents enabled
[ 310.377810] EXT4-fs: mballoc enabled
[ 310.377829] EXT4-fs (dm-0): recovery complete
[ 310.378071] EXT4-fs (dm-0): mounted filesystem with ordered data mode
[ 376.704083] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 376.704103] ata5.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 376.704104] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 376.704119] ata5.00: status: { DRDY }
[ 376.704131] ata5: hard resetting link
[ 376.704137] ata5: nv: skipping hardreset on occupied port
[ 376.855065] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 376.950181] ata5.00: configured for UDMA/133
[ 376.950193] ata5.00: device reported invalid CHS sector 0
[ 376.950204] end_request: I/O error, dev sda, sector 0
[ 376.950225] ata5: EH complete
[ 407.704102] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 407.704122] ata5.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 407.704124] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 407.704139] ata5.00: status: { DRDY }
[ 407.704150] ata5: hard resetting link
[ 407.704157] ata5: nv: skipping hardreset on occupied port
[ 407.855065] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 407.970209] ata5.00: configured for UDMA/133
[ 407.970220] ata5.00: device reported invalid CHS sector 0
[ 407.970230] end_request: I/O error, dev sda, sector 0
[ 407.970248] ata5: EH complete
[ 407.970361] Aborting journal on device dm-0:8.
[ 462.492850] EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal
[ 462.492866] EXT4-fs (dm-0): Remounting filesystem read-only
[ 524.928830] EXT4-fs: mballoc: 0 blocks 0 reqs (0 success)
[ 524.928854] EXT4-fs: mballoc: 0 extents scanned, 0 goal hits, 0 2^N hits, 0 breaks, 0 lost
[ 524.928861] EXT4-fs: mballoc: 0 generated and it took 0
[ 524.928866] EXT4-fs: mballoc: 0 preallocated, 0 discarded
[ 524.928958] EXT4-fs error (device dm-0): ext4_put_super: Couldn't clean up the journal
[ 629.888028] EXT4-fs (dm-0): barriers enabled
[ 629.896701] kjournald2 starting: pid 4815, dev dm-0:8, commit interval 5 seconds
[ 629.896709] EXT4-fs warning (device dm-0): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
[ 629.896718] EXT4-fs warning (device dm-0): ext4_clear_journal_err: Marking fs in need of filesystem check.
[ 629.896981] EXT4-fs (dm-0): warning: mounting fs with errors, running e2fsck is recommended
[ 629.897165] EXT4-fs (dm-0): internal journal on dm-0:8
[ 629.897177] EXT4-fs (dm-0): delayed allocation enabled
[ 629.897186] EXT4-fs: file extents enabled
[ 629.899824] EXT4-fs: mballoc enabled
[ 629.899843] EXT4-fs (dm-0): recovery complete
[ 629.899985] EXT4-fs (dm-0): mounted filesystem with ordered data mode
[ 696.701053] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 696.701073] ata5.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 696.701075] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 696.701090] ata5.00: status: { DRDY }
[ 696.701102] ata5: hard resetting link
[ 696.701108] ata5: nv: skipping hardreset on occupied port
[ 696.852081] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 696.966202] ata5.00: configured for UDMA/133
[ 696.966213] ata5.00: device reported invalid CHS sector 0
[ 696.966226] end_request: I/O error, dev sda, sector 0
[ 696.966250] ata5: EH complete
[ 727.701061] ata5.00: NCQ disabled due to excessive errors
[ 727.701076] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 727.701090] ata5.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 727.701092] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 727.701106] ata5.00: status: { DRDY }
[ 727.701118] ata5: hard resetting link
[ 727.701125] ata5: nv: skipping hardreset on occupied port
[ 727.852159] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 727.950222] ata5.00: configured for UDMA/133
[ 727.950233] ata5.00: device reported invalid CHS sector 0
[ 727.950244] end_request: I/O error, dev sda, sector 0
[ 727.950265] ata5: EH complete
[ 727.950293] Aborting journal on device dm-0:8.
[ 727.959032] EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal
[ 727.959044] EXT4-fs (dm-0): Remounting filesystem read-only
#fdisk -H 32 -S 32 /dev/sda
#fdisk -l
Disk /dev/sda: 50.0 GB, 50020540416 bytes
32 heads, 32 sectors/track, 95406 cylinders
Units = cylinders of 1024 * 512 = 524288 bytes
Disk identifier: 0x000863d8
Device Boot Start End Blocks Id System
/dev/sda1 * 2 129 65536 83 Linux
/dev/sda2 130 16513 8388608 82 Linux swap / Solaris
/dev/sda3 16514 95385 40382464 83 Linux
Can anyone tell me why EXT2 is fine while EXT 4 is having troubles?
What kind of further tests can perform?
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
