/home suddenly doesn't mount

Yesterday 12.3 on Dell D630 went to emergency mode. looking at the journalctl output it says /home won’t mount. Trying to manually mount /dev/sda3 to /home just sits there.

smartctl says it passes, i have not yet run the long test on it.

fdisk -l shows all three partitions there, sda1, sda2, sda3. SDA3 is brtfs.

I’ve tried recovery mode and it does the same thing. I am going to kick off the long test but searching finds many threads with similar situations but none that it’s just one partition.

Anyone have any suggestions? There is a letter to an attorney I’d rather not lose if it’s possible. as a last resort i can throw it on my sata>USB adapter and try to get it but wondered where I should start with fixing this issue.

On 2013-10-09 03:36, troykent wrote:
>
> Yesterday 12.3 on Dell D630 went to emergency mode. looking at the
> journalctl output it says /home won’t mount. Trying to manually mount
> /dev/sda3 to /home just sits there.

Run fsck on it, while umounted.

>
> smartctl says it passes, i have not yet run the long test on it.
>
> fdisk -l shows all three partitions there, sda1, sda2, sda3. SDA3 is
> brtfs.

Home is the btrfs? Too bad :frowning:


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

I’m not sure why… but after running gparted and doing a repair it gave me the same response that btrfsck did… but after restarting it came up normally??

If anyone has any tips i’m all ears. I’m running the long smart test now.

I also found this thread: https://bbs.archlinux.org/viewtopic.php?pid=1322132

It had tips for some commands I had not found after searching for about 2 hours. extent tree was one of my errors that btrfsck reported.

On 2013-10-09 04:36, troykent wrote:

> It had tips for some commands I had not found after searching for about
> 2 hours. extent tree was one of my errors that btrfsck reported.

Well, you have hit on one of the reasons why many of us hesitate to use
btrfs.

If your partition is still failing, the btrfs devs are interested to
know about it in order to develop a better fsck.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

I’m backing up the data and replacing btrfs with ext4.

After using gparted > check feature it looks like the repair fails. However when I reboot it comes up.

Once I restart the laptop again it goes back to emergency mode. I don’t really want to use gparted everytime I start it up.

where do i contact the btrfs devs?

On 2013-10-09 14:16, troykent wrote:

> where do i contact the btrfs devs?

Bugzilla, with copy to Jeff Mahoney, I think.

openSUSE:Submitting bug
reports

But obviously, if you reformat the disk, they can not obtain the info.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Please stop this. If you’d actually followed btrfs you wouldn’t write this. Read this: **btrfs is not unstable. DOT.**​

To the OP: wait a bit, until some member using btrfs / having deeper knowledge of btrfs drops in.

On 2013-10-09 21:46, Knurpht wrote:

> Please stop this. If you’d actually followed btrfs you wouldn’t write
> this. Read this: *btrfs is not unstable. DOT.*​

He has 12.3. That version’s btrfs is not considered stable.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Are you telling me openSUSE 12.3 was released with unstable filesystem software? Come on.
The biggest point made at release time, was that supporting it was still hard due to not many of us using it yet. But stable it was, otherwise it would not have been added.

Yep.

Any FS can fail but the tools to fix it are not mature for btrfs, at least on 12.3

This is a prime example of the problem.

On 2013-10-10 20:16, gogalthorp wrote:
>
> Yep.
>
> Any FS can fail but the tools to fix it are not mature for btrfs, at
> least on 12.3
>
>
> This is a prime example of the problem.

Just my point.

That’s why I asked the OP to create a bugzilla; I know (because the dev
asked directly for it in a mail thread on factory) that the tool is
unfinished, and that they want to study failure cases to know what they
have to add to the tool.

If a btrfs partition fails in a manner that the fsck tool is unable to
recover, the only way to solve is backup, reformat, restore. With a
bugzilla ASAP so that they can study it.

Unfortunately, I have no idea what data they require for the study, nor
how fast they will respond to the bugzilla - I understand the person
having the problem will usually be in a hurry.

And they may say that you have to upgrade to the most recent version…


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))