Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
SSD unrecognized disk label
128 views
Skip to first unread message
Allen Hoover
Sep 13, 2018, 5:50:03 PM9/13/18
to
I have an SSD that has some serious issues. It contains files that
are fairly important to recover. The user had not done backups quite
recently.
If I view the SSD in parted, it says unrecognized disk label, and the
size is shown as 1073MB instead of 120GB as it should.
I have another SSD here that would have an identical partition table,
at 1 point it was an exact clone.
There are multiple partitions, but the main one is the one with
important data, and it is an ext4 filesystem.
Is there any hope of recovery?
Please CC me, as I only subscribe to user digest mailing list.
Thank You!
are fairly important to recover. The user had not done backups quite
recently.
If I view the SSD in parted, it says unrecognized disk label, and the
size is shown as 1073MB instead of 120GB as it should.
I have another SSD here that would have an identical partition table,
at 1 point it was an exact clone.
There are multiple partitions, but the main one is the one with
important data, and it is an ext4 filesystem.
Is there any hope of recovery?
Please CC me, as I only subscribe to user digest mailing list.
Thank You!
rv riveravaldez
Sep 14, 2018, 11:30:04 PM9/14/18
to
On Thu, Sep 13, 2018 at 6:16 PM, Allen Hoover
<enterpris...@gmail.com> wrote:
> I have an SSD that has some serious issues. It contains files that
> are fairly important to recover. The user had not done backups quite
> recently.
>
> If I view the SSD in parted, it says unrecognized disk label, and the
> size is shown as 1073MB instead of 120GB as it should.
>
> I have another SSD here that would have an identical partition table,
> at 1 point it was an exact clone.
>
> There are multiple partitions, but the main one is the one with
> important data, and it is an ext4 filesystem.
>
> Is there any hope of recovery?
Have you tried these two?
<enterpris...@gmail.com> wrote:
> I have an SSD that has some serious issues. It contains files that
> are fairly important to recover. The user had not done backups quite
> recently.
>
> If I view the SSD in parted, it says unrecognized disk label, and the
> size is shown as 1073MB instead of 120GB as it should.
>
> I have another SSD here that would have an identical partition table,
> at 1 point it was an exact clone.
>
> There are multiple partitions, but the main one is the one with
> important data, and it is an ext4 filesystem.
>
> Is there any hope of recovery?
https://www.cgsecurity.org/wiki/TestDisk
https://www.cgsecurity.org/wiki/PhotoRec
Good tools.
Martin
Sep 15, 2018, 5:20:04 AM9/15/18
to
I suggest, you first have a look what you have in front of you:
What does 'lshw -c disk' say?
What does 'hdparm -I [device]' say?
Do you have any SCSI and/or disk related errors in your kernel log?
What does 'fdisk -l [device]' say?
Martin
What does 'lshw -c disk' say?
What does 'hdparm -I [device]' say?
Do you have any SCSI and/or disk related errors in your kernel log?
What does 'fdisk -l [device]' say?
Martin
Allen Hoover
Sep 15, 2018, 1:40:04 PM9/15/18
to
On Sat, Sep 15, 2018 at 11:16:18AM +0200, Martin wrote:
> I suggest, you first have a look what you have in front of you:
>
> What does 'lshw -c disk' say?
*-disk
> I suggest, you first have a look what you have in front of you:
>
> What does 'lshw -c disk' say?
description: ATA Disk
product: SPCC Solid State
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 12.2
serial: DA5A076408EE02778745
size: 111GiB (120GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=0003cf43
*-disk
description: ATA Disk
product: SM2246AA-5
physical id: 0.0.0
bus info: scsi@1:0.0.0
logical name: /dev/sdb
version: 0912
serial: (03)5526888-20080228
size: 1023MiB (1073MB)
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512
*-disk
description: ATA Disk
product: ESA3SMD2HSLB120G
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sdc
version: 4B
serial: E20150303710198
size: 111GiB (120GB)
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512
> What does 'hdparm -I [device]' say?
ATA device, with non-removable media
Model Number: SM2246AA-5
Serial Number: (03)5526888-20080228
Firmware Revision: 20120912
Standards:
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 2080 1008
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 15481935
LBA user addressable sectors: 2096640
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 7559 MBytes
device size with M = 1000*1000: 7926 MBytes (7 GB)
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 1 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* Power Management feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
Integrity word not set (found 0x0000, expected 0x4fa5)
> Do you have any SCSI and/or disk related errors in your kernel log?
[184170.852482] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[184170.852808] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[184170.852827] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff8a082a0e4960), AE_NOT_FOUND (20160831/psparse-543)
[184170.852854] ata2.00: ATA-9: SM2246AA-5, 20120912, max UDMA/100
[184170.852858] ata2.00: 2096640 sectors, multi 1: LBA
[184170.853159] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[184170.853177] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff8a082a0e4960), AE_NOT_FOUND (20160831/psparse-543)
[184170.853206] ata2.00: configured for UDMA/100
[184170.853219] ata2: EH complete
[184170.853527] scsi 1:0:0:0: Direct-Access ATA SM2246AA-5 0912 PQ: 0 ANSI: 5
[184170.892902] sd 1:0:0:0: [sdb] 2096640 512-byte logical blocks: (1.07 GB/1024 MiB)
[184170.892972] sd 1:0:0:0: [sdb] Write Protect is off
[184170.892976] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[184170.893006] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[184170.894076] sd 1:0:0:0: Attached scsi generic sg1 type 0
[184170.895638] sd 1:0:0:0: [sdb] Attached SCSI disk
> What does 'fdisk -l [device]' say?
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Martin
Sep 15, 2018, 3:50:04 PM9/15/18
to
Ok, fist I had a look at Google for 'SM2246AA'. There are some hits with exactly the problem you have. I have no real idea, what to make of those. With things like that, you need to know what you, guessing is a bad idea -> Sorry, I'm out at this point.
Am 15.09.2018 um 19:10 schrieb Allen Hoover:
>
> On Sat, Sep 15, 2018 at 11:16:18AM +0200, Martin wrote:
Try to dump its contents using dd. May be try to flash the firmware.
Good luck!
Martin
Am 15.09.2018 um 19:10 schrieb Allen Hoover:
>
> On Sat, Sep 15, 2018 at 11:16:18AM +0200, Martin wrote:
>> I suggest, you first have a look what you have in front of you:
>>
>> What does 'lshw -c disk' say?
>
>>
>> What does 'lshw -c disk' say?
>
>> What does 'hdparm -I [device]' say?
>
>
>> Do you have any SCSI and/or disk related errors in your kernel log?
>
> Following are the messages when the disk is hot plugged:
>
>
> [184170.852482] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [184170.852808] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
> [184170.852827] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff8a082a0e4960), AE_NOT_FOUND (20160831/psparse-543)
> [184170.852854] ata2.00: ATA-9: SM2246AA-5, 20120912, max UDMA/100
> [184170.852858] ata2.00: 2096640 sectors, multi 1: LBA
> [184170.853159] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
> [184170.853177] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff8a082a0e4960), AE_NOT_FOUND (20160831/psparse-543)
> [184170.853206] ata2.00: configured for UDMA/100
> [184170.853219] ata2: EH complete
> [184170.853527] scsi 1:0:0:0: Direct-Access ATA SM2246AA-5 0912 PQ: 0 ANSI: 5
> [184170.892902] sd 1:0:0:0: [sdb] 2096640 512-byte logical blocks: (1.07 GB/1024 MiB)
> [184170.892972] sd 1:0:0:0: [sdb] Write Protect is off
> [184170.892976] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [184170.893006] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
> [184170.894076] sd 1:0:0:0: Attached scsi generic sg1 type 0
> [184170.895638] sd 1:0:0:0: [sdb] Attached SCSI disk
>
>
>
> [184170.852482] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [184170.852808] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
> [184170.852827] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff8a082a0e4960), AE_NOT_FOUND (20160831/psparse-543)
> [184170.852854] ata2.00: ATA-9: SM2246AA-5, 20120912, max UDMA/100
> [184170.852858] ata2.00: 2096640 sectors, multi 1: LBA
> [184170.853159] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
> [184170.853177] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff8a082a0e4960), AE_NOT_FOUND (20160831/psparse-543)
> [184170.853206] ata2.00: configured for UDMA/100
> [184170.853219] ata2: EH complete
> [184170.853527] scsi 1:0:0:0: Direct-Access ATA SM2246AA-5 0912 PQ: 0 ANSI: 5
> [184170.892902] sd 1:0:0:0: [sdb] 2096640 512-byte logical blocks: (1.07 GB/1024 MiB)
> [184170.892972] sd 1:0:0:0: [sdb] Write Protect is off
> [184170.892976] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [184170.893006] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
> [184170.894076] sd 1:0:0:0: Attached scsi generic sg1 type 0
> [184170.895638] sd 1:0:0:0: [sdb] Attached SCSI disk
>
>
>
>> What does 'fdisk -l [device]' say?
>
>
> Disk /dev/sdb: 1023.8 MiB, 1073479680 bytes, 2096640 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
>
>
>
>>
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
>
>
>
>>
>> Martin
>>
>>
>> Am 13.09.2018 um 23:16 schrieb Allen Hoover:
>>> I have an SSD that has some serious issues. It contains files that
>>> are fairly important to recover. The user had not done backups quite
>>> recently.
>>>
>>> If I view the SSD in parted, it says unrecognized disk label, and the
>>> size is shown as 1073MB instead of 120GB as it should.
>>>
>>> I have another SSD here that would have an identical partition table,
>>> at 1 point it was an exact clone.
>>>
>>> There are multiple partitions, but the main one is the one with
>>> important data, and it is an ext4 filesystem.
>>>
>>> Is there any hope of recovery?
>>>
>>> Please CC me, as I only subscribe to user digest mailing list.
>>>
>>> Thank You!
>>>
But if you are seriously interested in getting your data back, do not alter anything on this device at first. Try a SATA port and/or controller... This is not USB, right? How dies this thing look in your mainboard's BIOS? Try to reset you MB's BIOS.
>>
>>
>> Am 13.09.2018 um 23:16 schrieb Allen Hoover:
>>> I have an SSD that has some serious issues. It contains files that
>>> are fairly important to recover. The user had not done backups quite
>>> recently.
>>>
>>> If I view the SSD in parted, it says unrecognized disk label, and the
>>> size is shown as 1073MB instead of 120GB as it should.
>>>
>>> I have another SSD here that would have an identical partition table,
>>> at 1 point it was an exact clone.
>>>
>>> There are multiple partitions, but the main one is the one with
>>> important data, and it is an ext4 filesystem.
>>>
>>> Is there any hope of recovery?
>>>
>>> Please CC me, as I only subscribe to user digest mailing list.
>>>
>>> Thank You!
>>>
Try to dump its contents using dd. May be try to flash the firmware.
Good luck!
Martin
0 new messages