01-13-2023, 03:33 AM
Today my phone went to a black screen after booting, it was just a filesystem issue easy to fix by running fsck maually.
I "blogged" about it in case it can help someone someday:
https://mdk.fr/blog/black-screen-at-boot...phone.html
But I though, why asking a user to fsck manually on a phone? Is there an option Mobian could enable to just do the fsck if needed? It's not that simple as it'll still ask the user to fix or not to fix, like:
Which I really never understood to be honest, as I'm not training myself to remember the inode number of each of my files, and even if I remembered, I don't imagine answering "no" here... Like "no no, I don't like this file anyway, it does not deserve to be fixed, keep it in its bad state on the filesystem, that'll teach him."
I "blogged" about it in case it can help someone someday:
https://mdk.fr/blog/black-screen-at-boot...phone.html
But I though, why asking a user to fsck manually on a phone? Is there an option Mobian could enable to just do the fsck if needed? It's not that simple as it'll still ask the user to fix or not to fix, like:
Code:
Block bitmap differences: -(392704--392976) -(1246016--1246019) -(1606912--1607056) -(1607776--1607792) -(1609536--1609552) -(1611200--1611216) -(1611360--1611376) -(1621504--1621907) -1722548 -(2034240--2034256) -(2036608--2036694) -(2039808--2043903) -(2054144--2054263) -(2058240--2060287) -(2061312--2061823) -(2230912--2230945) -2455149 -(2455162--2455163) -2455612 -(2556160--2556225) -(2556352--2556384) -(2556672--2556737) -(2556832--2556848) -(2556864--2556880) -(2562304--2562433) -(2563328--2563521) -(2563584--2563729) -(2570359--2570366) -(2761279--2761286) -(2790656--2790880) -(2790912--2791104) -(2792192--2792272) -(2792448--2792528) -(2795904--2795952) -(2796224--2796240) -(2796416--2796480) -(2796512--2796528) -(2798336--2798368) -(2799488--2799520) -(2800192--2800224) -(2800448--2800464) -(2800576--2800592) -(2801280--2801296) -(2802112--2802128) -(2802464--2802480) -(2803072--2803088) -(2803904--2803920) -(2807072--2807088) -(2807200--2807216) -(2829440--2829539) -(2980568--2980576) -(3067392--3067748) -(3080224--3080240) -(3080576--3080688) -3089408 -(3092480--3092800) -(3115264--3115300) -(3272704--3273637) -(3274752--3276799) -(3310432--3310448) -(3321247--3321253) -(3346048--3346084) -(3582208--3582353) -3794232 -3794237 -(3817472--3821567) -(3827712--3829759) -(3831808--3833855) -(3859377--3859385) -(3953152--3953281) -(3963799--3963808) -(3986432--3986786) -(4143872--4144034) -(4145408--4145570) -(4191232--4191556) -(4226823--4226825) -(4235200--4235216) -(4752448--4752464) -(4789960--4790091) -(4800710--4801025) -(4814071--4814080) -(4846254--4846409) -(4852416--4852465) -(4854432--4854448) -(4883456--4883729) -(5339966--5339967) -(5397760--5397872) -(5822464--5822579) -(5822976--5823280) -(6432960--6432992) -(6434688--6434768) -(6434784--6434800) -(6439936--6440447) -(6441472--6441490) -(6791680--6792191) -(6800832--6800867) -(6858368--6858400) -(7118729--7118736) -(7144448--7144480) -(7146432--7146448) -(7154432--7154609) -(7170048--7173750) -(7174144--7174400) -(7444480--7446527)
Fix<y>? yes
Free blocks count wrong for group #11 (15917, counted=16190).
Fix<y>? yes
Free blocks count wrong for group #38 (19424, counted=19428).
Fix<y>? yes
Free blocks count wrong for group #49 (24171, counted=24788).
Fix<y>? yes
Free blocks count wrong for group #52 (9990, counted=9991).
Fix<y>? yes
Free blocks count wrong for group #62 (16515, counted=23395).
Fix<y>? yesWhich I really never understood to be honest, as I'm not training myself to remember the inode number of each of my files, and even if I remembered, I don't imagine answering "no" here... Like "no no, I don't like this file anyway, it does not deserve to be fixed, keep it in its bad state on the filesystem, that'll teach him."