Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Virtual-DSM startet nicht, oder nur mit vielen Fehlermeldungen

phillip.de
in Deutsch

Featured Replies

Guten Morgen zusammen,

ich versuche momentan meine Synology auf eine virtuelle DSM umzustellen. Daher habe ich einen Container mit dem virtual dsm Image erstellt. Leider bekommt die Maschine beim booten ganz viele Fehlermeldungen:

  

text  error  warn  system  array  login  


❯ -----------------------------------------------------------
❯  You can now login to DSM at http://192.168.10.9:5000
❯ -----------------------------------------------------------

[   49.972838] iSCSI:target_core_ep.c:802:ep_attach_hba ODX Token Manager is enabled.
[   50.576436] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   50.578153] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   50.579203] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   50.580351] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 02 00
[   50.582003] blk_update_request: critical target error, dev synoboot, sector in range 28672 + 0-2(12)
[   50.583549] buffer_io_error: 2 callbacks suppressed
[   50.584397] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost sync page write
[   51.224167] EXT2-fs (synoboot2): previous I/O error to superblock detected
[   51.224167] 
[   51.228903] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.233295] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   51.235898] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   51.238713] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 02 00
[   51.242697] blk_update_request: critical target error, dev synoboot, sector 32132
[   51.246433] Buffer I/O error on dev synoboot2, logical block 1, lost async page write
[   51.250755] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.255080] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   51.258213] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   51.261012] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 02 00
[   51.264992] blk_update_request: critical target error, dev synoboot, sector 32132
[   51.268601] Buffer I/O error on dev synoboot2, logical block 1, lost sync page write
[   51.272349] EXT2-fs (synoboot2): previous I/O error to superblock detected
[   51.272349] 
[   51.276912] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.281493] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   51.284608] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   51.287405] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 02 00
[   51.291388] blk_update_request: critical target error, dev synoboot, sector 32132
[   51.295154] Buffer I/O error on dev synoboot2, logical block 1, lost sync page write
[   51.299628] VFS: Dirty inode writeback failed for block device synoboot2 (err=-5).
[   51.309364] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.311759] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   51.313565] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   51.315844] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 02 00
[   51.319468] blk_update_request: critical target error, dev synoboot, sector 32132
[   51.321491] Buffer I/O error on dev synoboot2, logical block 1, lost sync page write
[   51.327136] sd 6:0:0:0: [synoboot] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.329514] sd 6:0:0:0: [synoboot] tag#1 Sense Key : 0x5 [current] 
[   51.331457] sd 6:0:0:0: [synoboot] tag#1 ASC=0x24 ASCQ=0x0 
[   51.332712] sd 6:0:0:0: [synoboot] tag#1 CDB: opcode=0x2a 2a 00 00 00 9d 84 00 00 02 00
[   51.334748] blk_update_request: critical target error, dev synoboot, sector in range 36864 + 0-2(12)
[   51.337209] EXT2-fs (synoboot2): previous I/O error to superblock detected
[   51.337209] 
[   51.340271] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.342315] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   51.343814] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   51.345149] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 02 00
[   51.347034] blk_update_request: critical target error, dev synoboot, sector in range 28672 + 0-2(12)
[   51.349052] Buffer I/O error on dev synoboot2, logical block 1, lost sync page write
[   51.351159] EXT2-fs (synoboot2): error: ext2_fsync: detected IO error when writing metadata buffers
[   51.360152] EXT2-fs (synoboot2): previous I/O error to superblock detected
[   51.360152] 
[   51.362593] sd 6:0:0:0: [synoboot] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.362595] sd 6:0:0:0: [synoboot] tag#1 Sense Key : 0x5 [current] 
[   51.362596] sd 6:0:0:0: [synoboot] tag#1 ASC=0x24 ASCQ=0x0 
[   51.362598] sd 6:0:0:0: [synoboot] tag#1 CDB: opcode=0x2a 2a 00 00 00 81 84 00 00 02 00
[   51.362600] blk_update_request: critical target error, dev synoboot, sector in range 32768 + 0-2(12)
[   51.371632] sd 6:0:0:0: [synoboot] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.373249] sd 6:0:0:0: [synoboot] tag#0 Sense Key : 0x5 [current] 
[   51.374362] sd 6:0:0:0: [synoboot] tag#0 ASC=0x24 ASCQ=0x0 
[   51.375338] sd 6:0:0:0: [synoboot] tag#0 CDB: opcode=0x2a 2a 00 00 00 7d 84 00 00 04 00
[   51.376688] blk_update_request: critical target error, dev synoboot, sector in range 28672 + 0-2(12)
[   51.378110] Buffer I/O error on dev synoboot2, logical block 1, lost async page write
[   51.379333] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost async page write
[   51.380701] sd 6:0:0:0: [synoboot] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   51.381927] sd 6:0:0:0: [synoboot] tag#1 Sense Key : 0x5 [current] 
[   51.382764] sd 6:0:0:0: [synoboot] tag#1 ASC=0x24 ASCQ=0x0 
[   51.383505] sd 6:0:0:0: [synoboot] tag#1 CDB: opcode=0x2a 2a 00 00 00 7f 88 00 00 06 00
[   51.384551] blk_update_request: critical target error, dev synoboot, sector in range 28672 + 0-2(12)
[   51.385744] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost async page write
[   51.386990] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost async page write
[   51.388245] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost async page write
[   51.389495] blk_update_request: critical target error, dev synoboot, sector in range 28672 + 0-2(12)
[   51.390685] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost async page write
[   51.392089] blk_update_request: critical target error, dev synoboot, sector in range 28672 + 0-2(12)
[   51.393291] Buffer I/O error on dev synoboot2, logical block in range 0 + 0-2(12) , lost sync page write
[   51.394718] EXT2-fs (synoboot2): previous I/O error to superblock detected
[   51.394718] 
[   51.396359] blk_update_request: critical target error, dev synoboot, sector 32132
[   51.397393] Buffer I/O error on dev synoboot2, logical block 1, lost sync page write
[   51.398549] VFS: Dirty inode writeback failed for block device synoboot2 (err=-5).
[   51.502632] workqueue: max_active 1024 requested for vhost_scsi is out of range, clamping between 1 and 512
[   54.614354] findhostd uses obsolete (PF_INET,SOCK_PACKET)
[   58.408993] fuse init (API version 7.23)

 

Die Paritätsplatte (Temporär) meines Arrays gibt derzeit auch Smart-Errors aus, aber ich warte hier noch bis ich die Daten übertragen habe damit ich die Platten aus dem Synology einbauen kann. Kann der Fehler mit dem Smart-Error zusammenhängen? Ich habe mal ein Screenshot der Smart-Werte der betroffenen Platte anhängt...

 

Ein Bild der Containerkonfiguration habe ich auch angehängt.

 

Nebeninformationen:

Ich habe für die Daten der DSM einen eigenen Share angelegt (Public / No Export) wo die Daten der DSM direkt auf dem Array liegen sollen. Ich brauche hier ja keine Performance, nur Speicher. Die Partition qcow2 habe ich genutzt, da ich hier die Platte beizeiten gerne vergrößern würde.

 

Danke!

 

 

 

 

 

Screenshot 2024-09-01 093406.png

Screenshot 2024-09-01 093504.png

  • Quote
    9 hours ago, phillip.de said:

    Leider bekommt die Maschine beim booten ganz viele Fehlermeldungen:

    dazu würde ich eher mal im github dieses Dockers anfragen / issue aufmachen / ...

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.