- Joined
- Feb 18, 2010
- Messages
- 1,850 (0.36/day)
System Name | Eldritch |
---|---|
Processor | AMD Ryzen 5 5800X3D |
Motherboard | ASUS TUF X570 Pro Wifi |
Cooling | Satan's butthole after going to Taco Bell |
Memory | 64 GB G.Skill TridentZ |
Video Card(s) | Vega 56 |
Storage | 6*8TB Western Digital Blues in RAID 6, 2*512 GB Samsung 960 Pros |
Display(s) | Acer CB281HK |
Case | Phanteks Enthoo Pro PH-ES614P_BK |
Audio Device(s) | ASUS Xonar DX |
Power Supply | EVGA Supernova 750 G2 |
Mouse | Razer Viper 8K |
Software | Debian Bullseye |
I'm undecided whether this belongs here or in the hardware section, so whatever...
Long story short I had to use a busted SATA cable due to A) very important, time-critical reasons, and B) I didn't have another, and I had to hard shutdown because it got disconnected (due to busted cable), this morning I got a new cable and now fuck's shitted up.
EDIT: The drive is a 1TB Seagate Barracuda 7200rpm ST31000523AS.
At boot I'm lucky if BIOS will see it, and I can't boot from it, and if I try to do anything (fsck, etc.) usually spits out
However, mke2fs can (apprently) see things:
I've tried to use various things using a backup superblock, but that usually fails with
Also of note is that the kernel log is downright littered with
But apparently it's able to do enough to tell what partitions it has:
And I'm looking for help.
Treebeard said:There is no curse in Elvish, Entish, or the tongues of men for this treachery.
Long story short I had to use a busted SATA cable due to A) very important, time-critical reasons, and B) I didn't have another, and I had to hard shutdown because it got disconnected (due to busted cable), this morning I got a new cable and now fuck's shitted up.
EDIT: The drive is a 1TB Seagate Barracuda 7200rpm ST31000523AS.
At boot I'm lucky if BIOS will see it, and I can't boot from it, and if I try to do anything (fsck, etc.) usually spits out
Code:
Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3
Could this be a zero-length partition?
Code:
mint@mint ~/Desktop $ sudo mke2fs /dev/sda
mke2fs 1.42 (29-Nov-2011)
/dev/sda is entire device, not just one partition!
Proceed anyway? (y,n) y
Warning: could not erase sector 2: Attempt to write block to filesystem resulted in short write
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
61054976 inodes, 244190646 blocks
12209532 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
7453 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
I've tried to use various things using a backup superblock, but that usually fails with
Code:
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda
Couldn't find valid filesystem superblock.
Also of note is that the kernel log is downright littered with
Code:
Apr 16 21:26:31 mint kernel: [ 51.669184] end_request: I/O error, dev sda, sector 1953524992
Apr 16 21:26:31 mint kernel: [ 51.669188] Buffer I/O error on device sda, logical block 244190624
Apr 16 21:26:31 mint kernel: [ 51.669807] sd 2:0:0:0: [sda] Unhandled error code
Apr 16 21:26:31 mint kernel: [ 51.669811] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Apr 16 21:26:31 mint kernel: [ 51.669816] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 74 70 6d a0 00 00 08 00
But apparently it's able to do enough to tell what partitions it has:
Code:
mint@mint ~/Desktop $ sudo ls -l /dev/sda*
brw-rw---- 1 root disk 8, 0 Apr 16 22:16 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 16 21:33 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 16 21:27 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 16 21:54 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 16 21:27 /dev/sda4
And I'm looking for help.
Last edited: