Hi all, How do I query the system to report the fs types? I know that the RAID is btrfs, just can't remember the / fs. Everything has worked so well. And now it is not. Thanks Andrew On 23/10/19 10:31 pm, Morrie Wyatt via luv-main wrote:
Hi Andrew.
By rebooting, I meant _after_ the fsck, not as a way of performing it.
(Note to David. I did suggest the "-N" dry reporting run option. It could however be a reasonably lengthy report.)
I remember the discussion some time back when you were deciding how to configure your partitions, but don't know what the final outcome was.
The fact that you are getting a console session means that whatever partitions needed to boot the system are mounted, all be it in read only mode. You should be able to run the "mount" command and see what it reports as the "/" partition and its type.
"/dev/md1 on / type ext4 (rw)"
So it is reporting on the machine I have here as being an ext4 partition on a raid (/dev/md1) drive, and is mounted in rw mode.
"/dev/md2 on /home type ext4 (rw)" may not be mountable if there is any need to write to the root "/" partition during the process.
I had a weird issue on an ubuntu machine at home a while back. It would keep offering the same set of ubuntu updates, time and time again. It was only then that I investigated and found that the root partition was in read only mode. So I umounted my /home partition and ran an fsck on the root partition. It found several corrupted inodes, unattached file fragments, wrong link counts etc. Once I confirmed that the fragments were from an unimportant package that had been in the process of being updated, I deleted the contents of /lost+found then ran the mount -o remount and mount -a commands to bring everything back online.
Lo and behold, the updates now installed correctly, and I have had no trouble since. (I hope Murphy wasn't looking in my direction there.)
So as David said, if in doubt, send us details from the -N dry run so we can look for anything likely to go BOOM!
Regards, Morrie.
And as a side note, (vi vs emacs flame wars aside) it is worth investing some time learning at least the basics of vi. It's a very powerful modal editor with a plethora of functions, but to do the basics you only need to learn a handful of them. The reason I say this is that you will find vi on pretty much every variant of linux/unix/BSD etc.
(Obligatory XKCD reference: https://xkcd.com/378/ )
-----Original Message----- From: luv-main [mailto:luv-main-bounces@luv.asn.au] On Behalf Of Andrew Greig via luv-main Sent: Wednesday, 23 October 2019 9:46 PM To: luv-main@luv.asn.au Subject: Re: Power outage today, system fscked
Thanks Morrie,
The problem has survived 4 reboots, my console works so I will run the fsck options.
Cheers
Andrew
On 23/10/19 9:39 pm, Morrie Wyatt via luv-main wrote:
Hi Andrew.
Note: I'm making an assumption that your root partition is an ext4 format. If it's not, then you will need to use the tool for your partition type (assuming it has one).
The reason you can't mount the btrfs partitions is that they need to mount to somewhere on the root partition.
As the root partition mounts "Read only", the system won't let the mount occur. You need to run fsck on the root partition. "fsck /" (see "man fsck" for full details, or look it up on the net if necessary.)
As it's already in read only mode, fsck (or the variant of fsck that matches your root partition type) will happily look for any broken i-nodes, and will reconnect any broken file fragments via their inode number to the "lost+found" directory of the root partition. For the "Hail Mary" option, you can run "fsck -a /" which will run wiithout asking any questions. Before trying the -a option, try the -N option as it is a dry-run oprion, making no changes, but just reporting on what it would do if given free reign.
By default, fsck runs in interactive mode, so it will prompt you at each error it finds.
If you are lucky, nothing critical was open at the time of the power outage. Once the fsck has run its course, "mount -o remount /" will bring the root partition up in rw mode. You can then run a "mount -a" to mount all of the partitions in /et/fstab. Rebooting the machine is your other alternative.
Regards, Morrie.
-----Original Message----- From: luv-main [mailto:luv-main-bounces@luv.asn.au] On Behalf Of Andrew Greig via luv-main Sent: Wednesday, 23 October 2019 8:42 PM To: Andrew Greig via luv-main Subject: Power outage today, system fscked
Hi All,
Two events, Ubuntu update and power outage.
I cannot access my btrfs RAID drives, system reports it is mounted as read only.
Thunderbird is not working browsers are not working
Sane scanner is working
Darktable is reporting as running but not responsive.
KPatience is not working
So, in general, I have a system which boots but the programs are not starting properly. Is this a symptom of LockFiles not reporting correctly?
If I cannot access my RAID drives I am in a world of pain.
Any suggestions on how to solve this would be truly appreciated.
Andrew Greig
_______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
_______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
_______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main