Results 1 to 2 of 2
I have a new Vertex2 Solid State Drive. When I try to install any distributions, formating the drive in EXT3 or EXT4 (or LUKS with EXT3, or EXT4). My hard ...
- 06-01-2010 #1Just Joined!
- Join Date
- Jun 2010
- Posts
- 1
Vertex2 SSD - ATA Timeout with Ext3/4 but not Ext2
I have a new Vertex2 Solid State Drive. When I try to install any distributions, formating the drive in EXT3 or EXT4 (or LUKS with EXT3, or EXT4). My hard drive times out during a copy process. (OpenSUSE 11.2 for example would crash after the 2nd file of X11. Debian got ~12% done when it crashed.)
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 EXT3/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 errors.
Symptoms:
-During any installation of these Distributions on EXT3 or EXT4 I get I/O errors, and the file-system remounts as Read Only.
Info:
While mounted with EXT3/4Code: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)
While with EXT3/4Code:# 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)
dmesg for EXT4Code:# badblocks -v /dev/sda Checking blocks 0 to 48848183 Checking for bad blocks (read-only test): done Pass completed, 0 bad blocks found.
dmesg for EXT3Code:#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
Code:[66147.701430] ata5: hard resetting link [66147.701434] ata5: nv: skipping hardreset on occupied port [66147.954290] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [66148.068288] ata5.00: configured for UDMA/133 [66148.068309] ata5: EH complete [66155.701446] ata5: drained 256 bytes to clear DRQ. [66155.701455] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [66155.701474] ata5.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in [66155.701476] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [66155.701491] ata5.00: status: { DRDY } [66155.701503] ata5: hard resetting link [66155.701510] ata5: nv: skipping hardreset on occupied port [66155.852470] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [66155.966167] ata5.00: configured for UDMA/133 [66155.966195] ata5: EH complete [66471.704288] Intel AES-NI instructions are not detected. [66471.721083] padlock: VIA PadLock not detected. [66471.732718] alg: No test for stdrng (krng) [66471.733945] alg: No test for stdrng (ansi_cprng) [66471.739303] padlock: VIA PadLock Hash Engine not detected. [66471.761918] device-mapper: ioctl: unable to remove open device temporary-cryptsetup-19645 [66471.762218] Buffer I/O error on device dm-0, logical block 120 [66471.762227] Buffer I/O error on device dm-0, logical block 121 [66471.762234] Buffer I/O error on device dm-0, logical block 122 [66471.762241] Buffer I/O error on device dm-0, logical block 123 [66471.762248] Buffer I/O error on device dm-0, logical block 124 [66471.762256] Buffer I/O error on device dm-0, logical block 120 [66471.762263] Buffer I/O error on device dm-0, logical block 121 [66471.762270] Buffer I/O error on device dm-0, logical block 122 [66471.762277] Buffer I/O error on device dm-0, logical block 123 [66989.893398] kjournald starting. Commit interval 15 seconds [66989.893652] EXT3 FS on dm-0, internal journal [66989.893665] EXT3-fs: mounted filesystem with ordered data mode. [67023.701419] ata5: drained 256 bytes to clear DRQ. [67023.701428] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [67023.701447] ata5.00: cmd ec/00:00:00:00:00/00:00:00:00:00/40 tag 0 pio 512 in [67023.701449] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [67023.701464] ata5.00: status: { DRDY } [67023.701475] ata5: hard resetting link [67023.701482] ata5: nv: skipping hardreset on occupied port [67023.852104] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [67023.950166] ata5.00: configured for UDMA/133 [67023.950192] ata5: EH complete [67242.701065] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [67242.701084] ata5.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [67242.701086] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [67242.701101] ata5.00: status: { DRDY } [67242.701112] ata5: hard resetting link [67242.701120] ata5: nv: skipping hardreset on occupied port [67242.852067] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [67242.947209] ata5.00: configured for UDMA/133 [67242.947221] ata5.00: device reported invalid CHS sector 0 [67242.947234] end_request: I/O error, dev sda, sector 0 [67242.947255] ata5: EH complete [67273.701054] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [67273.701073] ata5.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [67273.701075] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [67273.701089] ata5.00: status: { DRDY } [67273.701101] ata5: hard resetting link [67273.701108] ata5: nv: skipping hardreset on occupied port [67273.852064] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [67273.947207] ata5.00: configured for UDMA/133 [67273.947219] ata5.00: device reported invalid CHS sector 0 [67273.947231] end_request: I/O error, dev sda, sector 0 [67273.947252] __ratelimit: 49 callbacks suppressed [67273.947258] ata5: EH complete [67273.947280] Buffer I/O error on device dm-0, logical block 6065687 [67273.947298] lost page write due to I/O error on dm-0 [67273.947381] Aborting journal on device dm-0. [67274.031603] EXT3-fs error (device dm-0) in ext3_new_inode: Journal has aborted [67274.802245] EXT3-fs error (device dm-0) in ext3_mkdir: Journal has aborted [67274.830144] ext3_abort called. [67274.830169] EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal [67274.830181] Remounting filesystem read-only [67275.213428] __journal_remove_journal_head: freeing b_committed_dataCode:#fdisk -H 32 -S 32 /dev/sda
Code:#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 EXT3/4 is having troubles? Are there any more tests I can perform?
- 06-02-2010 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,961
Most likely reason is the overhead of the journalling of ext3/ext4. In fact, ext3 is ext2, but with journalling added. I would guess that you either need to switch to ext2, or somehow increase the timeout parameters of the drive.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
Reply With Quote 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
