problem in porteus 3.2.2

[barquerito]

Hello,

I recently used porteus, although I use linux and years slackware

Sometimes the basic system commands fail

Dmesg throw this:
...
REISERFS warning (device loop7): sh-2006 read_super_block: bread failed (dev loop7, block 16, size 4096)
Random: crng init done
REISERFS warning (device loop9): sh-2006 read_super_block: bread failed (dev loop9, block 16, size 4096)
REISERFS warning (device loop11): sh-2006 read_super_block: bread failed (dev loop11, block 16, size 4096)
REISERFS warning (device loop12): sh-2006 read_super_block: bread failed (dev loop12, block 16, size 4096)
REISERFS warning (device loop16): sh-2006 read_super_block: bread failed (dev loop16, block 16, size 4096)
REISERFS warning (device loop19): sh-2006 read_super_block: bread failed (dev loop19, block 2, size 4096)
...

- the xzm modules I think are fine (think)

help.

[Bogomips]

Welcome to Porteus. Can you please provide more details, like at what stage this happens, and what you were tring to do at the time. Also, in which DE?

[barquerito]

Hello,
I have an old laptop, which handles other linux without problems.

Now I want to use Porteus-XFCE-v3.2.2-i586.iso, I made 2 new and different usb installations, and when I add a module to the modules folder, in dmesg, for each module the following message appears:
REISERFS warning (device loopX): sh-2006 read_super_block: bread failed (dev loopX, block XX, size 4096)

QUESTION: IS THIS ERROR SERIOUS? Can you check it?

(Shortly after using it starts to give me linux errors, and I do not know if it is due to the previous error)

thx

[Blaze]

Can you show log of these commands?

Code: Select all

cat /proc/cmdline
dmesg | grep -i "warning\|error\|failed"
ls -l /sys/block

BTW, I have the same warnings:

Code: Select all

guest@porteus:~$ dmesg | grep -i "warning\|error\|failed"
[    1.926808] REISERFS warning (device loop5): sh-2006 read_super_block: bread failed (dev loop5, block 16, size 4096)
[    2.304433] REISERFS warning (device loop13): sh-2006 read_super_block: bread failed (dev loop13, block 2, size 4096)
[    2.304441] REISERFS warning (device loop13): sh-2006 read_super_block: bread failed (dev loop13, block 16, size 4096)
[    2.355436] REISERFS warning (device loop14): sh-2006 read_super_block: bread failed (dev loop14, block 2, size 4096)
[    2.355443] REISERFS warning (device loop14): sh-2006 read_super_block: bread failed (dev loop14, block 16, size 4096)
guest@porteus:~$

Cheers

[Ed_P]

I don't have those errors.

I do have other errors though.

Code: Select all

guest@porteus:~$ dmesg | grep -i "warning\|error\|failed"
[    0.949067] i8042: Warning: Keylock active
[   13.298902] ACPI Warning: \_SB.IETM._ART: Return Package type mismatch at index 0 - found Integer, expected Reference (20160831/nspredef-297)
[   13.852982] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[   14.675999] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[   14.676119] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[   14.676228] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
guest@porteus:~$ 

But I'm using a different DE and arch.

What kernel are you using?

Code: Select all

guest@porteus:~$ uname -r
4.9.12-porteus
guest@porteus:~$

[barquerito]

log:

Code: Select all

uname -r :

  4.9.0-porteus

Code: Select all

cat /proc/cmdline :

  quiet initrd=initrd.xz nomagic norootcopy zram=33% BOOT_IMAGE=vmlinuz 

Code: Select all

ls -l /sys/block :

  total 0
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop0 -> ../devices/virtual/block/loop0/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop1 -> ../devices/virtual/block/loop1/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop10 -> ../devices/virtual/block/loop10/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop11 -> ../devices/virtual/block/loop11/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop12 -> ../devices/virtual/block/loop12/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop13 -> ../devices/virtual/block/loop13/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop14 -> ../devices/virtual/block/loop14/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop15 -> ../devices/virtual/block/loop15/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop16 -> ../devices/virtual/block/loop16/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop17 -> ../devices/virtual/block/loop17/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop18 -> ../devices/virtual/block/loop18/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop2 -> ../devices/virtual/block/loop2/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop3 -> ../devices/virtual/block/loop3/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop4 -> ../devices/virtual/block/loop4/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop5 -> ../devices/virtual/block/loop5/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop6 -> ../devices/virtual/block/loop6/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop7 -> ../devices/virtual/block/loop7/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop8 -> ../devices/virtual/block/loop8/
  lrwxrwxrwx 1 root root 0 ago 14 22:45 loop9 -> ../devices/virtual/block/loop9/
  lrwxrwxrwx 1 root root 0 ago 14 22:43 mmcblk0 -> ../devices/pci0000:00/0000:00:1c.0/0000:02:00.0/mmc_host/mmc0/mmc0:e624/block/mmcblk0/
  lrwxrwxrwx 1 root root 0 ago 14 22:43 sda -> ../devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/host2/target2:0:0/2:0:0:0/block/sda/
  lrwxrwxrwx 1 root root 0 ago 14 22:43 sdb -> ../devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sdb/
  lrwxrwxrwx 1 root root 0 ago 14 22:43 zram0 -> ../devices/virtual/block/zram0/

Code: Select all

