#Unable to (re)mount BTRFS Partition

69 messages · Page 1 of 1 (latest)

final tulip
#

So basically my Drive has been randomly locked up itself like 3 Days (Happened while working on a Coding Project even tho i stil had 12GB left of Disk Space but whatever stuff like this happens)
so i just poweroff the Machine and unplug the Disk and hook up externally and boot up my PC again and to my Suprise it was shown in the list of Drives in Thunar so i click on it and get greeted with a "Superblock" Error so first thing i do is check if i can like mount it to a folder atleast specifically /mnt/tmp which then greets me with this

sudo mount /dev/sdd1 /mnt/tmp
mount: /mnt/tmp: can't read superblock on /dev/sdd1.
       dmesg(1) may have more information after failed mount system call.

afterwards i try seeing if btrfs check can give me any results and well it does give me a few errors but not any that seemingly stick out to me

https://privatebin.net/?74c17101374834b2#ErNyUtq3J6Fu1FifPdUHCUfjbUNFpGz58RWTnjM2CNUU

same with the btrfs rescue command which just tells me all my superblocks are fine and that there is no need to recover

https://privatebin.net/?af930d7d3b28fc27#FSqudMjbTAyhbCgnr3zYZKLRPsKtW9koUgaJRLpSSNh5

which afterwards still trying to mount it with the above same terminal output and now i will get annoyed obviously so i see if my dmesg has something and welp im gonna be honest i have no idea what any of this means X_X

https://privatebin.net/?8e03872f91533dea#CSKuSuvZfNcXizsLKuQiEEyUXyP2kgvWUwCFu4yVUq79

and since i obviously also have no idea how to fix it decided to ask yall :P
now i do wanna say that i am too poor to afford hard drive so my last backup was like from 5 Years Ago which sucks but yea in the worst case ill may just get this atleast X_X
i am just honestly super confused as to how and what exactly is going on and if its even worth fixing it like i do not have the money to go to a rescue data recovery service because it costs like 800€ usually overhere :((((((

grim shardBOT
#

How does the disk result in a smart test

final tulip
grim shardBOT
#

I probably don't know how to fix but running a recent smart test would be helpful for the other people who'll look into it

final tulip
#

here is my smartctl output

#

i did not knew uh how to do it really so i just used the entire disk instead of just sdd1 like usual

grim shardBOT
#

Ya use the entire disk

#

Your disk fails

#

im sorry

#

Your disk is dying

final tulip
#

so no way for me to save it? :(((((

grim shardBOT
#

you need to recover everything as soon as possible

final tulip
#

oof fuck X_X
uh well ill see if a repair shop has open at Monday X_X

dreamy basin
#

before opening: "can't be that bad surely"
after opening: "oh damn it is that bad"

final tulip
#

hey i did not knew :((((

#

its been acting weird since 4 days X_X

#

if i knew before i wouldnt have even used it X_X

#

but i thought i could fix it sadly myself :(((((

#

rip me rescue costs 1500€ X_X

#

i dont have that much money :((((((

grim shardBOT
#

can you see the partition

final tulip
#

uh what?

#

like in Thunar or gparted? >.>

#

well sure i can

grim shardBOT
#

is a partition like sdd1 present and recognised by the kernel

final tulip
#

well uh yea? >.>

#

thats the entire reason why im mounting sdd1

grim shardBOT
#

i would advise to create an image of it

final tulip
#

or like uh always trying to fix sdd1 specifically

final tulip
grim shardBOT
#

if you run the dd command correctly, it's safe

#

also uhh there are other programs that can image a disk

dreamy basin
#

Can you mount the partition read only?

final tulip
final tulip
final tulip
grim shardBOT
#

clonezilla

final tulip
#

but i can honestly wait til monday

#

and like call them

#

and if its actually 1500€ i will just do it with clonezilla

grim shardBOT
#

fair
good luck

final tulip
#

thanks X_X

#

wow now i feel even more stupid :c

#

like i wish i wouldve just called sooner honestlx X_X

dreamy basin
#

there's ddrescue and hddsuperclone too

final tulip
#

then i atleast would not have to wait until monday -.-

dreamy basin
#

data recovery is generally expensive but should probably be less than that

grim shardBOT
#

you could try imaging the disk and see what you can do with it

final tulip
#

if its "just" the PCB its 350€ - 1250€ X_X

#

but i assume its more of a logical error? >.>

#

because those are like 150€ - 500€

#

and besides i also have a spare 2TB SSD he can like put it on as the dead SSD is also a 2TB :P

#

but ugh i really should invest in a External 4TB HDD someday -.-

dreamy basin
#

I would investigate the options above first and see if you can save yourself the money tbh

final tulip
#

well im scared of plugging it back in tbh :((((((((((

#

like what if the reconnection causes it to rot further :(((((((((

dreamy basin
#

a logical issue doesn't turn into a PCB/physical issue (though PCB issues can cause logic errors, afaik)

point is, even if it were to get worse as a result (and it probably won't), it wouldn't be a big deal and make things entirely unrecoverable.

Data recovery professionals have the tools and knowledge to go to some crazy lengths in order to pull data

final tulip
#

woa :000000

dreamy basin
#

I would try using ddrescue first because it's built for these kinds of situations (old as it is), the other one I suggested was more HDD specific ><

final tulip
#

hm ill try ddrescue then? :0

#

is there uh a specific set of commands itd have to use? >.>

dreamy basin
#

but yeah this is going to be a CLI job

final tulip
#

welp time to wait 16 Hours for the image to be created X_X

#

afterall putting 2TB SSD into a Disk Image is uh interesting

final tulip
#

Update: so after getting through 99.61% (yes im not kidding) i actually ran out of space :(

#

deicded to stiill wanna mount it and welp was greeted with this

$ sudo mount 2TBSSD.img /mnt/tmp
[sudo] password for retro-hax:
mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.