![]() I tried creating a duplicate by creating partitions and copying the files to the correct location. The SSD had a partition on it with a boot file. I suppose I should try it again with another SSD. My suspicion is that there are bugs in the USB driver code that came with the BSP but I’m not at all sure. The system did not see the USB drive at all. I put the SSD in a USB enclosure and plugged it in. Now before you ask, I did try to connect this to a QNX 7 system. The customer tells me that there is a procedure with his software than can import files which writes them to the SSD, so obviously it can be used read-write. Is there such a thing as a software read-only switch on an SSD? A lot of devices such as floppy disks and SD cards have such a switch that is mechanical. I was able to mount it read only and I could see all the files and copy them off. I kept getting a message that it was read only. It was created with QNX 7, not sure which version. It had two partitions, each with a QNX 6 (power-safe) file system on it. I don’t think the brand is relevant, but it might be. I ran into some strange behaviors that I’ve never seen before and I’m wondering if anyone knows anything about them. We just wanted to delete some files from an SSD. There was nothing nefarious about what we were trying to do. This guide describes this rather complex procedure in English, in a very good way IMHO.I was trying to help someone with a proprietary system that uses QNX. You will lose all your data on it, but if you managed to back it up, then it's not a big deal. If you get a successful recognition, quickly backup all your data, as it might be your last chance to do so.Īt that point you may want to try to revive your drive, you need to use SandForce's official software do so. You may try multiple times before giving up, as it is your only chance to recover your SSD without losing data. This operations might work if the controller got stuck after an improper SATA wake-up command after hybernation. Then shutdown your computer and wait another 5 minutes. Try to unplug it from its socket, wait 5 minutes, then plug it back in and open the BIOS, leaving it open for 10 minutes. Flashing the controller will inevitably lead to the loss of all your documents.īefore starting a flashing procedure you can always try having the SSD to " cycle", in order to force it out of panic mode. Unfortunately, you will not be able to retain your data. You can fix this within Linux: you'll need to operate with Fedora, in order to force-flash a new firmare on the SSD's controller. It is a common issue with SF-2000 controllers. The contents on the drive are quite important, so if possible, I'm trying to recover this drive in a non-destructive way.Īs your drive is recognised as SandForce, this means that your SSD controller is stuck in "panic mode". ![]() If this is the issue, is there any way to fix this from within Linux? What further steps should I do to try to recover this drive? I/O size (minimum/optimal): 4096 bytes / 4096 bytesįrom what I can tell, the issue may be caused by the "DevSlp" feature of the SSD ( ). Sector size (logical/physical): 512 bytes / 4096 bytes Physical block size: 512.00 Byte (2^9 Bytes)įdisk: Disk /dev/sdb: 32 KiB, 32768 bytes, 64 sectors Doneīad news: The device `/dev/sdb' is damagedĪpproximate cache size: 0.00 Byte (0 blocks), need-reset=no WARNING: Probing normally takes from a few seconds to 15 minutes, but ![]() This is free software see the source for copying conditions. To continue, add one or more '-T permissive' options.Ĭopyright (C) 2010 Digirati Internet LTDA. SMART support is: Unavailable - device lacks SMART capability.Ī mandatory SMART command failed: exiting. Sector Sizes: 512 bytes logical, 4096 bytes physicalĭevice is: Not in smartctl database ĪTA Version is: ATA8-ACS T13/1699-D revision 4 Smartctl 7.1 r5022 (local build)Ĭopyright (C) 2002-19, Bruce Allen, Christian Franke, = START OF INFORMATION SECTION = I also tried using PNY's firmware update tool, but it didn't detect my SSD (even when installed internally).īelow is the output of smartctl: # smartctl -a /dev/sdb However, I am not using an Intel SSD, so the firmware update doesn't apply. After some Googling, I found this Intel thread which seems to describe my problem: The kernel detects the new device, but it refuses to mount it or perform any operations on the block device, stating, "I/O Error". ![]() Plugging it into my new laptop via SATA-USB adapter, I noticed a few interesting things. The drive shows up in the BIOS as a "0.0GB Solid State Drive", when it used to show PNY and the serial number. Then suddenly the laptop stopped booting. ![]() I have a PNY "CS1111" 240 GB SSD which I was using in my old laptop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |