Search Debian Channel Logs

Wednesday, January 25, 2017

#debian channel featuring TvL2386, dpkg, petn-randall, Rephlexie, Digital, trevorj,

trevorj 2017-01-24 23:46:00
petn-randall: apt/dpkg is however a precious debianism which is why my q is here
Digital 2017-01-24 23:47:37
TvL2386: SynrG petn-randall https://usercontent.irccloud-cdn.com/file/mivq8HRH/IMG_20170125_114330.jpg
TvL2386 2017-01-24 23:50:32
I admit I don't have a clue Digital
petn-randall 2017-01-24 23:50:54
Digital: Can you show us the output of 'apt-cache policy e2fsprogs' to http://paste.debian.net?
SynrG 2017-01-24 23:50:59
trevorj: about those squirrels, a timed aptitude search '~nearth !~sastronomy !~sscience' which returns 21 hits and it took 4.7 seconds. that's too slow for you?
SynrG 2017-01-24 23:51:08
s/a timed/I timed/
TvL2386 2017-01-24 23:51:30
Digital, Isn't the error a response from fsck.ext4 and not that fsck.ext4 is missing?
SynrG 2017-01-24 23:51:36
trevorj: if it's significantly slower, i think the answer is steroids
TvL2386 2017-01-24 23:51:41
maybe /dev/sda6 is missing?
SynrG 2017-01-24 23:52:01
trevorj: aptitude really is the best tool for this
Digital 2017-01-24 23:52:35
petn-randall, apt-cache policy e2fsprogs
Digital 2017-01-24 23:52:38
err https://paste.debian.net/910488/
TvL2386 2017-01-24 23:52:41
Digital, maybe I haven't followed completely, but do you confirm there is no fsck.ext4 binary?
SynrG 2017-01-24 23:53:11
i'll repeat my suggestion earlier ... maybe Digital's initrd is built incorrectly?
Digital 2017-01-24 23:53:12
I don't know, how do i confirm?
SynrG 2017-01-24 23:53:41
wait, wait, wait folks. stop the presses
SynrG 2017-01-24 23:53:46
i looked at the screenshot
TvL2386 2017-01-24 23:53:46
yes
SynrG 2017-01-24 23:53:51
it doesn't say fsck is missing
TvL2386 2017-01-24 23:53:59
exactly
TvL2386 2017-01-24 23:54:00
my point
SynrG 2017-01-24 23:54:03
"fsck exited with status code 0"
Digital 2017-01-24 23:54:11
TvL2386, "ls /sbin/" shows fsck.ext4
TvL2386 2017-01-24 23:54:16
ack
SynrG 2017-01-24 23:54:21
fsck is complaining about /dev/sda6
TvL2386 2017-01-24 23:54:24
I think /dev/sda6 is missing
SynrG 2017-01-24 23:54:32
Digital: why are you telling it to fsck a non-existent device? :)
SynrG 2017-01-24 23:54:39
check your /etc/fstab ... i think it's screwed
SynrG 2017-01-24 23:54:42
!uuid
dpkg 2017-01-24 23:54:42
A Universally Unique IDentifier (UUID) is used to reference disk partitions (among other things). See currently known partition UUIDs with 'blkid'. In /etc/fstab, use "UUID=dead-beef-0420-etc" as the partition name. UUIDs help to cope with device name changes such as hda->sda ( transition) or changes in USB disk order discovery. tools accept PV/VG/LV UUIDs as arguments, use {pv,vg,lv}display to acquire.
Digital 2017-01-24 23:54:58
fsck exited with status code 8, not 0
SynrG 2017-01-24 23:55:17
so i'm blind
SynrG 2017-01-24 23:55:26
it's entirely irrelevant what status code it is ...
SynrG 2017-01-24 23:55:33
the relevant point is that it's *fsck* doing something
SynrG 2017-01-24 23:55:43
i.e. it's there. your /dev/sda6 is not
SynrG 2017-01-24 23:55:52
learn to read error messages :)
SynrG 2017-01-24 23:56:26
the thing before the colon is the thing doing the error reporting. the thing after the colon is the thing it's complaining about
TvL2386 2017-01-24 23:56:31
<< hates UUID, likes LABEL :)
Digital 2017-01-24 23:56:38
yeah, sorry
Digital 2017-01-24 23:57:17
sda6 is there, its my root partition. fstab shows the correct uuid
TvL2386 2017-01-24 23:57:23
no worries Digital
SynrG 2017-01-24 23:57:28
Digital: sda6 is apparently not there during early boot
SynrG 2017-01-24 23:57:36
Digital: i.e. read the UUID factoid above
SynrG 2017-01-24 23:57:45
names of things can change ...
TvL2386 2017-01-24 23:58:08
yeah but he says fstab shows the correct UUID
TvL2386 2017-01-24 23:58:13
so he's using UUIDs?
TvL2386 2017-01-24 23:58:20
and not sda6
SynrG 2017-01-24 23:58:28
beats me. let's see the /etc/fstab then
SynrG 2017-01-24 23:58:37
and the output of 'blkid'
Rephlexie 2017-01-24 23:58:43
paste fstab
Digital 2017-01-24 23:59:40
https://paste.debian.net/hidden/55a32576/
SynrG 2017-01-24 23:59:56
um, hmm ...
SynrG 2017-01-24 23:59:58
aptitude search '~nearth !~sastronomy !~sscience'
SynrG 2017-01-25 00:00:04
oops, wrong paste buffer :)
Digital 2017-01-25 00:00:16
uh, i forgot blkid
SynrG 2017-01-25 00:00:18
http://forums.debian.net/viewtopic.php?f=17&t=127039
SynrG 2017-01-25 00:00:33
^^ this user had the same issue, and updated the initramfs and then everything worked
SynrG 2017-01-25 00:00:48
their fstab and blkid looked fine, too
TvL2386 2017-01-25 00:01:11
haha SynrG just wanted to paste that too
SynrG 2017-01-25 00:01:21
so back to my original assertion that the initrd was built incorrectly :)
TvL2386 2017-01-25 00:01:23
update-initramfs -u has fixed it for the dude
Digital 2017-01-25 00:01:34
do you still need blkid?
SynrG 2017-01-25 00:01:52
welcome to twenty minutes ago ;)
Digital 2017-01-25 00:02:01
so, what's caused initrd to be build incorrectly?
Digital 2017-01-25 00:02:11
huh?
TvL2386 2017-01-25 00:02:25
<< dunno
SynrG 2017-01-25 00:02:30
today i'm blaming squirrels.
TvL2386 2017-01-25 00:02:38
anyway: got to get my son from school... BBL!
TvL2386 2017-01-25 00:02:50
good lcuk
Digital 2017-01-25 00:02:51
uhh, I always blame microsoft :P
Digital 2017-01-25 00:02:59
seeya
SynrG 2017-01-25 00:03:59
Digital: it's harmless to try rebuilding the initramfs and rebooting ...
SynrG 2017-01-25 00:04:16
as for it not building, could be due to a failed apt upgrade?
SynrG 2017-01-25 00:04:38
if you abort an upgrade partway through, then reboot, you're asking for trouble. the triggers that rebuild your initrd run at the end.
Digital 2017-01-25 00:05:02
i deleted my kernel by switching ubuntu and debian repositories... then i formated the partition and installed debian lol
SynrG 2017-01-25 00:05:24
wtf ... "deleted my kernel by ..." ...
Digital 2017-01-25 00:05:44
yeah, i was shocked too
SynrG 2017-01-25 00:05:56
anyway, if it's a fresh install of Debian, no worries :)
SynrG 2017-01-25 00:06:04
as for how you hosed your initrd
SynrG 2017-01-25 00:06:40
i gotta work, folks. good luck, Digital
Digital 2017-01-25 00:06:54
the update gave some errors about missing firmware
Digital 2017-01-25 00:07:00
thanks synrg
Digital 2017-01-25 00:13:11
SynrG, petn-randall it works now
petn-randall 2017-01-25 00:15:26
Digital: Sweet! Glad it worked out.
TvL2386 2017-01-25 00:38:59
back!