Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
spockOffline
Post subject: Sandisk Ultra SSD (SandForce controller) disconnecting  PostPosted: 02.01.2012, 12:22



Joined: 2010-09-11
Posts: 50
Location: Near Milton Keynes, UK
Status: Offline
Hello, Happy New Year and thanks for a fabulous new aptosid! Very Happy

I'm trying to install the "imera 2011-02" live CD (and more recently "ponos 2011-03" on a USB stick) onto a 120GB SanDisk Ultra SSD, following the fine manual religiously, having read and re-read all GPT docs and most articles+reviews on the web about SSDs. Unfortunately the SSD keeps disconnecting and becomes unusable, no longer appearing in fdisk -l until after powercycling the SSD (rebooting the PC).

I tried using gdisk and also using cfdisk to partition the drive, both with sectors aligned and non-aligned, in case my partitioning was to blame. I just wanted to check that I'm not making stupid mistakes before I RMA the drive.

After GPT partitioning (with gdisk, making a BIOS Boot Partition, a swap partition and a Linux partition, all verified fine), attempts to create a filesystem using mkfs.ext4 cause the SSD to become inaccessible - here are errors in the log from /var/log/syslog:
      Code:
ata3: lost interrupt (Status 0x58)
ata3: drained 512 bytes to clear DRQ
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata3.00: failed command: IDENTIFY DEVICE
[...]
end_request: I/O error, dev sda, sector 4917250
[...]
sda: detected capacity change from 120034123776 to 0

This behaviour is repeatable. Rebooting the machine, I can see the SSD fine, until I try and write a filesystem onto it. Since doing this before Christmas, I have retried with the new aptosid 2011-03 and get exactly the same thing happening. I had high hopes for ponos since the changelog mentioned improved support for GPT/SSDs, but it looks like the problem is with this particular SSD or even the entire controller family, which would be a shame as they otherwise seem a good buy. I know all about the BSOD issues in Windows with SandForce 2281 controllers. I'm unsure which SF controller is in the SanDisk Ultra, as Wikipedia says SF2200, but a detailed review says the older SF1200 previous-generation. This article has some comments:

http://www.anandtech.com/show/4973/sand ... y?all=true
      Quote:
"If your non-SF drive dies or is problematic, you can just swap it out with the vendor or retailer. If your SF22xx drive BSOD/Disconnects/etc,, you can't do too much about it. The problem is with all the 22xxs." -ckryan

      Quote:
"It's great that there is a fix for the second generation drives, but what about the first generation? I have 2 SF-1200 drives that disconnect randomly after waking up from S3." - Quad5Ny


I read the single post in Sandisk's Support Forum about Ultra SSDs. I emailed support and their only answer was that Googling (they didn't actually know themselves!) showed some reports of problems, and I should try other cables and PCs, which I did, using my new Phenom X6 1055T workstation (also non-UEFI). My friend also had the same error with an OCZ (same/similar SandForce controller):

http://www.jumpstation.co.uk/flog/Aug20 ... 0820112146
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
spockOffline
Post subject:   PostPosted: 02.01.2012, 12:23



Joined: 2010-09-11
Posts: 50
Location: Near Milton Keynes, UK
Status: Offline
Here is /var/log/syslog:

      Code:

Jan 2 10:45:01 aptosid kernel: [ 81.728046] ata3: lost interrupt (Status 0x58)
Jan 2 10:45:01 aptosid kernel: [ 81.728408] ata3: drained 512 bytes to clear DRQ
Jan 2 10:45:01 aptosid kernel: [ 81.728419] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 10:45:01 aptosid kernel: [ 81.728425] ata3.00: failed command: SMART
Jan 2 10:45:01 aptosid kernel: [ 81.728433] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
Jan 2 10:45:01 aptosid kernel: [ 81.728435] res 40/00:01:ea:bf:cd/00:00:00:00:00/e0 Emask 0x4 (timeout)
Jan 2 10:45:01 aptosid kernel: [ 81.728439] ata3.00: status: { DRDY }
Jan 2 10:45:01 aptosid kernel: [ 81.728454] ata3: soft resetting link
Jan 2 10:45:01 aptosid kernel: [ 81.920151] ata3.00: configured for UDMA/133
Jan 2 10:45:01 aptosid kernel: [ 81.920185] ata3: EH complete
Jan 2 10:45:09 aptosid kernel: [ 89.728052] ata3: lost interrupt (Status 0x50)
Jan 2 10:45:09 aptosid kernel: [ 89.728072] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 10:45:09 aptosid kernel: [ 89.728077] ata3.00: failed command: SMART
Jan 2 10:45:09 aptosid kernel: [ 89.728085] ata3.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
Jan 2 10:45:09 aptosid kernel: [ 89.728087] res 40/00:01:ea:bf:cd/00:00:00:00:00/e0 Emask 0x4 (timeout)
Jan 2 10:45:09 aptosid kernel: [ 89.728090] ata3.00: status: { DRDY }
Jan 2 10:45:09 aptosid kernel: [ 89.728105] ata3: soft resetting link
Jan 2 10:45:09 aptosid kernel: [ 89.904136] ata3.00: configured for UDMA/133
Jan 2 10:45:09 aptosid kernel: [ 89.904164] ata3: EH complete
Jan 2 10:46:21 aptosid kernel: [ 161.760036] ata3: lost interrupt (Status 0x58)
Jan 2 10:46:21 aptosid kernel: [ 161.760397] ata3: drained 512 bytes to clear DRQ
Jan 2 10:46:21 aptosid kernel: [ 161.760407] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 10:46:21 aptosid kernel: [ 161.760413] ata3.00: failed command: IDENTIFY DEVICE
Jan 2 10:46:21 aptosid kernel: [ 161.760421] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Jan 2 10:46:21 aptosid kernel: [ 161.760422] res 40/00:01:ea:bf:cd/00:00:00:00:00/e0 Emask 0x4 (timeout)
Jan 2 10:46:21 aptosid kernel: [ 161.760427] ata3.00: status: { DRDY }
Jan 2 10:46:21 aptosid kernel: [ 161.760441] ata3: soft resetting link
Jan 2 10:46:21 aptosid kernel: [ 161.936134] ata3.00: configured for UDMA/133
Jan 2 10:46:21 aptosid kernel: [ 161.936159] ata3: EH complete
Jan 2 10:46:29 aptosid kernel: [ 169.728030] ata3: lost interrupt (Status 0x58)
Jan 2 10:46:29 aptosid kernel: [ 169.728391] ata3: drained 512 bytes to clear DRQ
Jan 2 10:46:29 aptosid kernel: [ 169.728401] ata3.00: limiting speed to UDMA/100:PIO4
Jan 2 10:46:29 aptosid kernel: [ 169.728407] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 10:46:29 aptosid kernel: [ 169.728413] ata3.00: failed command: IDENTIFY DEVICE
Jan 2 10:46:29 aptosid kernel: [ 169.728420] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Jan 2 10:46:29 aptosid kernel: [ 169.728422] res 40/00:01:ea:bf:cd/00:00:00:00:00/e0 Emask 0x4 (timeout)
Jan 2 10:46:29 aptosid kernel: [ 169.728426] ata3.00: status: { DRDY }
Jan 2 10:46:29 aptosid kernel: [ 169.728441] ata3: soft resetting link
Jan 2 10:46:29 aptosid kernel: [ 169.920138] ata3.00: configured for UDMA/100
Jan 2 10:46:29 aptosid kernel: [ 169.920163] ata3: EH complete
Jan 2 10:48:39 aptosid kernel: [ 300.135371] sda: sda1 sda2
Jan 2 10:49:10 aptosid kernel: [ 331.104047] ata3: lost interrupt (Status 0x58)
Jan 2 10:49:10 aptosid kernel: [ 331.104409] ata3: drained 512 bytes to clear DRQ
Jan 2 10:49:10 aptosid kernel: [ 331.104420] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 10:49:10 aptosid kernel: [ 331.104425] ata3.00: failed command: IDENTIFY DEVICE
Jan 2 10:49:10 aptosid kernel: [ 331.104433] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Jan 2 10:49:10 aptosid kernel: [ 331.104435] res 40/00:01:ea:bf:cd/00:00:00:00:00/e0 Emask 0x4 (timeout)
Jan 2 10:49:10 aptosid kernel: [ 331.104439] ata3.00: status: { DRDY }
Jan 2 10:49:10 aptosid kernel: [ 331.104454] ata3: soft resetting link
Jan 2 10:49:11 aptosid kernel: [ 331.296139] ata3.00: configured for UDMA/100
Jan 2 10:49:11 aptosid kernel: [ 331.296166] ata3: EH complete
Jan 2 10:49:40 aptosid udevd[1718]: timeout 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda'
Jan 2 10:49:41 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:43 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:44 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:45 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:46 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:47 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:48 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:49 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:50 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:51 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:52 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:53 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:54 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:55 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:56 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:57 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:58 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:49:59 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:00 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:01 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:02 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:03 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:04 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:05 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:06 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:07 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:08 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:09 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:10 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:11 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:11 aptosid kernel: [ 392.032072] ata3: lost interrupt (Status 0x50)
Jan 2 10:50:11 aptosid kernel: [ 392.032095] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 2 10:50:11 aptosid kernel: [ 392.032101] ata3.00: failed command: FLUSH CACHE
Jan 2 10:50:11 aptosid kernel: [ 392.032110] ata3.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 2 10:50:11 aptosid kernel: [ 392.032111] res 40/00:01:ea:bf:cd/00:00:00:00:00/e0 Emask 0x4 (timeout)
Jan 2 10:50:11 aptosid kernel: [ 392.032115] ata3.00: status: { DRDY }
Jan 2 10:50:11 aptosid kernel: [ 392.032130] ata3: soft resetting link
Jan 2 10:50:12 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:12 aptosid kernel: [ 392.224140] ata3.00: configured for UDMA/100
Jan 2 10:50:12 aptosid kernel: [ 392.224147] ata3.00: retrying FLUSH 0xe7 Emask 0x4
Jan 2 10:50:13 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:14 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:15 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:16 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:17 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:18 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:19 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:20 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:21 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:22 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:23 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:24 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:25 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:26 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:27 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:27 aptosid kernel: [ 407.224042] ata3.00: qc timeout (cmd 0xe7)
Jan 2 10:50:27 aptosid kernel: [ 407.224050] ata3.00: FLUSH failed Emask 0x4
Jan 2 10:50:27 aptosid kernel: [ 407.224063] ata3: soft resetting link
Jan 2 10:50:27 aptosid kernel: [ 407.416139] ata3.00: configured for UDMA/100
Jan 2 10:50:27 aptosid kernel: [ 407.416145] ata3.00: retrying FLUSH 0xe7 Emask 0x4
Jan 2 10:50:28 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:29 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:30 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:31 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:32 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:33 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:34 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:35 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:36 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:37 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:38 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:39 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:40 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:41 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:42 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:42 aptosid kernel: [ 422.416072] ata3.00: qc timeout (cmd 0xe7)
Jan 2 10:50:42 aptosid kernel: [ 422.416080] ata3.00: FLUSH failed Emask 0x4
Jan 2 10:50:42 aptosid kernel: [ 422.416086] ata3.00: limiting speed to UDMA/100:PIO3
Jan 2 10:50:42 aptosid kernel: [ 422.416100] ata3: soft resetting link
Jan 2 10:50:42 aptosid kernel: [ 422.608140] ata3.00: configured for UDMA/100
Jan 2 10:50:42 aptosid kernel: [ 422.608146] ata3.00: retrying FLUSH 0xe7 Emask 0x4
Jan 2 10:50:43 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:44 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:45 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:46 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:47 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:48 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:49 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:50 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:51 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:52 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:53 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:54 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:55 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:56 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:57 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:58 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:50:59 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:00 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:01 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:02 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:03 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:04 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:05 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:06 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:07 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:08 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:09 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:10 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:11 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:12 aptosid udevd[1718]: timeout: killing 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531]
Jan 2 10:51:12 aptosid kernel: [ 452.608080] ata3.00: qc timeout (cmd 0xe7)
Jan 2 10:51:12 aptosid kernel: [ 452.608087] ata3.00: FLUSH failed Emask 0x4
Jan 2 10:51:12 aptosid kernel: [ 452.608091] ata3.00: disabled
Jan 2 10:51:12 aptosid kernel: [ 452.608115] ata3: soft resetting link
Jan 2 10:51:12 aptosid kernel: [ 452.759096] ata3: EH complete
Jan 2 10:51:12 aptosid kernel: [ 452.761229] sd 2:0:0:0: [sda] READ CAPACITY(16) failed
Jan 2 10:51:12 aptosid kernel: [ 452.761234] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 2 10:51:12 aptosid kernel: [ 452.761240] sd 2:0:0:0: [sda] Sense not available.
Jan 2 10:51:12 aptosid kernel: [ 452.761285] sd 2:0:0:0: [sda] READ CAPACITY failed
Jan 2 10:51:12 aptosid kernel: [ 452.761288] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 2 10:51:12 aptosid kernel: [ 452.761292] sd 2:0:0:0: [sda] Sense not available.
Jan 2 10:51:12 aptosid kernel: [ 452.762093] sd 2:0:0:0: [sda] Asking for cache data failed
Jan 2 10:51:12 aptosid kernel: [ 452.762099] sd 2:0:0:0: [sda] Assuming drive cache: write through
Jan 2 10:51:12 aptosid kernel: [ 452.762107] sda: detected capacity change from 120034123776 to 0
Jan 2 10:51:12 aptosid udevd[1718]: 'scsi_id --whitelisted --replace-whitespace -p0x80 -d/dev/sda' [2531] terminated by signal 9 (Killed)
Jan 2 10:51:12 aptosid udevd[1718]: timeout '/sbin/blkid -o udev -p /dev/sda'
Jan 2 10:51:12 aptosid udevd[1718]: timeout 'udisks-part-id /dev/sda'
Jan 2 10:51:12 aptosid udevd[1718]: timeout 'udisks-probe-ata-smart /dev/sda'
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
DeepDayzeOffline
Post subject:   PostPosted: 02.01.2012, 15:53



Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
if this is a widespread issue maybe Sandisk needs to work with SF to come up with a workaround/fix via a firmware update to keep customers happy
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio