| View previous topic :: View next topic |
| Author |
Message |
198728
l33t
Joined: 08 Apr 2009
Posts: 693
|
 Posted: Sun May 02, 2021 6:34 pm Post subject: HDD disapear after chroot |
 |
|
Hi, I'm moving an hdd sata drive to a new computer and I'm using chroot to change nvidia driver due an upgrade.
I don't know what's happening really, but now I can't see my drive in the bios, and I can't chroot into it again, to try to solve the issue. 
Any suggestion?  |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54387
Location: 56N 3W
|
| Posted: Sun May 02, 2021 6:50 pm Post subject: |
|
|
mrl4n,
Not all SATA ports are created equal.
In the BIOS, ensure the SATA ports are set to SATA mode, not legacy or IDE or Compatibility.
Often, the BIOS can only see the first two, if its not set to SATA mode.
Even that's not enough. Some BIOSes can only boot from the first four SATA ports anyway.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
198728
l33t
Joined: 08 Apr 2009
Posts: 693
|
| Posted: Sun May 02, 2021 10:25 pm Post subject: |
|
|
NeddySeagoon
thanks for your reply.
I don't modify bios setup, and before chroot I saw it.
I booted my pc with another linux distro, and I can see only 2 hdd instead 3.
I think chroot was its last job, and now I lost more than 4 years of data. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54387
Location: 56N 3W
|
| Posted: Mon May 03, 2021 10:23 am Post subject: |
|
|
mrl4n,
I suspect its still there, you just can't see it.
What does dmesg show when the drive does not appear. Are there any errors?
Put the whole thing onto a pastebin site and post a link.
It can be lots of things but we can start with dmesg.
Cables, the SATA port on the motherboard, the kernel ... they all need to be looked at before concluding that the drive has failed.
Oh, what does tell?
Post all that then we can decide what to poke at next.
Oh, read my signature too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
198728
l33t
Joined: 08 Apr 2009
Posts: 693
|
| Posted: Mon May 03, 2021 1:21 pm Post subject: |
|
|
Here dmesg results.
Maybe you are right
| Code: | ls -l /dev/sdb
brw-rw---- 1 root disk 8, 16 May 3 13:46 /dev/sdb |
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54387
Location: 56N 3W
|
| Posted: Mon May 03, 2021 2:47 pm Post subject: |
|
|
mrl4n,
The kernel only sees SATA links on ata1 and ata3.
| Code: | [ 4.853519] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 4.853550] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) |
and the drives are
| Code: | [ 4.859210] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 1B6Q PQ: 0 ANSI: 5
[ 4.859457] scsi 2:0:0:0: Direct-Access ATA WDC WD10EZEX-08M 1A01 PQ: 0 ANSI: 5 |
The partition are.
| Code: | [ 4.879459] sda: sda1 sda2 < sda5 sda6 sda7 sda8 >
[ 4.902752] sdb: sdb1 |
Your Bluetooth is missing firmware.
| Code: | | [ 43.622572] Bluetooth: hci0: Intel reset sent to retry FW download |
As you have a third drive, shut down the PC, switch of the PSU but leave it connected to the mains power as you want it to be 'earthed'.
Open the case and touch some bare metal, in case you are carrying a static charge. This discharges you, so you won't do any static damage to the electronics you are about to touch.
Find the data cable to the third HDD. Disconnect it and reconnect it both ends. Twice. This 'wipes' the contacts.
Repeat with with the power cable. Now test. Don't forget the PSU power switch.
This 'wiping' the contacts, if it works, is not usually a long term fix. Plan on a replacement SATA dada cable unless it wasn't connected properly in the first place.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
198728
l33t
Joined: 08 Apr 2009
Posts: 693
|
| Posted: Mon May 03, 2021 3:21 pm Post subject: |
|
|
NeddySeagoon
thanks for your support, really appreciated.
I saw the result of dmesg and understand it.
The cable is a new one, like all hardware in this computer; I know there is an hardware error, yesterday I quickly installed that distro just to check sata drive missing.
I'm changing the cable with a new one directly
UPDATED
with a new cable now I see all disks in bios and in the mounted OS. (/dev/sdb it's 1 TB disk, but system read only 134MB)
Now dmesg give me a new alert
| Code: | ata2.00: exception Emask 0x0 SAct 0x5 SErr 0x0 action 0x0
[ 19.158412] ata2.00: irq_stat 0x40000008
[ 19.158413] ata2.00: failed command: READ FPDMA QUEUED
[ 19.158415] ata2.00: cmd 60/08:00:00:08:84/00:00:00:00:00/40 tag 0 ncq dma 4096 in
res 41/40:08:00:08:84/00:00:00:00:00/00 Emask 0x409 (media error) <F>
[ 19.158415] ata2.00: status: { DRDY ERR }
[ 19.158416] ata2.00: error: { UNC }
[ 19.160902] ata2.00: configured for UDMA/133
[ 19.160908] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
[ 19.160909] sd 1:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 19.160910] sd 1:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
[ 19.160912] sd 1:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 84 08 00 00 00 08 00
[ 19.160913] blk_update_request: I/O error, dev sdb, sector 8652800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 19.160915] Buffer I/O error on dev sdb3, logical block 0, async page read
|
|
|
| Back to top |
|
|
|
Installing Gentoo
