You are not logged in.
Pages: 1
i have the ssd mounted properly it can be read! however when i go to the file with /home/user/ its a default layout
Desktop Documents Downloads Music Videos
i know my files are there i was able to cd into Pictures and recover them and a few others i could remember the directory names of! further more when i cd into the folders that are missing the rest of the folders and files are viable, this happens both with the ls -la command and any file explorer
last thing i could think of was i tried a fschk on it but everywhere i read they should be gone gone but ive been able to recover them whats going on?!
Last edited by Banshee_Cass (2024-09-02 17:54:33)
Offline
i ran
find | grep Pictures
find: ‘./.local/share/fish/generated_completions’: Input/output error
does this mean there is a file messing with what i can see?
Offline
There's an IO error, check dmesg for what that is.
You should avoid writing to a damaged drive ( https://wiki.archlinux.org/title/SMART ) at all costs, so make a backup/clone onto a healthy drive before even attempting a fixing fsck.
https://wiki.archlinux.org/title/File_recovery
From the symptoms it kinda sounds a if the superblock got corrupted and restoring one of its backups might help you out - you can select one as mount option for ext4, https://man.archlinux.org/man/ext4.5.en#sb=
If this is btrfs, fsck actually isn't at thing.
Offline
There's an IO error, check dmesg for what that is.
You should avoid writing to a damaged drive ( https://wiki.archlinux.org/title/SMART ) at all costs, so make a backup/clone onto a healthy drive before even attempting a fixing fsck.
https://wiki.archlinux.org/title/File_recoveryFrom the symptoms it kinda sounds a if the superblock got corrupted and restoring one of its backups might help you out - you can select one as mount option for ext4, https://man.archlinux.org/man/ext4.5.en#sb=
If this is btrfs, fsck actually isn't at thing.
i think you have me confused, im not writing to a damaged drive i have one im trying to recover the files from...
the files are there just dont show up data is intact too
Offline
everything is there ive recovered a good amount of data i just cant see the directories with ls but can cd and cp no issue
to be more accurate for example the Pictures folder is missing i cant sit at the user folder and expect cp to work but if i cd into Pictures i can see everything else and can then do a cp * to get all the files
Last edited by Banshee_Cass (2024-09-01 10:27:01)
Offline
I do understand your Situation and Task, but using fsck to fix the Filesystem will write on the Drive - it's Not only about you copying files there etc.
Check the integrity of the Drive and in doubt dd_rescue it onto healthy storage.
The try to mount the Partition read-only using an alternative Superblock and/or fsck IT to fix the dirtrees.
None of this ist applicable to btrfs, ie elaborate in the affected FS because that's very relevant Here.
Offline
I do understand your Situation and Task, but using fsck to fix the Filesystem will write on the Drive - it's Not only about you copying files there etc.
Check the integrity of the Drive and in doubt dd_rescue it onto healthy storage.The try to mount the Partition read-only using an alternative Superblock and/or fsck IT to fix the dirtrees.
None of this ist applicable to btrfs, ie elaborate in the affected FS because that's very relevant Here.
umm... im not interested in attempting to save the old ssd? its health was at 55%! i attempted to use a live boot of clonezilla to get my data but it didnt work so thats when i ran the fschk, its connected like a normal usb its accessable i just cant see the files its like hidden but the ls -a flag doesnt show anything. now i might be naive but i was really hoping for a command to let me see these directories to recover them and deal with the possible data corruption in the files (if any so far no) once its actually on my computer would that be achievable?
if your claim is that its not reading cause of how its mounted then im just a lil dumb n dont know how to fix that :v
thank you so much for yall time btw
Last edited by Banshee_Cass (2024-09-01 16:33:43)
Offline
You mean like a magic oneliner to save data from a corrupted filesystem on a dying disk?
From the symptoms it kinda sounds a if the superblock got corrupted and restoring one of its backups might help you out - you can select one as mount option for ext4, https://man.archlinux.org/man/ext4.5.en#sb=
You also do not have to "save the old ssd" but sanitize the filesystem and you best do so w/o using a broken drive, ie. dump it somewhere else (can be as an image) and attempt to fsck that image (iff this is ext4, again: the actual filesystem is INCREDIBLY relevant here)
Edit: also have a close look at testdisc and photorec as last resort, but again: Do not operate on a drive that you already know is fallign apart in front of you.
Last edited by seth (2024-09-01 16:36:22)
Offline
You mean like a magic oneliner to save data from a corrupted filesystem on a dying disk?
From the symptoms it kinda sounds a if the superblock got corrupted and restoring one of its backups might help you out - you can select one as mount option for ext4, https://man.archlinux.org/man/ext4.5.en#sb=
You also do not have to "save the old ssd" but sanitize the filesystem and you best do so w/o using a broken drive, ie. dump it somewhere else (can be as an image) and attempt to fsck that image (iff this is ext4, again: the actual filesystem is INCREDIBLY relevant here)
Edit: also have a close look at testdisc and photorec as last resort, but again: Do not operate on a drive that you already know is fallign apart in front of you.
no my guy i just want to see the directories that are not appearing, once again i am not doing anything with the bloody ssd!
look
asper@Gateway in /run/media/Casper/78f68d78-6c06-473e-bf0a-a8e52ff670e6/@home/casper as ? took 238ms
╰─λ ls -la ./
drwx--x---@ - Casper 31 Aug 21:25 .
drwxr-xr-x - root 1 Oct 2022 ..
drwxr-xr-x - Casper 30 Aug 21:46 .cache
drwxr-xr-x - Casper 31 Aug 16:41 .config
drwxr-xr-x - Casper 9 Sep 2022 .kde4
drwxr-xr-x - Casper 15 Oct 2023 .local
drwxr-xr-x - Casper 14 Aug 18:11 Desktop
drwxr-xr-x - Casper 25 Aug 21:50 Documents
drwxr-xr-x - Casper 29 Aug 05:37 ? Downloads
drwxr-xr-x - Casper 29 Aug 01:42 ? Music
drwxr-xr-x - Casper 31 Aug 20:50 Videos
.rw------- 2.4k Casper 31 Aug 16:42 ? .bash_history
.rw-r--r-- 21 Casper 8 Jan 2022 ? .bash_logout
.rw-r--r-- 183 Casper 7 Jul 2022 ? .profile
…─Casper@Gateway in /run/media/Casper/78f68d78-6c06-473e-bf0a-a8e52ff670e6/@home/casper as ? took 9ms
╰─λ ls -la ./Pictures
drwxr-xr-x - Casper 30 Aug 21:26 .
drwx--x---@ - Casper 31 Aug 21:25 ..
drwxr-xr-x - Casper 13 Aug 17:25 Background
drwxr-xr-x - Casper 11 Aug 08:43 cave
drwxr-xr-x - Casper 16 Mar 14:36 Dad
drwxr-xr-x - Casper 13 Aug 17:24 Icons
drwxr-xr-x - Casper 18 Apr 20:01 MC-Skins
drwxr-xr-x - Casper 30 Aug 16:58 Meme
drwxr-xr-x - Casper 13 Aug 17:24 Selfie
THERE IS NO PICTURES FILE BUT I CAN STILL PULL IT UP
now... how would i get it where i can actually see these?
not copy i already have them off and idc if i should or should operator on it thats my dad who i cant bring back from the dead ud be damned if i let em just go! let me ruin my equipment at my leasure
thats everything in the Pictures folder that was there to start with but i think i have some in my Documents which is just like this it doesnt show the file but its there
is there a way to see it
Last edited by Banshee_Cass (2024-09-01 21:23:32)
Offline
i have tried the testdisk it just said nothing could be recovered no surprise :v
photorec is looking promising!
Last edited by Banshee_Cass (2024-09-01 21:27:15)
Offline
I suggest to maybe take a deep breath and relax, maybe wait until tomorrow.
You might perhaps also benefit from https://deepl.com/
1. The filesystem is corrupted.
2. You'll *have* to fix that to access the data through the filesystem (the filenames).
3. But fixing the filesystem inevitably includes write operations.
4. Write operations on a dying disk is detremental to any goal of data rescue - you're causing more harm with them.
You've still failed to address what filesystem we're actually dealing with here.
lsblk -f
If it is ext3/4, you can try to simply mount it using one of the backup superblocks, but that doesn't guarantee there's no further damage to the directory tree entries.
fsck can be able to fix those, though - but
1. that depends on the actual filesystem
2. do not run a writing fsck on broken hardware, you'll destroy more data!
Offline
I suggest to maybe take a deep breath and relax, maybe wait until tomorrow.
You might perhaps also benefit from https://deepl.com/1. The filesystem is corrupted.
2. You'll *have* to fix that to access the data through the filesystem (the filenames).
3. But fixing the filesystem inevitably includes write operations.
4. Write operations on a dying disk is detremental to any goal of data rescue - you're causing more harm with them.You've still failed to address what filesystem we're actually dealing with here.
lsblk -f
If it is ext3/4, you can try to simply mount it using one of the backup superblocks, but that doesn't guarantee there's no further damage to the directory tree entries.
fsck can be able to fix those, though - but
1. that depends on the actual filesystem
2. do not run a writing fsck on broken hardware, you'll destroy more data!
apologize i haven't slept but i think its done and i dont gotta deal with this actual piece of electronic waste
PhotoRec 7.2, Data Recovery Utility, February 2024
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sda - 512 GB / 476 GiB (RO) - SSK Storage
Partition Start End Size in sectors
2 P Linux filesys. data 618496 860516351 859897856 [root]
243156 files saved in /home/Casper/Documents/recup_dir directory.
Recovery completed.
You are welcome to donate to support and encourage further development
https://www.cgsecurity.org/wiki/Donation
and you are correct its a ext4 i looked at some of it and while the names have changed its the data thank you very much <3
Offline
nb. that photorec will recover what it can get hold on, in doubt data fragments (data can fragment on ext4, it's much better than ntfs or let alone fat, but it cannot do magic - esp. not on full partitions)
If you want to return to this (after a good night sleep, maybe) you need to understand that the partition itself is basically just one huge file, you can "copy" it onto another drive (using the error tolerant dd_rescue) and then operate on that image as if it was the partition on the broken disk. With the difference that you can try to run fsck to fix the (unmounte) filesystem/image without having to worry about that breaking more data by writing it to broken hardware.
fsck can also tell whether it was able to recover a file properly or just parts of it.
And for completeness sake and wrt your irritation (and extremely simplifying :
A directory is basically a textfile that has the files inside written into it. This textfile can get corrupted and then the texteditor (ls) stumbles over some weird bytes and ultimately gives up on reading it (or thinks that the file ends here although there's actually more text to read)
That's why you could enter the "Pictures" directory but not see it - the structure is still there, but ls has issues reading the directory "file" before it gets to the "Pictures" line.
Offline
nb. that photorec will recover what it can get hold on, in doubt data fragments (data can fragment on ext4, it's much better than ntfs or let alone fat, but it cannot do magic - esp. not on full partitions)
If you want to return to this (after a good night sleep, maybe) you need to understand that the partition itself is basically just one huge file, you can "copy" it onto another drive (using the error tolerant dd_rescue) and then operate on that image as if it was the partition on the broken disk. With the difference that you can try to run fsck to fix the (unmounte) filesystem/image without having to worry about that breaking more data by writing it to broken hardware.
fsck can also tell whether it was able to recover a file properly or just parts of it.And for completeness sake and wrt your irritation (and extremely simplifying :
A directory is basically a textfile that has the files inside written into it. This textfile can get corrupted and then the texteditor (ls) stumbles over some weird bytes and ultimately gives up on reading it (or thinks that the file ends here although there's actually more text to read)
That's why you could enter the "Pictures" directory but not see it - the structure is still there, but ls has issues reading the directory "file" before it gets to the "Pictures" line.
and since im sure i cause a fair deal of damage to my new file system anything you would recommend i do?
should i run a fsck on it?
Offline
What makes you sure you causes any damage to any *new* filesystem? How?
fsck.ext4 -n /path/to/filesystem
runs an absolute "read-only" check, you can do this anytime* to assess the integrity of the filesystem.
*except on physically broken drives - if the head of a spinning drive breaks off or a SSD overheats and melts because you access it, that's obviously bad news
Whenever you've a physically broken drive there's only one thing you want to do: copy as many bytes as you can get onto a physically not broken drive.
Offline
What makes you sure you causes any damage to any *new* filesystem? How?
fsck.ext4 -n /path/to/filesystem
runs an absolute "read-only" check, you can do this anytime* to assess the integrity of the filesystem.
*except on physically broken drives - if the head of a spinning drive breaks off or a SSD overheats and melts because you access it, that's obviously bad news
Whenever you've a physically broken drive there's only one thing you want to do: copy as many bytes as you can get onto a physically not broken drive.
simple answer discord was barking at me x3
[Vencord] Starting up...
[Vencord] Loading original Discord app.asar
[OpenAsar > Init] OpenAsar nightly-5c875eb
[OpenAsar > Settings] /home/Casper/.config/discord/settings.json {
DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING: true,
MIN_WIDTH: 940,
MIN_HEIGHT: 500,
openasar: { setup: true, quickstart: true },
chromiumSwitches: {},
IS_MAXIMIZED: false,
IS_MINIMIZED: false,
WINDOW_BOUNDS: { x: 967, y: 558, width: 926, height: 495 },
trayBalloonShown: true
}
[OpenAsar > BuildInfo] { releaseChannel: 'stable', version: '0.0.66' }
[OpenAsar > Modules] Checking
Optional module ./ElectronTestRpc was not included.
[OpenAsar > AsarUpdate] Updating...
[OpenAsar > AsarUpdate] Downloaded [Error: EACCES: permission denied, open '/opt/discord/resources/_app.asar'] {
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/discord/resources/_app.asar'
}
mainScreen.UpdaterEvents: UPDATER_HISTORY_QUERY_AND_TRUNCATE
[app] null analytics
mainScreen.on(did-finish-load) false false
(node:457351) UnhandledPromiseRejectionWarning: Error: An object could not be cloned.
at IpcRendererInternal.send (node:electron/js2c/renderer_init:2:11351)
at IpcRendererInternal.<anonymous> (node:electron/js2c/renderer_init:2:10846)
(Use `discord --trace-warnings ...` to show where the warning was created)
(node:457351) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
mainScreen.UpdaterEvents: CHECK_FOR_UPDATES UPDATE_NOT_AVAILABLE
[OpenAsar > Modules] Checking
[OpenAsar > Settings] Saved
might be a vencord thing since i got the files from the broken drive
gonna run
fsck.ext4 -n /path/to/filesystem
command now
Offline
huh... well....
sudo fsck.ext4 -n /dev/nvme0n1p3
e2fsck 1.47.1 (20-May-2024)
Warning! /dev/nvme0n1p3 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/nvme0n1p3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 45102515 extent tree (at level 1) could be narrower. Optimize? no
Inode 46022823 extent tree (at level 1) could be shorter. Optimize? no
Inode 46022824 extent tree (at level 1) could be shorter. Optimize? no
Inode 46022856 extent tree (at level 1) could be shorter. Optimize? no
Inode 46022859 extent tree (at level 1) could be shorter. Optimize? no
Inode 46022962 extent tree (at level 1) could be shorter. Optimize? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached zero-length inode 44847589. Clear? no
Unattached inode 44847589
Connect to /lost+found? no
Pass 5: Checking group summary information
Block bitmap differences: +(1280580--1280583) +(12991261--12991290) -(185635848--185635851)
Fix? no
Free blocks count wrong for group #39 (5231, counted=5235).
Fix? no
Free blocks count wrong for group #396 (434, counted=464).
Fix? no
Free blocks count wrong for group #415 (3361, counted=3362).
Fix? no
Free blocks count wrong for group #1515 (1569, counted=1570).
Fix? no
Free blocks count wrong for group #5665 (4569, counted=4565).
Fix? no
Free blocks count wrong for group #5666 (1758, counted=1757).
Fix? no
Free blocks count wrong (192986048, counted=192986955).
Fix? no
Inode bitmap differences: +44847589
Fix? no
Free inodes count wrong for group #5474 (421, counted=422).
Fix? no
Free inodes count wrong for group #5556 (6220, counted=6221).
Fix? no
Free inodes count wrong (59107799, counted=59107739).
Fix? no
Inode bitmap differences: Group 5474 inode bitmap does not match checksum.
IGNORED.
Group 5556 inode bitmap does not match checksum.
IGNORED.
Block bitmap differences: Group 39 block bitmap does not match checksum.
IGNORED.
Group 396 block bitmap does not match checksum.
IGNORED.
Group 415 block bitmap does not match checksum.
IGNORED.
Group 1515 block bitmap does not match checksum.
IGNORED.
Group 5665 block bitmap does not match checksum.
IGNORED.
Group 5666 block bitmap does not match checksum.
IGNORED.
Orphan file (inode 12) block 39 is not clean.
Clear? no
Failed to initialize orphan file.
Recreate? no
/dev/nvme0n1p3: ********** WARNING: Filesystem still has errors **********
/dev/nvme0n1p3: 833065/59940864 files (0.2% non-contiguous), 46747712/239733760 blocks
deserved >w<
Offline
also just noticed i have programs in my drun that is clearly not installed :v
Offline
a few reboots later
sudo fsck.ext4 -n /dev/nvme0n1p3
e2fsck 1.47.1 (20-May-2024)
Warning! /dev/nvme0n1p3 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/nvme0n1p3: clean, 796835/59940864 files, 48544623/239733760 blocks
so confused but im gonna assume this is good! :3
Offline
[OpenAsar > AsarUpdate] Downloaded [Error: EACCES: permission denied, open '/opt/discord/resources/_app.asar'] {
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/discord/resources/_app.asar'
}
isn't a filesystem error, the discord tries to open (probably for writing) a file the process owning UID/GID has no (probably writing) access to.
The other filesystem errors will have been cleaned up w/ the implicit fsck's during a reboot (ext4 in doubt recovers itself from its journal, typically required after cold reboots)
You could have triggered an auto-correcting check to achieve this, provided 1. the filesystem isn't mounted and 2. the drive isn't falling apart (I assume the nvme is not your dying SSD?)
Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Last edited by seth (2024-09-02 07:30:12)
Offline
[OpenAsar > AsarUpdate] Downloaded [Error: EACCES: permission denied, open '/opt/discord/resources/_app.asar'] { errno: -13, code: 'EACCES', syscall: 'open', path: '/opt/discord/resources/_app.asar' }
isn't a filesystem error, the discord tries to open (probably for writing) a file the process owning UID/GID has no (probably writing) access to.
The other filesystem errors will have been cleaned up w/ the implicit fsck's during a reboot (ext4 in doubt recovers itself from its journal, typically required after cold reboots)
You could have triggered an auto-correcting check to achieve this, provided 1. the filesystem isn't mounted and 2. the drive isn't falling apart (I assume the nvme is not your dying SSD?)Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
ye the NVMe is the good one thats been installed any work on the other would have been sda
Last edited by Banshee_Cass (2024-09-02 17:56:33)
Offline
Pages: 1