10 Sep
2020
10 Sep
'20
11:03 p.m.
Anno domini 2020 Thu, 10 Sep 18:47:10 -0400
BorgLabs - Kate Draven via tde-users scripsit:
On Thursday 10 September 2020, deloptes wrote:
ext3/ext4 is never readonly, even when mounted readonly. For forensics you always have to
do a 1:1 copy, make it writeprotect and then mount the image.
Nik
William Morder via tde-users wrote:
That's a
good point. Mount it as a readonly.
Wouldn't that work. You might not even need to run an fsck.
That's how it works with JFS. I intend to try all other avenues for data
recovery, before I try
performing surgery on the hard disk itself. That is a last option, I
think.
ok, but if you use the badblocks command to identify potential bad block,
you could then easily get the filesystem mounted.
---------------------------------------------------------------------
Kate
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
_______________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...