Beiträge von Chino2

Chino2 · 30. Januar 2020

I reinstalled by omv and remake the partition.

Code

Jan 30 07:45:31 hikari9 kernel: [41777.900602] xhci_hcd 0000:01:00.0: xHCI host not responding to stop endpoint command.
Jan 30 07:45:31 hikari9 kernel: [41777.916622] xhci_hcd 0000:01:00.0: Host halt failed, -110
Jan 30 07:45:31 hikari9 kernel: [41777.916633] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
Jan 30 07:45:31 hikari9 kernel: [41777.916666] xhci_hcd 0000:01:00.0: HC died; cleaning up
Jan 30 07:45:31 hikari9 kernel: [41777.917049] usb 1-1: USB disconnect, device number 2
Jan 30 07:45:31 hikari9 kernel: [41777.918679] usb 2-2: USB disconnect, device number 2


Jan 30 10:05:29 hikari9 kernel: [50176.469501] EXT4-fs warning (device dm-2): htree_dirblock_to_tree:995: inode #11272193: lblock 0: comm smbd: error -5 reading directory block
Jan 30 10:05:29 hikari9 kernel: [50176.469721] EXT4-fs warning (device dm-2): htree_dirblock_to_tree:995: inode #11272193: lblock 0: comm smbd: error -5 reading directory block


Jan 30 10:45:13 hikari9 kernel: [52560.423277] EXT4-fs warning (device dm-2): htree_dirblock_to_tree:995: inode #11272193: lblock 0: comm sshd: error -5 reading directory block


Jan 30 11:00:51 hikari9 kernel: [53498.123555] Buffer I/O error on dev dm-1, logical block 137364464, async page read
Jan 30 11:00:51 hikari9 kernel: [53498.126049] Buffer I/O error on dev dm-2, logical block 267180016, async page read
Jan 30 11:00:51 hikari9 kernel: [53498.130815] Buffer I/O error on dev dm-0, logical block 83825648, async page read




Jan 30 11:00:52 hikari9 kernel: [53499.761185] Buffer I/O error on dev dm-1, logical block 68714496, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.761195] JBD2: Error -5 detected when updating journal superblock for dm-1-8.
Jan 30 11:00:52 hikari9 kernel: [53499.761199] Aborting journal on device dm-1-8.
Jan 30 11:00:52 hikari9 kernel: [53499.761212] Buffer I/O error on dev dm-1, logical block 68714496, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.761217] JBD2: Error -5 detected when updating journal superblock for dm-1-8.
Jan 30 11:00:52 hikari9 kernel: [53499.764305] Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.764314] EXT4-fs (dm-1): I/O error while writing superblock




Jan 30 11:00:52 hikari9 kernel: [53499.789912] Buffer I/O error on dev dm-0, logical block 41451520, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.789926] JBD2: Error -5 detected when updating journal superblock for dm-0-8.
Jan 30 11:00:52 hikari9 kernel: [53499.789931] Aborting journal on device dm-0-8.
Jan 30 11:00:52 hikari9 kernel: [53499.789946] Buffer I/O error on dev dm-0, logical block 41451520, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.789951] JBD2: Error -5 detected when updating journal superblock for dm-0-8.
Jan 30 11:00:52 hikari9 kernel: [53499.790034] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.790041] EXT4-fs (dm-0): I/O error while writing superblock
Jan 30 11:00:52 hikari9 kernel: [53499.790047] EXT4-fs error (device dm-0): ext4_put_super:985: Couldn't clean up the journal
Jan 30 11:00:52 hikari9 kernel: [53499.790070] EXT4-fs (dm-0): Remounting filesystem read-only
Jan 30 11:00:52 hikari9 kernel: [53499.790090] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
Jan 30 11:00:52 hikari9 kernel: [53499.790095] EXT4-fs (dm-0): I/O error while writing superblock


Jan 30 11:02:15 hikari9 kernel: [53581.954378] Buffer I/O error on dev dm-0, logical block 83825648, async page read
Jan 30 11:02:15 hikari9 kernel: [53581.954651] Buffer I/O error on dev dm-0, logical block 83825648, async page read
Jan 30 11:02:15 hikari9 kernel: [53581.954812] Buffer I/O error on dev dm-1, logical block 137364464, async page read
Jan 30 11:02:15 hikari9 kernel: [53581.955059] Buffer I/O error on dev dm-1, logical block 137364464, async page read
Jan 30 11:02:15 hikari9 kernel: [53581.955204] Buffer I/O error on dev dm-2, logical block 267180016, async page read
Jan 30 11:02:15 hikari9 kernel: [53581.955417] Buffer I/O error on dev dm-2, logical block 267180016, async page read
Jan 30 11:02:15 hikari9 kernel: [53582.032142] Buffer I/O error on dev dm-2, logical block 267180016, async page read
Jan 30 11:02:15 hikari9 kernel: [53582.035204] Buffer I/O error on dev dm-2, logical block 267180016, async page read
Jan 30 11:02:15 hikari9 kernel: [53582.058296] Buffer I/O error on dev dm-2, logical block 267180016, async page read
Jan 30 11:02:15 hikari9 kernel: [53582.064510] Buffer I/O error on dev dm-2, logical block 267180016, async page read

Alles anzeigen

Still get almost same error. What should I do?

Chino2 · 29. Januar 2020

Code

Jan 29 05:56:27 hikari9 kernel: [39634.581972] EXT4-fs error (device sda3): __ext4_get_inode_loc:4708: inode #12: block 1057: comm umount: unable to read itable block
Jan 29 05:56:27 hikari9 kernel: [39634.582018] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582025] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582034] EXT4-fs error (device sda3) in ext4_reserve_inode_write:5921: IO failure
Jan 29 05:56:27 hikari9 kernel: [39634.582052] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582058] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582204] EXT4-fs error (device sda3): __ext4_get_inode_loc:4708: inode #12: block 1057: comm umount: unable to read itable block
Jan 29 05:56:27 hikari9 kernel: [39634.582229] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582235] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582240] EXT4-fs error (device sda3) in ext4_reserve_inode_write:5921: IO failure
Jan 29 05:56:27 hikari9 kernel: [39634.582255] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582260] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582471] Aborting journal on device sda3-8.
Jan 29 05:56:27 hikari9 kernel: [39634.582482] Buffer I/O error on dev sda3, logical block 68165664, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582488] JBD2: Error -5 detected when updating journal superblock for sda3-8.
Jan 29 05:56:27 hikari9 kernel: [39634.582595] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582602] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582608] EXT4-fs error (device sda3): ext4_journal_check_start:61: Detected aborted journal
Jan 29 05:56:27 hikari9 kernel: [39634.582630] EXT4-fs (sda3): Remounting filesystem read-only
Jan 29 05:56:27 hikari9 kernel: [39634.582645] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582650] EXT4-fs (sda3): I/O error while writing superblock

Alles anzeigen

Maybe this is error?

Chino2 · 29. Januar 2020

My drive is unmounting randomly.
I found this in syslog.

Code

Jan 29 05:56:26 hikari9 kernel: [39634.031678] xhci_hcd 0000:01:00.0: Abort failed to stop command ring: -110
Jan 29 05:56:26 hikari9 kernel: [39634.047692] xhci_hcd 0000:01:00.0: Host halt failed, -110
Jan 29 05:56:26 hikari9 kernel: [39634.047698] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
Jan 29 05:56:26 hikari9 kernel: [39634.047724] xhci_hcd 0000:01:00.0: HC died; cleaning up
Jan 29 05:56:26 hikari9 kernel: [39634.047840] xhci_hcd 0000:01:00.0: xHCI host not responding to stop endpoint command.
Jan 29 05:56:26 hikari9 kernel: [39634.063855] xhci_hcd 0000:01:00.0: Host halt failed, -110
Jan 29 05:56:26 hikari9 kernel: [39634.064646] usb 1-1: USB disconnect, device number 2
Jan 29 05:56:26 hikari9 kernel: [39634.068013] usb 2-2: USB disconnect, device number 2

And this

Code

Jan 29 05:56:27 hikari9 kernel: [39634.581972] EXT4-fs error (device sda3): __ext4_get_inode_loc:4708: inode #12: block 1057: comm umount: unable to read itable block
Jan 29 05:56:27 hikari9 kernel: [39634.582018] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582025] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582034] EXT4-fs error (device sda3) in ext4_reserve_inode_write:5921: IO failure
Jan 29 05:56:27 hikari9 kernel: [39634.582052] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582058] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582204] EXT4-fs error (device sda3): __ext4_get_inode_loc:4708: inode #12: block 1057: comm umount: unable to read itable block
Jan 29 05:56:27 hikari9 kernel: [39634.582229] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582235] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582240] EXT4-fs error (device sda3) in ext4_reserve_inode_write:5921: IO failure
Jan 29 05:56:27 hikari9 kernel: [39634.582255] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582260] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582471] Aborting journal on device sda3-8.
Jan 29 05:56:27 hikari9 kernel: [39634.582482] Buffer I/O error on dev sda3, logical block 68165664, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582488] JBD2: Error -5 detected when updating journal superblock for sda3-8.
Jan 29 05:56:27 hikari9 kernel: [39634.582595] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582602] EXT4-fs (sda3): I/O error while writing superblock
Jan 29 05:56:27 hikari9 kernel: [39634.582608] EXT4-fs error (device sda3): ext4_journal_check_start:61: Detected aborted journal
Jan 29 05:56:27 hikari9 kernel: [39634.582630] EXT4-fs (sda3): Remounting filesystem read-only
Jan 29 05:56:27 hikari9 kernel: [39634.582645] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Jan 29 05:56:27 hikari9 kernel: [39634.582650] EXT4-fs (sda3): I/O error while writing superblock

Alles anzeigen

Code

Jan 29 05:56:27 hikari9 umount[7281]: umount: /srv/dev-disk-by-label-Time1: target is busy.
Jan 29 05:56:27 hikari9 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dTime1.mount: Mount process exited, code=exited, status=32/n/a
Jan 29 05:56:27 hikari9 systemd[1]: Failed unmounting /srv/dev-disk-by-label-Time1.
Jan 29 05:56:27 hikari9 umount[7282]: umount: /srv/dev-disk-by-label-Time1: target is busy.
Jan 29 05:56:27 hikari9 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dTime1.mount: Unit is bound to inactive unit dev-disk-by\x2dlabel-Time1.device. Stopping, too.
Jan 29 05:56:27 hikari9 systemd[1]: Unmounting /srv/dev-disk-by-label-Time1...
Jan 29 05:56:27 hikari9 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dTime2.mount: Succeeded.
Jan 29 05:56:27 hikari9 systemd[1]: Unmounted /srv/dev-disk-by-label-Time2.
Jan 29 05:56:27 hikari9 umount[7283]: umount: /srv/dev-disk-by-label-Time1: target is busy.
Jan 29 05:56:27 hikari9 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dTime1.mount: Mount process exited, code=exited, status=32/n/a

I tested another drive, it still unmount randomly.

Chino2 · 12. Januar 2020

After 'chmod 755 /sftp' it works. thanks.

Chino2 · 12. Januar 2020

After add user to the group, I can't access to the SFTP

Chino2 · 12. Januar 2020

Hello, I'm using OMV5 on my Raspberry pi 4.

When I login to SFTP server, it shows root directory.
My account is in "users" group.

Beiträge von Chino2

My drive unmount randomly.

My drive unmount randomly.

My drive unmount randomly.

Sftp plugins shows root directory

Sftp plugins shows root directory

Sftp plugins shows root directory