dmesg | grep -i "warning\|error\|failed" :

  [    0.000000] tsc: Fast TSC calibration failed
  [    0.249885] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
  [    4.062536] REISERFS warning (device loop9): sh-2006 read_super_block: bread failed (dev loop9, block 2, size 4096)
  [    4.062548] REISERFS warning (device loop9): sh-2006 read_super_block: bread failed (dev loop9, block 16, size 4096)
  [    4.296538] REISERFS warning (device loop17): sh-2006 read_super_block: bread failed (dev loop17, block 2, size 4096)
  [    4.296551] REISERFS warning (device loop17): sh-2006 read_super_block: bread failed (dev loop17, block 16, size 4096)
  [    4.322541] REISERFS warning (device loop18): sh-2006 read_super_block: bread failed (dev loop18, block 2, size 4096)
  [    4.322554] REISERFS warning (device loop18): sh-2006 read_super_block: bread failed (dev loop18, block 16, size 4096)
  [   19.747801] [drm:0xf931012f] *ERROR* CPU pipe A FIFO underrun
  [   19.747809] [drm:0xf931012f] *ERROR* CPU pipe B FIFO underrun

[donald]

Hello barquerito

These messages are not normal in XFCE-32 Bit - as you can see here:

• guest@porteus:~$ uname -rm
  4.9.0-porteus i686
  guest@porteus:~$ cat /proc/cmdline
  quiet initrd=initrd.xz changes=/porteus ipv6.disable=1 BOOT_IMAGE=vmlinuz
  guest@porteus:~$ ls $PORTDIR/modules
  nvidia-304.134-k4.9.xzm palemoon-26.5.0-i686-1.xzm
  guest@porteus:~$ dmesg | grep -i "warning\|error\|failed"
  [ 0.000000] ACPI BIOS Warning (bug): Optional FADT field .....
  [ 1.285314] EXT4-fs (sda2): warning: mounting unchecked fs, running e2fsck is recommended
  [ 1.308093] EXT4-fs (sda3): warning: mounting unchecked fs, running e2fsck is recommended
  [ 1.338656] EXT4-fs (sda4): warning: mounting unchecked fs, running e2fsck is recommended
  [ 17.547252] blk_update_request: I/O error, dev fd0, sector 0
  [ 17.547255] floppy: error -5 while reading block 0
  guest@porteus:~$

I suspect there is something wrong with your additional modules.
Boot porteus without them - move them into the optional folder
and check if you get the same errors.
If not, try your additional modules one by one to identify the ones who give the errors,

[barquerito]

boot whitout modules:
=====================

uname -r =
4.9.0-porteus

cat /proc/cmdline =
quiet initrd=initrd.xz nomagic norootcopy BOOT_IMAGE=vmlinuz

ls -l /sys/block =
total 0
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop0 -> ../devices/virtual/block/loop0/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop1 -> ../devices/virtual/block/loop1/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop2 -> ../devices/virtual/block/loop2/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop3 -> ../devices/virtual/block/loop3/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop4 -> ../devices/virtual/block/loop4/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop5 -> ../devices/virtual/block/loop5/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop6 -> ../devices/virtual/block/loop6/
lrwxrwxrwx 1 root root 0 Aug 18 00:03 loop7 -> ../devices/virtual/block/loop7/
lrwxrwxrwx 1 root root 0 Aug 18 00:01 mmcblk0 -> ../devices/pci0000:00/0000:00:1c.0/0000:02:00.0/mmc_host/mmc0/mmc0:e624/block/mmcblk0/
lrwxrwxrwx 1 root root 0 Aug 18 00:01 sda -> ../devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/host2/target2:0:0/2:0:0:0/block/sda/
lrwxrwxrwx 1 root root 0 Aug 18 00:02 sdb -> ../devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0/block/sdb/

dmesg | grep -i 'warning\|error\|failed' =
[ 0.249885] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 17.945787] [drm:0xf8bf812f] *ERROR* CPU pipe A FIFO underrun
[ 17.945796] [drm:0xf8bf812f] *ERROR* CPU pipe B FIFO underrun

[donald]

As one can see, no "REISERFS warning.." anymore.
now step 2:
Put back additional modules one by one to find the ones who give the errors.

[barquerito]

Hello,

I currently have 27 modules in the modules folder, and there is no error in dmesg.
But I have detected some module that does give error in dmesg ("REISERFS warning.."), if it is loaded at startup:

Example: enchant-1.6.0-i486-1.txz __md5: d8a7cad772cd312935ff451676e30a5a
( https://mirrors.slackware.com/slackware ... i486-1.txz )

(Question 1):
Can you check it by putting the xzm in modules?

If I download txz and I generate a xzm, which I put in /porteus/modules,
In dmesg I get an error message when I boot.

Incision: it happens that if I run several times txz2xzm enchant-1.6.0-i486-1.txz
The md5 of the xzm is different can you verify it? (Question 2)


I use this script:

Code: Select all

#!/bin/bash 
# TXZ2XZM DOES NOT GENERATE THE SAME FILE
# example: https://mirrors.slackware.com/slackware/slackware-14.2/slackware/l/enchant-1.6.0-i486-1.txz
wwwpath=https://mirrors.slackware.com/slackware/slackware-14.2/slackware/l/
file=enchant-1.6.0-i486-1
txz=$file.txz
xzm=$file.xzm

clear
rm $file*	# clean files
wget -nv $wwwpath$txz	# -nv = no verbose

for i in {1..3}; do
   rm $xzm* 2>/dev/null
   txz2xzm $txz >/dev/null
   echo -e "\n__ Round $i __======== MD5 FILES TXZ AND XZM ==================="
   md5sum $file*
   echo "---------------------------------------------------------------"
done

thx

[donald]

Hello barquerito

some observations:
If i convert only the enchant-1.6.0-i486-1.txz package,i get the REISERFS error.
(put into modules / reboot)

If i download enchant via USM, (it has the same md5sum), it shows missing dependencies and pull in
aspell-0.60.6.1-i586-1.txz and hunspell-1.3.3-i486-1.txz.
Using this bundle doesn't produce the errors.

[wread]

@barquerito
Are you using a reiserfs in your system? (I guess you are not, therefore the warning!)