[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Re: [LUG] Only two weeks to stop your medical records being available
- To: list@xxxxxxxxxxxxx
- Subject: Re: [LUG] Only two weeks to stop your medical records being available
- From: comrade meowski <mr.meowski@xxxxxxxx>
- Date: Wed, 9 Jun 2021 14:28:47 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JXAjba41AJ2Dn5cutmoJXXFRmoCObXo9wgjxGM/4uUg=; b=WtC0+BbTcYsWVSAPbXyVOUUA8O0lHYBNs3XL3evQjIU8rZcE9T9VVL8vFZGCf5KKmEL9gxOsB4dUhRZYiuwDcuGxsETJLQyIdztyFMvRADIrH6athQB9qVgbLuosq8qHbnJRN1Jyn+yuYx0hkj47/bGC/lyVKuFA8GU9/f044Ot3qiB6qSNzcOdj9TzXk8b5vsJ6I2HOHtAo4Pbt7ke7UjdFpnQnPoz3WxAQZhVEJrHYzybnXR5IXx3aqBm/0cDsruMi1zWU1zD8+G+m1GUHY2E3iiGf/ybFVrxsh1hZ4QooE/K6Vi9pBHPVGkdgyHZACUuaBJZKSgBK+6tFLmRRhg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kISo2gBZulpJsqxqZB8xOX8JVvG8kPRTv+v8RuJdmIg3f5eW3ar7I+SUvzLGS4M+K1WIaPK7jut71mx2b0nnxwwNBzWU3u/UUWsoUsxygT0a3JDKguMyleHorw+N1XnTbm+8fgcRj7Wrlpuk7qbu5N7wk5y4BE2PVRrhTDL2CNcIfLueNsbrs9RC6prxfrwC0Um4Glx42exbIGFeC2Cp9DoMeFnBc2uq+sl4Em0mnhqdEUSWKbt0vfI/d01R3ldyNQ8cePXyXS+XjinkvZrYzW3nSU6oTspnRH1lXKiF6NIo3Gi3/KcFBY/w9mFSWsK7vkFyzAH1JFrzI5k/Y48pOA==
- Content-language: en-GB
- Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dcglug.org.uk; s=1618045561; h=Sender:Content-Type: Content-Transfer-Encoding:Reply-To:List-Subscribe:List-Help:List-Post: List-Unsubscribe:List-Id:Subject:MIME-Version:In-Reply-To:Date:Message-ID: From:References:To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner:List-Archive; bh=ocz04881+EiysO1h7Kav2kwTJauSqCFwivV/kBlH92s=; b=V/PykF2Mz+Ma03bKSahiCgGoE ighONj+5fub6B2M76gvvWtByv+zyTkXEymU78VJgYNW8w0idAtWiHgyatSRF8PVlJ8Qjw3fEJUgVX WEb31gbeabzedCPtC0smOBi1KPehvqNqdxi+EpoEYniuwedmYULWlCoYf0TC7fWJkb6SQ=;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=live.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JXAjba41AJ2Dn5cutmoJXXFRmoCObXo9wgjxGM/4uUg=; b=H1s8GHnS5ftWDruApYcvY28UvKNmCUzlmqHS/VBWCAVg0Y9rIU+ChI9az2bFFDKBhaxaswXedugtxdbGUr78I09cRcobfRYJQW9jmGaiwUk3GrDJEYJ6VyyNNdY5xOFJvuAnwqBXG4/TaeaxljFG5LoK9LYMRxX5mXZZ2gWN8SYKvLU5j6Zqsr0pEYbGLOZ7pR7Agcgim9EcPdnwmneas1MAzw1afFQBcTNgTjbgdaqIedZJXz1o9xK0K0jdfzOOWkX5nwWM/JgFnL4y442i1rGIZOWgutooHZm80+Dpck8OMKT7TztalCjyrO/DpIXUuIUHrry3krWatDWGl2bxbQ==
On 09/06/2021 14:17, james kilty wrote:
Hello
I had an accident and need help to remount a ssd.
https://www.slashroot.in/understanding-file-system-superblock-linux may
contain the right information but I was hoping there might be an easier
way given that I "exited with non-zero exit status".
Full message on attempting to mount:
Error mounting /dev/dm-0 at
/media/james/10bc55ec-8a6c-4b4d-ae32-93e51a0fdf7c: Command-line `mount
-t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-0"
"/media/james/10bc55ec-8a6c-4b4d-ae32-93e51a0fdf7c"' exited with
non-zero exit status 32: mount: /dev/mapper/mint--vg-root: can't read
superblock
Basically I wanted to shut down to move my computer to another room as
the battery is bad. My usual computer after POST went to a tab named
recovery which gave me the error "cannot read ROM". In the meantime I
took out my ssd and put it in a caddy and mounted successfully after
some research. I used the GUI to unmount but it went on and on telling
me to wait. Unfortunately I managed to unplug the computer, hence the
problem.
Is there a quick fix? The ssd is ext4.
Fsck the disk partitions before mounting, it's telling you that the
filesystem was damaged. It's a LVM based Mint setup so you'll have to
negotiate the confusing partitioning structure with your actual ext4
partitions ending up getting mounted under /dev/mapper/mint-blah-blah.
sudo fsck.ext4 -fy /dev/mapper/mint--vg-root
Is probably about what you need to run from the working host to check
the partition currently troubling you - I'd fsck the rest of them on the
same disk as well.
You forgot to change the Subject so we'll have mangled everyone's
threading now...
--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dcglug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq