SSD Died, Detected by BIOS but not OS Unicorn Meta Zoo #1: Why another podcast? ...
The weakest link
What is it called when you ride around on your front wheel?
Raising a bilingual kid. When should we introduce the majority language?
Check if a string is entirely made of the same substring
Is there really no use for MD5 anymore?
Will I lose my paid in full property
How can I wire a 9-position switch so that each position turns on one more LED than the one before?
English or Hindi translation of Vyasa Smriti
Where was the County of Thurn und Taxis located?
Obeylines and gappto from etoolbox
How would this chord from "Rocket Man" be analyzed?
First instead of 1 when referencing
How to keep bees out of canned beverages?
`microtype`: Set Minimum Width of a Space
Drawing a german abacus as in the books of Adam Ries
Suing a Police Officer Instead of the Police Department
How to not starve gigantic beasts
Sharepoint Designer Discontinuation - software to modify existing workflows
Is this homebrew arcane communication device abusable?
Philosophical question on logisitic regression: why isn't the optimal threshold value trained?
Can I criticise the more senior developers around me for not writing clean code?
Crossed out red box fitting tightly around image
Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?
How long after the last departure shall the airport stay open for an emergency return?
SSD Died, Detected by BIOS but not OS
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara“mount: special device /dev/sdc1 doesn't exist” but according to fdisk -l, it doesSDcard /dev/sdb2 is apparently in use by the system; will not make a filesystem hereHarddisk not mounting: not recognized under Devices - UbuntuCan't log in on kali linuxDebian jessie fails to boot - changed the fstab fileSSD died after BSODKali - Live Session has no Install Kali applicationMount command not working, pulling up info page on Ubuntu ServerCannot find windows 10 in grub menu after installing Fedora 24 alongside windowsInstalling Kali Linux, stuck at “Detect and mount CD-Rom”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
So few days ago I was playing a game. When I was finished with it, I closed the game and to my avail, everything was frozen (I could only move my mouse). I assumed silly Windows 10 simply crashed, so I force shutdown my computer by holding the power button.
I then started it. The BIOS was taking minutes to load, which was unusual. I assumed something might have happened with the motherboard, so I opened the laptop and went through the components, narrowing down the problem.
It ended at the 128GB Kingston mSATA SSD drive which, when removed, made BIOS boot instantly. The mSATA had windows and was not bootable, so I bought a mSATA to USB adapter and booted KALI up via USB.
When booted, I connected the SSD with the adapter to the USB hub and when running lsblk I get the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 450M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 464.5G 0 part /media/root/BCB22D59B22D1A02
└─sda5 8:5 0 786M 0 part
sdb 8:16 1 29G 0 disk
└─sdb1 8:17 1 29G 0 part /lib/live/mount/medium
sdc 8:32 0 119.2G 0 disk
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 2.5G 1 loop /lib/live/mount/rootfs/filesystem.squashfs
The drive I am going after is sdc, which clearly does not have a partition. When running lsblk -o MAJ:MIN,NAME,KNAME,FSTYPE,MODEL,SIZE,TYPE,MOUNTPOINT,STATE I get the following output for my sdc drive:
8:32 sdc sdc SABRENT 119.2G disk offline
I used the "Disks" program included in KALI and it shows the following information.
Almost everything I try leads me to "No such device or address found." error in linux. For example, when I try to create an image of the device via "Disks" program. Using Windows software to recover it is impossible since the drive is not recognized at all there.
Is there a way I can go about recovering my data?
Thanks in advance!
linux ssd hardware-failure kali-linux
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
add a comment |
So few days ago I was playing a game. When I was finished with it, I closed the game and to my avail, everything was frozen (I could only move my mouse). I assumed silly Windows 10 simply crashed, so I force shutdown my computer by holding the power button.
I then started it. The BIOS was taking minutes to load, which was unusual. I assumed something might have happened with the motherboard, so I opened the laptop and went through the components, narrowing down the problem.
It ended at the 128GB Kingston mSATA SSD drive which, when removed, made BIOS boot instantly. The mSATA had windows and was not bootable, so I bought a mSATA to USB adapter and booted KALI up via USB.
When booted, I connected the SSD with the adapter to the USB hub and when running lsblk I get the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 450M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 464.5G 0 part /media/root/BCB22D59B22D1A02
└─sda5 8:5 0 786M 0 part
sdb 8:16 1 29G 0 disk
└─sdb1 8:17 1 29G 0 part /lib/live/mount/medium
sdc 8:32 0 119.2G 0 disk
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 2.5G 1 loop /lib/live/mount/rootfs/filesystem.squashfs
The drive I am going after is sdc, which clearly does not have a partition. When running lsblk -o MAJ:MIN,NAME,KNAME,FSTYPE,MODEL,SIZE,TYPE,MOUNTPOINT,STATE I get the following output for my sdc drive:
8:32 sdc sdc SABRENT 119.2G disk offline
I used the "Disks" program included in KALI and it shows the following information.
Almost everything I try leads me to "No such device or address found." error in linux. For example, when I try to create an image of the device via "Disks" program. Using Windows software to recover it is impossible since the drive is not recognized at all there.
Is there a way I can go about recovering my data?
Thanks in advance!
linux ssd hardware-failure kali-linux
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
When you have the drive connected to the motherboard, does it eventually boot? Does the BIOS recognize it at all?
– LawrenceC
Aug 26 '18 at 3:03
add a comment |
So few days ago I was playing a game. When I was finished with it, I closed the game and to my avail, everything was frozen (I could only move my mouse). I assumed silly Windows 10 simply crashed, so I force shutdown my computer by holding the power button.
I then started it. The BIOS was taking minutes to load, which was unusual. I assumed something might have happened with the motherboard, so I opened the laptop and went through the components, narrowing down the problem.
It ended at the 128GB Kingston mSATA SSD drive which, when removed, made BIOS boot instantly. The mSATA had windows and was not bootable, so I bought a mSATA to USB adapter and booted KALI up via USB.
When booted, I connected the SSD with the adapter to the USB hub and when running lsblk I get the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 450M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 464.5G 0 part /media/root/BCB22D59B22D1A02
└─sda5 8:5 0 786M 0 part
sdb 8:16 1 29G 0 disk
└─sdb1 8:17 1 29G 0 part /lib/live/mount/medium
sdc 8:32 0 119.2G 0 disk
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 2.5G 1 loop /lib/live/mount/rootfs/filesystem.squashfs
The drive I am going after is sdc, which clearly does not have a partition. When running lsblk -o MAJ:MIN,NAME,KNAME,FSTYPE,MODEL,SIZE,TYPE,MOUNTPOINT,STATE I get the following output for my sdc drive:
8:32 sdc sdc SABRENT 119.2G disk offline
I used the "Disks" program included in KALI and it shows the following information.
Almost everything I try leads me to "No such device or address found." error in linux. For example, when I try to create an image of the device via "Disks" program. Using Windows software to recover it is impossible since the drive is not recognized at all there.
Is there a way I can go about recovering my data?
Thanks in advance!
linux ssd hardware-failure kali-linux
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
So few days ago I was playing a game. When I was finished with it, I closed the game and to my avail, everything was frozen (I could only move my mouse). I assumed silly Windows 10 simply crashed, so I force shutdown my computer by holding the power button.
I then started it. The BIOS was taking minutes to load, which was unusual. I assumed something might have happened with the motherboard, so I opened the laptop and went through the components, narrowing down the problem.
It ended at the 128GB Kingston mSATA SSD drive which, when removed, made BIOS boot instantly. The mSATA had windows and was not bootable, so I bought a mSATA to USB adapter and booted KALI up via USB.
When booted, I connected the SSD with the adapter to the USB hub and when running lsblk I get the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 450M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 464.5G 0 part /media/root/BCB22D59B22D1A02
└─sda5 8:5 0 786M 0 part
sdb 8:16 1 29G 0 disk
└─sdb1 8:17 1 29G 0 part /lib/live/mount/medium
sdc 8:32 0 119.2G 0 disk
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 2.5G 1 loop /lib/live/mount/rootfs/filesystem.squashfs
The drive I am going after is sdc, which clearly does not have a partition. When running lsblk -o MAJ:MIN,NAME,KNAME,FSTYPE,MODEL,SIZE,TYPE,MOUNTPOINT,STATE I get the following output for my sdc drive:
8:32 sdc sdc SABRENT 119.2G disk offline
I used the "Disks" program included in KALI and it shows the following information.
Almost everything I try leads me to "No such device or address found." error in linux. For example, when I try to create an image of the device via "Disks" program. Using Windows software to recover it is impossible since the drive is not recognized at all there.
Is there a way I can go about recovering my data?
Thanks in advance!
linux ssd hardware-failure kali-linux
linux ssd hardware-failure kali-linux
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
edited Jan 21 '18 at 16:16
Smokesick
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
asked Jan 19 '18 at 16:29
SmokesickSmokesick
113
113
When you have the drive connected to the motherboard, does it eventually boot? Does the BIOS recognize it at all?
– LawrenceC
Aug 26 '18 at 3:03
add a comment |
When you have the drive connected to the motherboard, does it eventually boot? Does the BIOS recognize it at all?
– LawrenceC
Aug 26 '18 at 3:03
When you have the drive connected to the motherboard, does it eventually boot? Does the BIOS recognize it at all?
– LawrenceC
Aug 26 '18 at 3:03
When you have the drive connected to the motherboard, does it eventually boot? Does the BIOS recognize it at all?
– LawrenceC
Aug 26 '18 at 3:03
add a comment |
1 Answer
1
active
oldest
votes
When lsblk shows the device, then the system known about it. I suggest to use the traditional fdisk program in order the examine existing partitions, if existing or to recreate such ones if not more existing. According to your information, the partition structure of your disk is lost. I ignore why.
answered 23 hours ago
Claude FrantzClaude Frantz
846
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1287152%2fssd-died-detected-by-bios-but-not-os%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When lsblk shows the device, then the system known about it. I suggest to use the traditional fdisk program in order the examine existing partitions, if existing or to recreate such ones if not more existing. According to your information, the partition structure of your disk is lost. I ignore why.
answered 23 hours ago
Claude FrantzClaude Frantz
846
add a comment |
When lsblk shows the device, then the system known about it. I suggest to use the traditional fdisk program in order the examine existing partitions, if existing or to recreate such ones if not more existing. According to your information, the partition structure of your disk is lost. I ignore why.
answered 23 hours ago
Claude FrantzClaude Frantz
846
add a comment |
When lsblk shows the device, then the system known about it. I suggest to use the traditional fdisk program in order the examine existing partitions, if existing or to recreate such ones if not more existing. According to your information, the partition structure of your disk is lost. I ignore why.
answered 23 hours ago
Claude FrantzClaude Frantz
846
When lsblk shows the device, then the system known about it. I suggest to use the traditional fdisk program in order the examine existing partitions, if existing or to recreate such ones if not more existing. According to your information, the partition structure of your disk is lost. I ignore why.
answered 23 hours ago
Claude FrantzClaude Frantz
846
answered 23 hours ago
Claude FrantzClaude Frantz
846
answered 23 hours ago
Claude FrantzClaude Frantz
846
answered 23 hours ago
Claude FrantzClaude Frantz
846
846
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1287152%2fssd-died-detected-by-bios-but-not-os%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
When you have the drive connected to the motherboard, does it eventually boot? Does the BIOS recognize it at all?
– LawrenceC
Aug 26 '18 at 3:03