Garage : install fail: kernel: EXT4-fs (nbd0): unable to read superblock

My YunoHost server

Hardware: VM on proxmox
YunoHost version:
yunohost:
repo: stable
version: 11.2.10.3
yunohost-admin:
repo: stable
version: 11.2.4.1
moulinette:
repo: stable
version: 11.2
ssowat:
repo: stable
version: 11.2
I have access to my server : SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
YNH_APP_INSTANCE_NAME: garage
YNH_APP_INSTANCE_NUMBER: ‘1’
YNH_APP_MANIFEST_VERSION: 0.9.1~ynh2
YNH_APP_PACKAGING_FORMAT: ‘2.0’

Description of my issue

I would like to test garage but I have some problems during installation …

https://paste.yunohost.org/raw/malodedopo

I don’t find much interesting in the log books, but that :

Mar 01 18:42:56 charbowicz.fr kernel: block nbd0: Attempted send on invalid socketMar 01 18:42:56 charbowicz.fr kernel: blk_update_request: I/O error, dev nbd0, sector 2 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
Mar 01 18:42:56 charbowicz.fr kernel: EXT4-fs (nbd0): unable to read superblock
Mar 01 18:42:56 charbowicz.fr systemd[1]: garage.service: Control process exited, code=exited, status=32/n/a

I don’t like !

Wouldn’t that be a problem with my VM’s system disk ?

Francais ou English peut importe :slight_smile:

PS: at the boot; I have:

kernel: x86/PAT: IPMI[sensors]:1866 map pfn expected mapping type uncached-minus for [mem 0xbffe2000-0xbffe2fff], got write-back  
kernel: x86/PAT: IPMI[sel]:1867 map pfn expected mapping type uncached-minus for [mem 0xbffe2000-0xbffe2fff], got write-back
kernel: x86/PAT: IPMI[sensors]:1866 map pfn expected mapping type uncached-minus for [mem 0xbffe2000-0xbffe2fff], got write-back
kernel: x86/PAT: IPMI[sel]:1867 map pfn expected mapping type uncached-minus for [mem 0xbffe2000-0xbffe2fff], got write-back

I know I have IPMI on my server, but I don’t understand why the kernel isn’t happy

It sounds like it, but I can’t really diagnose that one, sorry.

Wath is the best way ? Or the “the least worst solution” ?

  • backup yunohost and restor on new VM (fresh install)
  • copy disk whti proxmox
  • clone VM (for me no)

It’s just difficult to say because I/O error and unable to read superblock usually point towards physical issues, or at least partioning / filesystem issues, and YunoHost doesn’t deal with any of this x_x. I doubt backup/restore will magically fix the issue.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.