KYTECHNGAMING Posted September 7, 2021 Share Posted September 7, 2021 Ext3 disks are not recognized. It happened in Hero DSL with 3.7.2 Beta and earlier software as well. Look Media4 👇 Spoiler { "media": { "Media1": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "Kingston", "product": "DataTraveler 2.0", "serial": "5B651E00029F", "size": "1031798784", "partition": [ { "uuid": "9e1f4c42-b45a-d701-9003-4c42b45ad701", "label": "Keenetic_OPKG", "fstype": "ext4", "state": "MOUNTED", "total": "961764352", "free": "861008896" } ] }, "Media0": { "usb": { "port": 1, "version": "3.00" }, "state": "ACTIVE", "manufacturer": "Intenso", "product": "External USB 3.0", "serial": "20201108102D9", "size": "5000981078016", "partition": [ { "uuid": "f3cff6b6-fe95-d701-0085-f6b6fe95d701", "label": "Keenetic_DATA", "fstype": "ext4", "state": "MOUNTED", "total": "4688046686208", "free": "4050643341312" } ] }, "Media3": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "TOSHIBA", "product": "TransMemory", "serial": "001CC0C60D71E810542F0368", "size": "3926949888", "partition": [ { "uuid": "6c9b90db-fea3-d701-6080-90dbfea3d701", "label": "Keenetic_TEMP", "fstype": "ext2", "state": "MOUNTED", "total": "3026038784", "free": "3026011136" }, { "uuid": "00000000-0000-0000-0000-000000000000", "label": "", "fstype": "swap", "state": "MOUNTED", "total": "801107968", "free": "801107968" } ] }, "Media4": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "TOSHIBA ", "product": "TransMemory ", "serial": "001D92AD6BE2C96093800AAA", "size": "4005527552" }, "Media5": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "TOSHIBA", "product": "TransMemory", "serial": "001CC0C440A7EBB0541E0772", "size": "3926949888", "partition": [ { "uuid": "A2E1-A5A0", "label": "NO NAME", "fstype": "vfat", "state": "MOUNTED", "total": "3913998336", "free": "3912933376" } ] }, "Media6": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "Kingston", "product": "DataTraveler G3 ", "serial": "00187D1174B1EB30700080CB", "size": "8006074368", "partition": [ { "uuid": "D498B20898B1E8DE", "label": "en-ru_WinSer2012R2x64_u", "fstype": "ntfs", "state": "MOUNTED", "total": "8005021696", "free": "2493157376" } ] } }, "prompt": "(config)" } Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 7, 2021 Author Share Posted September 7, 2021 (edited) Additional log: Spoiler Sep 7 19:06:11 10.101.0.1 kernel: usb 1-2.3: new high-speed USB device number 10 using xhci-mtk Sep 7 19:06:11 10.101.0.1 kernel: usb 1-2.3: New USB device found, idVendor=0930, idProduct=6544 Sep 7 19:06:11 10.101.0.1 kernel: usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 7 19:06:11 10.101.0.1 kernel: usb 1-2.3: Product: TransMemory Sep 7 19:06:11 10.101.0.1 kernel: usb 1-2.3: Manufacturer: TOSHIBA Sep 7 19:06:11 10.101.0.1 kernel: usb 1-2.3: SerialNumber: 001D92AD6BE2C96093800AAA Sep 7 19:06:11 Keenetic-0615 kernel: usb-storage 1-2.3:1.0: USB Mass Storage device detected Sep 7 19:06:11 Keenetic-0615 kernel: scsi host4: usb-storage 1-2.3:1.0 Sep 7 19:06:12 10.101.0.1 kernel: scsi 4:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: Attached scsi generic sg3 type 0 Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: [sde] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: [sde] Write Protect is off Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: [sde] Mode Sense: 65 44 09 30 Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: [sde] No Caching mode page found Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: [sde] Assuming drive cache: write through Sep 7 19:06:12 10.101.0.1 kernel: sde: sde1 Sep 7 19:06:12 10.101.0.1 kernel: sd 4:0:0:0: [sde] Attached SCSI removable disk Sep 7 19:06:13 10.101.0.1 ndm: Storage::Manager: "Media4": enabled a disk spin down. Sep 7 19:06:13 10.101.0.1 ndm: Storage::Manager: created "Media4", port 2. Sep 7 19:06:13 10.101.0.1 netdata[936]: DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/dev/mapper'. Sep 7 19:06:13 10.101.0.1 netdata[936]: DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/dev/disk/by-label'. Sep 7 19:06:13 10.101.0.1 netdata[936]: DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/dev/vx/dsk'. Sep 7 19:06:13 10.101.0.1 netdata[936]: Initializing file /opt/var/cache/netdata/disk.sde/main.db. Sep 7 19:06:13 10.101.0.1 ndm: Storage::Partition: ext3 "f79f0eda-01a4-d701-f093-0eda01a4d701:": filesystem initialized. Sep 7 19:06:13 10.101.0.1 kernel: EXT4-fs (sde1): mounting ext3 file system using the ext4 subsystem Sep 7 19:06:13 10.101.0.1 kernel: EXT4-fs error (device sde1): ext4_ext_check_inode:510: inode #8: comm ndm: pblk 0 bad header/extent: invalid magic - magic 114, entries 0, max 277(0), depth 0(0) Sep 7 19:06:13 10.101.0.1 kernel: EXT4-fs (sde1): no journal found Sep 7 19:06:13 10.101.0.1 ndm: Core::FileSystem::Native: failed to mount "/tmp/mnt/f79f0eda-01a4-d701-f093-0eda01a4d701": invalid argument. Sep 7 19:06:13 10.101.0.1 ndm: Storage::Partition: failed to mount. Sep 7 19:06:13 10.101.0.1 ndm: Storage::Partition: ext3 "f79f0eda-01a4-d701-f093-0eda01a4d701:": unable to mount. Sep 7 19:06:13 10.101.0.1 ndm: Storage::Manager: "Media4": failed to register partition "f79f0eda-01a4-d701-f093-0eda01a4d701:". Edited September 7, 2021 by yerebakan Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 8, 2021 Share Posted September 8, 2021 @yerebakan plz run fsck on this ext4 volume on PC. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 8, 2021 Author Share Posted September 8, 2021 17 minutes ago, Le ecureuil said: @yerebakan plz run fsck on this ext4 volume on PC. I will. But this usb was formatted as new ext3 with Minitool Partition Wizard. Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 8, 2021 Share Posted September 8, 2021 24 минуты назад, yerebakan сказал: I will. But this usb was formatted as new ext3 with Minitool Partition Wizard. Цитата Sep 7 19:06:13 10.101.0.1 kernel: EXT4-fs (sde1): mounting ext3 file system using the ext4 subsystemSep 7 19:06:13 10.101.0.1 kernel: EXT4-fs error (device sde1): ext4_ext_check_inode:510: inode #8: comm ndm: pblk 0 bad header/extent: invalid magic - magic 114, entries 0, max 277(0), depth 0(0)Sep 7 19:06:13 10.101.0.1 kernel: EXT4-fs (sde1): no journal found There are errors on disk, the must be fixed. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 8, 2021 Author Share Posted September 8, 2021 3 minutes ago, Le ecureuil said: There are errors on disk, the must be fixed. I am formatting ext3 again. I wanted to try ext3 because my friend who use Keenetic, he said me that "yes, ext3 was not recognized so I use ext4" Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 8, 2021 Author Share Posted September 8, 2021 Same USB Spoiler usb 1-2.1.3: new high-speed USB device number 19 using xhci-mtk Sep 8 12:14:51 kernel usb 1-2.1.3: New USB device found, idVendor=0930, idProduct=6545 Sep 8 12:14:51 kernel usb 1-2.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 8 12:14:51 kernel usb 1-2.1.3: Product: TransMemory Sep 8 12:14:51 kernel usb 1-2.1.3: Manufacturer: TOSHIBA Sep 8 12:14:51 kernel usb 1-2.1.3: SerialNumber: 001CC0C440A7EBB0541E0772 Sep 8 12:14:51 kernel usb-storage 1-2.1.3:1.0: USB Mass Storage device detected Sep 8 12:14:51 kernel scsi host5: usb-storage 1-2.1.3:1.0 Sep 8 12:14:52 kernel scsi 5:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS Sep 8 12:14:52 kernel sd 5:0:0:0: Attached scsi generic sg3 type 0 Sep 8 12:14:53 kernel sd 5:0:0:0: [sdf] 7669824 512-byte logical blocks: (3.93 GB/3.66 GiB) Sep 8 12:14:53 kernel sd 5:0:0:0: [sdf] Write Protect is off Sep 8 12:14:53 kernel sd 5:0:0:0: [sdf] Mode Sense: 23 00 00 00 Sep 8 12:14:53 kernel sd 5:0:0:0: [sdf] No Caching mode page found Sep 8 12:14:53 kernel sd 5:0:0:0: [sdf] Assuming drive cache: write through Sep 8 12:14:53 ndm Storage::Manager: "Media5": enabled a disk spin down. Sep 8 12:14:53 ndm Storage::Manager: created "Media5", port 2. Sep 8 12:14:53 ndm Storage::Partition: ext3 "e6ffaf13-90a4-d701-60e7-af1390a4d701:": filesystem initialized. Sep 8 12:14:53 kernel EXT4-fs (sdf1): mounting ext3 file system using the ext4 subsystem Sep 8 12:14:53 kernel EXT4-fs error (device sdf1): ext4_ext_check_inode:510: inode #8: comm ndm: pblk 0 bad header/extent: invalid magic - magic 114, entries 0, max 277(0), depth 0(0) Sep 8 12:14:53 kernel EXT4-fs (sdf1): no journal found Sep 8 12:14:53 ndm Core::FileSystem::Native: failed to mount "/tmp/mnt/e6ffaf13-90a4-d701-60e7-af1390a4d701": invalid argument. Sep 8 12:14:53 ndm Storage::Partition: failed to mount. Sep 8 12:14:53 ndm Storage::Partition: ext3 "e6ffaf13-90a4-d701-60e7-af1390a4d701:": unable to mount. Sep 8 12:14:53 ndm Storage::Manager: "Media5": failed to register partition "e6ffaf13-90a4-d701-60e7-af1390a4d701:". Sep 8 12:14:55 netdata[936] DEVICE-MAPPER ('sdf', 8:80): Cannot open directory '/dev/mapper'. Sep 8 12:14:55 netdata[936] DEVICE-MAPPER ('sdf', 8:80): Cannot open directory '/dev/disk/by-label'. Sep 8 12:14:55 netdata[936] DEVICE-MAPPER ('sdf', 8:80): Cannot open directory '/dev/vx/dsk'. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk.sdf/reads.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk.sdf/writes.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_ops.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_ops.sdf/reads.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_ops.sdf/writes.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_backlog.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_backlog.sdf/backlog.db. Sep 8 12:14:55 netdata[936] RRDSET: chart name 'disk_busy.sdf' on host 'Keenetic-0615' already exists. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_util.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_util.sdf/utilization.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_mops.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_mops.sdf/reads.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_mops.sdf/writes.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_iotime.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_iotime.sdf/reads.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_iotime.sdf/writes.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_await.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_await.sdf/reads.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_await.sdf/writes.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_avgsz.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_avgsz.sdf/reads.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_avgsz.sdf/writes.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_svctm.sdf/main.db. Sep 8 12:14:55 netdata[936] Initializing file /opt/var/cache/netdata/disk_svctm.sdf/svctm.db. Sep 8 12:14:55 netdata[936] DEVICE-MAPPER ('sdf1', 8:81): Cannot open directory '/dev/mapper'. Sep 8 12:14:55 netdata[936] DEVICE-MAPPER ('sdf1', 8:81): Cannot open directory '/dev/disk/by-label'. Sep 8 12:14:55 netdata[936] DEVICE-MAPPER ('sdf1', 8:81): Cannot open directory '/dev/vx/dsk'. Sep 8 12:14:57 netdata[936] host 'Keenetic-0615', chart disk_busy.sdf: took too long to be updated (counter #578, update #579, 60550.008 secs). Resetting it. Different USB Spoiler Sep 8 12:30:46 kernel usb 1-2.1.4: new high-speed USB device number 20 using xhci-mtk Sep 8 12:30:47 kernel usb 1-2.1.4: New USB device found, idVendor=0930, idProduct=6544 Sep 8 12:30:47 kernel usb 1-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 8 12:30:47 kernel usb 1-2.1.4: Product: TransMemory Sep 8 12:30:47 kernel usb 1-2.1.4: Manufacturer: TOSHIBA Sep 8 12:30:47 kernel usb 1-2.1.4: SerialNumber: 001D92AD6BE2C96093800AAA Sep 8 12:30:47 kernel usb-storage 1-2.1.4:1.0: USB Mass Storage device detected Sep 8 12:30:47 kernel scsi host6: usb-storage 1-2.1.4:1.0 Sep 8 12:30:48 kernel scsi 6:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 Sep 8 12:30:48 kernel sd 6:0:0:0: Attached scsi generic sg4 type 0 Sep 8 12:30:48 kernel sd 6:0:0:0: [sdg] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) Sep 8 12:30:48 kernel sd 6:0:0:0: [sdg] Write Protect is off Sep 8 12:30:48 kernel sd 6:0:0:0: [sdg] Mode Sense: 65 44 09 30 Sep 8 12:30:48 kernel sd 6:0:0:0: [sdg] No Caching mode page found Sep 8 12:30:48 kernel sd 6:0:0:0: [sdg] Assuming drive cache: write through Sep 8 12:30:48 kernel sdg: sdg1 Sep 8 12:30:48 kernel sd 6:0:0:0: [sdg] Attached SCSI removable disk Sep 8 12:30:48 ndm Storage::Manager: "Media6": enabled a disk spin down. Sep 8 12:30:48 ndm Storage::Manager: created "Media6", port 2. Sep 8 12:30:48 ndm Storage::Partition: ext3 "75de3ff5-92a4-d701-109e-3cf592a4d701:": filesystem initialized. Sep 8 12:30:48 kernel EXT4-fs (sdg1): mounting ext3 file system using the ext4 subsystem Sep 8 12:30:48 kernel usb 1-2.1.4: reset high-speed USB device number 20 using xhci-mtk Sep 8 12:30:48 kernel usb 1-2.1.4: usbfs: USBDEVFS_CONTROL failed cmd ndm rqt 128 rq 6 len 50 ret -143 Sep 8 12:30:48 ndm Usb::Device: system failed [0xcffd00b1], cannot send after transport endpoint shutdown. Sep 8 12:30:48 ndm Usb::Device: invalid string descriptor. Sep 8 12:30:48 ndm Usb::Device: could not read description strings. Sep 8 12:30:48 kernel EXT4-fs error (device sdg1): ext4_ext_check_inode:510: inode #8: comm ndm: pblk 0 bad header/extent: invalid magic - magic 114, entries 0, max 277(0), depth 0(0) Sep 8 12:30:48 kernel EXT4-fs (sdg1): no journal found Sep 8 12:30:48 ndm Core::FileSystem::Native: failed to mount "/tmp/mnt/75de3ff5-92a4-d701-109e-3cf592a4d701": invalid argument. Sep 8 12:30:48 ndm Storage::Partition: failed to mount. Sep 8 12:30:48 ndm Storage::Partition: ext3 "75de3ff5-92a4-d701-109e-3cf592a4d701:": unable to mount. Sep 8 12:30:48 ndm Storage::Manager: "Media6": failed to register partition "75de3ff5-92a4-d701-109e-3cf592a4d701:". Sep 8 12:30:49 netdata[936] DEVICE-MAPPER ('sdg', 8:96): Cannot open directory '/dev/mapper'. Sep 8 12:30:49 netdata[936] DEVICE-MAPPER ('sdg', 8:96): Cannot open directory '/dev/disk/by-label'. Sep 8 12:30:49 netdata[936] DEVICE-MAPPER ('sdg', 8:96): Cannot open directory '/dev/vx/dsk'. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk.sdg/reads.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk.sdg/writes.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_ops.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_ops.sdg/reads.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_ops.sdg/writes.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_backlog.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_backlog.sdg/backlog.db. Sep 8 12:30:49 netdata[936] RRDSET: chart name 'disk_busy.sdg' on host 'Keenetic-0615' already exists. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_util.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_util.sdg/utilization.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_mops.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_mops.sdg/reads.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_mops.sdg/writes.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_iotime.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_iotime.sdg/reads.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_iotime.sdg/writes.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_await.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_await.sdg/reads.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_await.sdg/writes.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_avgsz.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_avgsz.sdg/reads.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_avgsz.sdg/writes.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_svctm.sdg/main.db. Sep 8 12:30:49 netdata[936] Initializing file /opt/var/cache/netdata/disk_svctm.sdg/svctm.db. Sep 8 12:30:49 netdata[936] DEVICE-MAPPER ('sdg1', 8:97): Cannot open directory '/dev/mapper'. Sep 8 12:30:49 netdata[936] DEVICE-MAPPER ('sdg1', 8:97): Cannot open directory '/dev/disk/by-label'. Sep 8 12:30:49 netdata[936] DEVICE-MAPPER ('sdg1', 8:97): Cannot open directory '/dev/vx/dsk'. Sep 8 12:30:51 netdata[936] host 'Keenetic-0615', chart disk_busy.sdg: took too long to be updated (counter #565, update #566, 61508.015 secs). Resetting it. show media Spoiler { "media": { "Media1": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "Kingston", "product": "DataTraveler 2.0", "serial": "5B651E00029F", "size": "1031798784", "partition": [ { "uuid": "9e1f4c42-b45a-d701-9003-4c42b45ad701", "label": "Keenetic_OPKG", "fstype": "ext4", "state": "MOUNTED", "total": "961764352", "free": "861423616" } ] }, "Media0": { "usb": { "port": 1, "version": "3.00" }, "state": "ACTIVE", "manufacturer": "Intenso", "product": "External USB 3.0", "serial": "20201108102D9", "size": "5000981078016", "partition": [ { "uuid": "f3cff6b6-fe95-d701-0085-f6b6fe95d701", "label": "Keenetic_DATA", "fstype": "ext4", "state": "MOUNTED", "total": "4688046686208", "free": "4051418591232" } ] }, "Media4": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "TOSHIBA", "product": "TransMemory", "serial": "001CC0C60D71E810542F0368", "size": "3926949888", "partition": [ { "uuid": "b8ba1277-55a4-d701-90b8-127755a4d701", "label": "Keenetic_TEMP", "fstype": "ext2", "state": "MOUNTED", "total": "3026038784", "free": "3025892352" }, { "uuid": "00000000-0000-0000-0000-000000000000", "label": "", "fstype": "swap", "state": "MOUNTED", "total": "801107968", "free": "801107968" } ] }, "Media5": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "TOSHIBA", "product": "TransMemory", "serial": "001CC0C440A7EBB0541E0772", "size": "3926949888" }, "Media6": { "usb": { "port": 2, "version": "2.00" }, "state": "ACTIVE", "manufacturer": "TOSHIBA ", "product": "TransMemory ", "serial": "001D92AD6BE2C96093800AAA", "size": "4005527552" } }, "prompt": "(config)" } show usb Spoiler { "usb": { "device": { "UsbModem0": { "DEVICE": "/devices/platform/xhci-mtk/usb1/1-2/1-2.2/1-2.2:1.0", "DEVPATH": "/devices/platform/xhci-mtk/usb1/1-2/1-2.2/1-2.2:1.0/ttyUSB0/tty/ttyUSB0", "alias": "", "subsystem": "network", "port": "2", "power-control": "yes", "usb-version": "2.00" }, "Media1": { "DEVICE": "/devices/platform/xhci-mtk/usb1/1-2/1-2.1/1-2.1.1/1-2.1.1:1.0", "DEVPATH": "/devices/platform/xhci-mtk/usb1/1-2/1-2.1/1-2.1.1/1-2.1.1:1.0/host1/target1:0:0/1:0:0:0/block/sdb", "manufacturer": "Kingston", "product": "DataTraveler 2.0", "serial": "5B651E00029F", "subsystem": "media", "port": "2", "power-control": "yes", "usb-version": "2.00" }, "Media0": { "DEVICE": "/devices/platform/xhci-mtk/usb2/2-1/2-1:1.0", "DEVPATH": "/devices/platform/xhci-mtk/usb2/2-1/2-1:1.0/host0/target0:0:0/0:0:0:0/block/sda", "manufacturer": "Intenso", "product": "External USB 3.0", "serial": "20201108102D9", "subsystem": "media", "port": "1", "power-control": "yes", "usb-version": "3.00" }, "Media4": { "DEVICE": "/devices/platform/xhci-mtk/usb1/1-2/1-2.4/1-2.4:1.0", "DEVPATH": "/devices/platform/xhci-mtk/usb1/1-2/1-2.4/1-2.4:1.0/host4/target4:0:0/4:0:0:0/block/sde", "manufacturer": "TOSHIBA", "product": "TransMemory", "serial": "001CC0C60D71E810542F0368", "subsystem": "media", "port": "2", "power-control": "yes", "usb-version": "2.00" }, "Media5": { "DEVICE": "/devices/platform/xhci-mtk/usb1/1-2/1-2.1/1-2.1.3/1-2.1.3:1.0", "DEVPATH": "/devices/platform/xhci-mtk/usb1/1-2/1-2.1/1-2.1.3/1-2.1.3:1.0/host5/target5:0:0/5:0:0:0/block/sdf", "manufacturer": "TOSHIBA", "product": "TransMemory", "serial": "001CC0C440A7EBB0541E0772", "subsystem": "media", "port": "2", "power-control": "yes", "usb-version": "2.00" }, "Media6": { "DEVICE": "/devices/platform/xhci-mtk/usb1/1-2/1-2.1/1-2.1.4/1-2.1.4:1.0", "DEVPATH": "/devices/platform/xhci-mtk/usb1/1-2/1-2.1/1-2.1.4/1-2.1.4:1.0/host6/target6:0:0/6:0:0:0/block/sdg", "manufacturer": "TOSHIBA ", "product": "TransMemory ", "serial": "001D92AD6BE2C96093800AAA", "subsystem": "media", "port": "2", "power-control": "yes", "usb-version": "2.00" } } }, "prompt": "(config)" } Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 8, 2021 Share Posted September 8, 2021 You must not use this buggy crap as Minitool Partition Wizard is. Plz format with reference ext2/3/4 implementation only: e2fsprogs. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 8, 2021 Author Share Posted September 8, 2021 1 minute ago, Le ecureuil said: You must not use this buggy crap as Minitool Partition Wizard is. Plz format with reference ext2/3/4 implementation only: e2fsprogs. Yeps. Ok master. I am thinking of same. Next step. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 8, 2021 Author Share Posted September 8, 2021 I am not using Linux. So I try Paragon Hard Disk Manager. I will let you know the result. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 8, 2021 Author Share Posted September 8, 2021 Interesting thing is that how to MiniTool format usb bad. Paragon Hard Disk Manager is better than MiniTool. Spoiler Sep 8 13:47:04 kernel usb 1-2.1.3: new high-speed USB device number 21 using xhci-mtk Sep 8 13:47:04 kernel usb 1-2.1.3: New USB device found, idVendor=0930, idProduct=6545 Sep 8 13:47:04 kernel usb 1-2.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 8 13:47:04 kernel usb 1-2.1.3: Product: TransMemory Sep 8 13:47:04 kernel usb 1-2.1.3: Manufacturer: TOSHIBA Sep 8 13:47:04 kernel usb 1-2.1.3: SerialNumber: 001CC0C440A7EBB0541E0772 Sep 8 13:47:04 kernel usb-storage 1-2.1.3:1.0: USB Mass Storage device detected Sep 8 13:47:04 kernel scsi host5: usb-storage 1-2.1.3:1.0 Sep 8 13:47:05 kernel scsi 5:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS Sep 8 13:47:05 kernel sd 5:0:0:0: Attached scsi generic sg3 type 0 Sep 8 13:47:06 kernel sd 5:0:0:0: [sdf] 7669824 512-byte logical blocks: (3.93 GB/3.66 GiB) Sep 8 13:47:06 kernel sd 5:0:0:0: [sdf] Write Protect is off Sep 8 13:47:06 kernel sd 5:0:0:0: [sdf] Mode Sense: 23 00 00 00 Sep 8 13:47:06 kernel sd 5:0:0:0: [sdf] No Caching mode page found Sep 8 13:47:06 kernel sd 5:0:0:0: [sdf] Assuming drive cache: write through Sep 8 13:47:06 kernel sdf: sdf1 Sep 8 13:47:06 kernel sd 5:0:0:0: [sdf] Attached SCSI removable disk Sep 8 13:47:06 ndm Storage::Manager: "Media5": enabled a disk spin down. Sep 8 13:47:06 ndm Storage::Manager: created "Media5", port 2. Sep 8 13:47:06 ndm Storage::Partition: ext3 "a9f5f1c7-3ccb-90e7-23d9-5bfefdf1aff6:": filesystem initialized. Sep 8 13:47:06 kernel EXT4-fs (sdf1): mounting ext3 file system using the ext4 subsystem Sep 8 13:47:07 netdata[936] DEVICE-MAPPER ('sdf', 8:80): Cannot open directory '/dev/mapper'. Sep 8 13:47:07 netdata[936] DEVICE-MAPPER ('sdf', 8:80): Cannot open directory '/dev/disk/by-label'. Sep 8 13:47:07 netdata[936] DEVICE-MAPPER ('sdf', 8:80): Cannot open directory '/dev/vx/dsk'. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_ops.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] Initializing file /opt/var/cache/netdata/disk_qops.sdf/main.db. Sep 8 13:47:07 netdata[936] Initializing file /opt/var/cache/netdata/disk_qops.sdf/operations.db. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_backlog.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_busy.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_util.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_mops.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_iotime.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_await.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_avgsz.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] RRDSET: chart name 'disk_svctm.sdf' on host 'Keenetic-0615' already exists. Sep 8 13:47:07 netdata[936] DEVICE-MAPPER ('sdf1', 8:81): Cannot open directory '/dev/mapper'. Sep 8 13:47:07 netdata[936] DEVICE-MAPPER ('sdf1', 8:81): Cannot open directory '/dev/disk/by-label'. Sep 8 13:47:07 netdata[936] DEVICE-MAPPER ('sdf1', 8:81): Cannot open directory '/dev/vx/dsk'. Sep 8 13:47:07 kernel EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: (null) Sep 8 13:47:07 ndm Storage::Manager: "Media5": registered partition "a9f5f1c7-3ccb-90e7-23d9-5bfefdf1aff6:". Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_space._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/main.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_space._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/avail.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_space._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/used.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_space._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/reserved_for_root.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_inodes._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/main.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_inodes._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/avail.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_inodes._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/used.db. Sep 8 13:47:19 netdata[936] Initializing file /opt/var/cache/netdata/disk_inodes._tmp_mnt_a9f5f1c7_3ccb_90e7_23d9_5bfefdf1aff6/reserved_for_root.db. 1 Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 11, 2021 Author Share Posted September 11, 2021 For best result about partitioning Parted Magic is really magic. Highly recommended if you haven't tried it. It is flawless with virtual machine in Windows environment. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 13, 2021 Author Share Posted September 13, 2021 Hello Community, As a result of 3-4 days of testing and as I have experienced before, the partition on a usb disappears. When I look at the disk with live linux, I can see all partitions. When I plug it back into Keenetic it only sees the Linux Swap partition. Spoiler Sep 13 10:12:35 kernel usb 1-2.4: new high-speed USB device number 15 using xhci-mtk Sep 13 10:12:35 kernel usb 1-2.4: New USB device found, idVendor=0930, idProduct=6545 Sep 13 10:12:35 kernel usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 13 10:12:35 kernel usb 1-2.4: Product: TransMemory Sep 13 10:12:35 kernel usb 1-2.4: Manufacturer: TOSHIBA Sep 13 10:12:35 kernel usb 1-2.4: SerialNumber: 001CC0C60D71E810542F0368 Sep 13 10:12:35 kernel usb-storage 1-2.4:1.0: USB Mass Storage device detected Sep 13 10:12:35 kernel scsi host4: usb-storage 1-2.4:1.0 Sep 13 10:12:36 kernel scsi 4:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS Sep 13 10:12:36 kernel sd 4:0:0:0: Attached scsi generic sg2 type 0 Sep 13 10:12:37 kernel sd 4:0:0:0: [sde] 7669824 512-byte logical blocks: (3.93 GB/3.66 GiB) Sep 13 10:12:37 kernel sd 4:0:0:0: [sde] Write Protect is off Sep 13 10:12:37 kernel sd 4:0:0:0: [sde] Mode Sense: 23 00 00 00 Sep 13 10:12:37 kernel sd 4:0:0:0: [sde] No Caching mode page found Sep 13 10:12:37 kernel sd 4:0:0:0: [sde] Assuming drive cache: write through Sep 13 10:12:37 kernel sde: sde1 sde2 Sep 13 10:12:37 kernel sd 4:0:0:0: [sde] Attached SCSI removable disk Sep 13 10:12:37 ndm Storage::Manager: "Media4": enabled a disk spin down. Sep 13 10:12:37 ndm Storage::Manager: created "Media4", port 2. Sep 13 10:12:37 ndm Storage::Partition: a filesystem with the same label (TEMP, f4d5d7a6-860a-483b-8890-2102af3d31d0) already mounted. Sep 13 10:12:37 ndm Storage::Manager: "Media4": failed to create a new partition. Sep 13 10:12:37 ndm FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/f4d5d7a6-860a-483b-8890-2102af3d31d0": device or resource busy. Sep 13 10:12:37 ndm Storage::Partition: swap "00000000-0000-0000-0000-000000000000:": filesystem initialized. Sep 13 10:12:37 kernel Adding 782332k swap on /dev/sde2. Priority:-3 extents:1 across:782332k Sep 13 10:12:37 ndm Storage::Manager: "Media4": registered partition "00000000-0000-0000-0000-000000000000:". Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/dev/mapper'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/dev/disk/by-label'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/dev/vx/dsk'. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_ops.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_backlog.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_busy.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_util.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_iotime.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_await.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_avgsz.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] RRDSET: chart name 'disk_svctm.sde' on host 'Keenetic-0615' already exists. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde1', 8:65): Cannot open directory '/dev/mapper'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde1', 8:65): Cannot open directory '/dev/disk/by-label'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde1', 8:65): Cannot open directory '/dev/vx/dsk'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde2', 8:66): Cannot open directory '/dev/mapper'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde2', 8:66): Cannot open directory '/dev/disk/by-label'. Sep 13 10:12:38 netdata[859] DEVICE-MAPPER ('sde2', 8:66): Cannot open directory '/dev/vx/dsk'. FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/f4d5d7a6-860a-483b-8890-2102af3d31d0": device or resource busy. Likewise, I saw a warning yesterday when we unmounted and re-mounted the disk of my friend. After restarting the router, the disc mounted successfully. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 15, 2021 Author Share Posted September 15, 2021 The same disk formatted as ext4 is no longer lost. I think it's a bug for ext3. Only syslog is written to this disk. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 16, 2021 Author Share Posted September 16, 2021 Interestingly, the partition of the same disk that I only used to write syslog was gone. Last night, there was 100% cpu and ram usage due to torrent and syslog was continuing to write. When I woke up in the morning, I saw that the partition (called Data) of the disk was gone again. Swap is still there. I'll also try replacing the disk. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 16, 2021 Author Share Posted September 16, 2021 and the whole disk appears on linux. What is mean lock? Who locked? Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 16, 2021 Author Share Posted September 16, 2021 Partition gone at 2:30AM Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 20, 2021 Author Share Posted September 20, 2021 According to these outputs, which one is the problem and the partition is lost. - disk (I tried a different disk this time) - writing syslog to disk - usb hub (but it still works for other usb opkg in the same hub.) - partitions (had the same issue with ext3 and ext4) Spoiler 10.101.0.1 Sep 20 22:34:56 10.101.0.1 user warning ndm Json::Object: AppendMember: duplicate key: "sh". 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 20 using xhci-mtk 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern info kernel usb 1-2.4: device firmware changed 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern info kernel usb 1-2.4: USB disconnect, device number 20 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern info kernel sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern info kernel sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 00 00 08 08 00 00 08 00 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel blk_update_request: I/O error, dev sdf, sector 2056 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel Buffer I/O error on dev sdf1, logical block 1, lost async page write 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern warning kernel EXT4-fs warning (device sdf1): ext4_end_bio:307: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 21117) 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel Buffer I/O error on device sdf1, logical block 20860 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern info kernel sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_wait_block_bitmap:529: comm syslog-ng: Cannot read block bitmap - block_group = 0, block_bitmap = 192 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_wait_block_bitmap:529: comm syslog-ng: Cannot read block bitmap - block_group = 0, block_bitmap = 192 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_wait_block_bitmap:529: comm syslog-ng: Cannot read block bitmap - block_group = 0, block_bitmap = 192 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_discard_preallocations:4075: comm syslog-ng: Error -5 reading block bitmap for 0 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_wait_block_bitmap:529: comm syslog-ng: Cannot read block bitmap - block_group = 0, block_bitmap = 192 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_discard_preallocations:4075: comm syslog-ng: Error -5 reading block bitmap for 0 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern crit kernel EXT4-fs error (device sdf1): ext4_free_branches:1021: inode #13: block 17111: comm syslog-ng: Read failure 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel Aborting journal on device sdf1-8. 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel JBD2: Error -5 detected when updating journal superblock for sdf1-8. 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel JBD2: Error while async write back metadata bh 1. 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel JBD2: Error while async write back metadata bh 192. 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern err kernel JBD2: Error while async write back metadata bh 17111. 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern notice kernel sd 5:0:0:0: [sdf] Stopping disk 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 kern info kernel sd 5:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern info kernel sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 00 00 0e 00 00 00 08 00 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel blk_update_request: I/O error, dev sdf, sector 3584 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel Buffer I/O error on dev sdf1, logical block 192, lost async page write 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern crit kernel EXT4-fs error (device sdf1): ext4_journal_check_start:56: Detected aborted journal 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern crit kernel EXT4-fs (sdf1): Remounting filesystem read-only 10.101.0.1 Sep 20 22:34:57 10.101.0.1 kern err kernel EXT4-fs (sdf1): previous I/O error to superblock detected 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 syslog err syslog-ng[32283] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Sep 20 22:34:57 Keenetic-0615 syslog notice syslog-ng[32283] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern crit kernel EXT4-fs error (device sdf1): ext4_find_entry:1454: inode #2: comm vfs-ctrl-6aa2f1: reading directory lblock 0 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern warning kernel EXT4-fs warning (device sdf1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm vfs-ctrl-6aa2f1: error -5 reading directory block 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern warning kernel EXT4-fs warning (device sdf1): htree_dirblock_to_tree:976: inode #2: lblock 0: comm vfs-ctrl-6aa2f1: error -5 reading directory block 10.101.0.1 Sep 20 22:34:58 10.101.0.1 user info ndm Core::FileSystem::Repository: unregistering "29bf1f34-afcb-4e89-b976-0e9033e236fe:" filesystem... 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: new high-speed USB device number 21 using xhci-mtk 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern err kernel usb 1-2.4: device descriptor read/all, error -71 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: new high-speed USB device number 22 using xhci-mtk 10.101.0.1 Sep 20 22:34:58 10.101.0.1 user info ndm Ntce::Database: cleared classification data. 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: New USB device found, idVendor=0930, idProduct=6544 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: Product: TransMemory 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: Manufacturer: TOSHIBA 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb 1-2.4: SerialNumber: 001D92AD6BE2C96093800AAA 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel usb-storage 1-2.4:1.0: USB Mass Storage device detected 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel scsi host6: usb-storage 1-2.4:1.0 10.101.0.1 Sep 20 22:34:58 10.101.0.1 kern info kernel ndm (3513): drop_caches: 3 10.101.0.1 Sep 20 22:34:58 10.101.0.1 user err ndm Core::FileSystem::Native: unable to disable swap: no device found. 10.101.0.1 Sep 20 22:34:58 10.101.0.1 user info ndm Storage::Manager: "Media5": unregistered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Sep 20 22:34:58 10.101.0.1 user info ndm Storage::Manager: "Media5": removed partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Sep 20 22:34:58 10.101.0.1 user info ndm Core::FileSystem::Repository: unregistering "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:" filesystem... 10.101.0.1 Sep 20 22:34:59 10.101.0.1 kern info kernel scsi 6:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 10.101.0.1 Sep 20 22:34:59 10.101.0.1 kern info kernel sd 6:0:0:0: Attached scsi generic sg2 type 0 10.101.0.1 Sep 20 22:34:59 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 22 using xhci-mtk 10.101.0.1 Sep 20 22:34:59 10.101.0.1 kern err kernel usb 1-2.4: device descriptor read/all, error -71 10.101.0.1 Sep 20 22:34:59 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 22 using xhci-mtk 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sd 6:0:0:0: [sdg] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sd 6:0:0:0: [sdg] Write Protect is off 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sd 6:0:0:0: [sdg] Mode Sense: 65 44 09 30 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sd 6:0:0:0: [sdg] No Caching mode page found 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sd 6:0:0:0: [sdg] Assuming drive cache: write through 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sdg: sdg1 sdg2 10.101.0.1 Sep 20 22:35:00 10.101.0.1 kern info kernel sd 6:0:0:0: [sdg] Attached SCSI removable disk 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg', 8:96): Cannot open directory '/dev/mapper'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg', 8:96): Cannot open directory '/dev/disk/by-label'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg', 8:96): Cannot open directory '/dev/vx/dsk'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 user warning ndm Process: "Ntce::Manager" has been killed. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk.sdg/main.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk.sdg/reads.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk.sdg/writes.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_ops.sdg/main.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_ops.sdg/reads.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_ops.sdg/writes.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_avgsz.sdg/main.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_avgsz.sdg/reads.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_avgsz.sdg/writes.db. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg1', 8:97): Cannot open directory '/dev/mapper'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg1', 8:97): Cannot open directory '/dev/disk/by-label'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg1', 8:97): Cannot open directory '/dev/vx/dsk'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg2', 8:98): Cannot open directory '/dev/mapper'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg2', 8:98): Cannot open directory '/dev/disk/by-label'. 10.101.0.1 Sep 20 22:35:00 10.101.0.1 daemon err netdata[859] DEVICE-MAPPER ('sdg2', 8:98): Cannot open directory '/dev/vx/dsk'. 10.101.0.1 Sep 20 22:35:02 10.101.0.1 daemon info ntce-pace2 starting "0.16". 10.101.0.1 Sep 20 22:35:02 10.101.0.1 daemon info ntce-pace2 using "libc" memory allocator. 10.101.0.1 Sep 20 22:35:02 10.101.0.1 daemon info ntce-pace2 using large memory model. 10.101.0.1 Sep 20 22:35:02 10.101.0.1 user err ndm Network::Interface::Base: unable to find PPTP0 as "Network::Interface::Base". 10.101.0.1 Sep 20 22:35:03 10.101.0.1 daemon info ntce-pace2 R&S PACE2 API version: "337". 10.101.0.1 Sep 20 22:35:03 10.101.0.1 daemon info ntce-pace2 R&S PACE2 build: "21.08.13". 10.101.0.1 Sep 20 22:35:03 10.101.0.1 daemon info ntce-pace2 now running as nobody:nobody. 10.101.0.1 Sep 20 22:35:03 10.101.0.1 daemon info ntce-pace2 ready for processing. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user err ndm Core::FileSystem::Native: failed to unmount "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": device or resource busy. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user err ndm Storage::Partition: failed to unmount. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user info ndm Storage::Manager: "Media5": unregistered partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user err ndm Core::FileSystem::Native: failed to unmount "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": device or resource busy. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user crit ndm FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": device or resource busy. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user info ndm Storage::Manager: "Media5": removed partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user crit ndm Storage::Manager: "Media5": a media was unsafely unplugged without ejecting. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user info ndm Storage::Manager: removed "Media5", port 2. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user info ndm Storage::Manager: "Media6": enabled a disk spin down. 10.101.0.1 Sep 20 22:35:12 10.101.0.1 user info ndm Storage::Manager: created "Media6", port 2. 10.101.0.1 Sep 20 22:35:13 10.101.0.1 user warning ndm Storage::Partition: "/dev/sdg1" has an unknown partition type, ignored. 10.101.0.1 Sep 20 22:35:13 10.101.0.1 user info ndm Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. 10.101.0.1 Sep 20 22:35:13 10.101.0.1 kern info kernel Adding 780284k swap on /dev/sdg2. Priority:-5 extents:1 across:780284k 10.101.0.1 Sep 20 22:35:13 10.101.0.1 user info ndm Storage::Manager: "Media6": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_backlog.sdg/main.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_backlog.sdg/backlog.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] File /opt/var/cache/netdata/disk_busy.sdg/main.db is too old. Clearing it. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] File /opt/var/cache/netdata/disk_busy.sdg/busy.db is too old (last collected 827822 seconds ago, but the database is 8068 seconds). Clearing it. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_util.sdg/main.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_util.sdg/utilization.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_iotime.sdg/main.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_iotime.sdg/reads.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_iotime.sdg/writes.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_await.sdg/main.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_await.sdg/reads.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_await.sdg/writes.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_svctm.sdg/main.db. 10.101.0.1 Sep 20 22:35:14 10.101.0.1 daemon info netdata[859] Initializing file /opt/var/cache/netdata/disk_svctm.sdg/svctm.db. 10.101.0.1 Sep 20 22:35:57 Keenetic-0615 syslog notice syslog-ng[32283] Error suspend timeout has elapsed, attempting to write again; fd='5' 10.101.0.1 Sep 20 22:35:57 Keenetic-0615 syslog err syslog-ng[32283] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Sep 20 22:35:57 Keenetic-0615 syslog notice syslog-ng[32283] Suspending write operation because of an I/O error; fd='5', time_reopen='60' @Le ecureuil Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 21, 2021 Author Share Posted September 21, 2021 it is the gparted image after the situation in my message above while the disk is working. How can the partition be corrupted? The disk with exfat file system attached to peak DSL, which I use in the same way, has been working smoothly for more than 1 week. 🙄 Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 21, 2021 Share Posted September 21, 2021 What does e2fsck say about it? Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 21, 2021 Author Share Posted September 21, 2021 29 minutes ago, Le ecureuil said: What does e2fsck say about it? Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 21, 2021 Author Share Posted September 21, 2021 10.101.0.1 Sep 21 10:46:27 10.101.0.1 kern info kernel scsi host2: usb-storage 1-2.4:1.0 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel scsi 2:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: Attached scsi generic sg2 type 0 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Write Protect is off 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Mode Sense: 65 44 09 30 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] No Caching mode page found 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Assuming drive cache: write through 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sdc: sdc1 sdc2 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Attached SCSI removable disk 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Manager: "Media2": enabled a disk spin down. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Manager: created "Media2", port 2. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user err ndm Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user err ndm Storage::Manager: "Media2": failed to create a new partition. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user crit ndm FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 21, 2021 Author Share Posted September 21, 2021 2 hours ago, yerebakan said: 2 hours ago, yerebakan said: 10.101.0.1 Sep 21 10:46:27 10.101.0.1 kern info kernel scsi host2: usb-storage 1-2.4:1.0 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel scsi 2:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: Attached scsi generic sg2 type 0 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Write Protect is off 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Mode Sense: 65 44 09 30 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] No Caching mode page found 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Assuming drive cache: write through 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sdc: sdc1 sdc2 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Attached SCSI removable disk 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Manager: "Media2": enabled a disk spin down. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Manager: created "Media2", port 2. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user err ndm Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user err ndm Storage::Manager: "Media2": failed to create a new partition. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user crit ndm FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k After fixing all, partition appear again. But when I mount into Keenetic, partition is not available. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 22, 2021 Author Share Posted September 22, 2021 21 hours ago, yerebakan said: After fixing all, partition appear again. But when I mount into Keenetic, partition is not available. I really can't understand why. 😔 Part is corrupted. It doesn't show up when I fix it and mount into Keenetic. I can use the disk in Linux. @Le ecureuil Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 22, 2021 Share Posted September 22, 2021 Did you try to reboot KN before inserting disk after fsck? Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 22, 2021 Author Share Posted September 22, 2021 (edited) 1 hour ago, Le ecureuil said: Did you try to reboot KN before inserting disk after fsck? Checked with e2fsck again while restarting my KN. Yes, partition re-appeared with same UUID. (so syslog is written to file in disk) Some reasons partition gets corrupted. OK. Just syslog send log to this disk. can it happen when too much log line arrives? Shouldn't it continue to work again when I plug it into KN after fixing it? Why doesn't it get proper journal or information without rebooting?@Le ecureuil Edited September 22, 2021 by yerebakan Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 22, 2021 Share Posted September 22, 2021 It seems that stale phantom record of damaged partition stays in memory, and prevents from mounting after fsck. Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 22, 2021 Author Share Posted September 22, 2021 11 minutes ago, Le ecureuil said: It seems that stale phantom record of damaged partition stays in memory, and prevents from mounting after fsck. If that's what you're talking about, I can't get past it by removing it. Is just restarting the solution? Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 27, 2021 Author Share Posted September 27, 2021 It might be a long post. Hopefully we can catch something for the fix. I upgraded my device to 3.7 Beta 3 and when the device was turned on, this disk partition was still not visible. Spoiler [I] Sep 27 05:04:35 kernel: usb 1-2.4: new high-speed USB device number 6 using xhci-mtk [I] Sep 27 05:04:35 kernel: usb 1-2.4: New USB device found, idVendor=0930, idProduct=6544 [I] Sep 27 05:04:35 kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [I] Sep 27 05:04:35 kernel: usb 1-2.4: Product: TransMemory [I] Sep 27 05:04:35 kernel: usb 1-2.4: Manufacturer: TOSHIBA [I] Sep 27 05:04:35 kernel: usb 1-2.4: SerialNumber: 001D92AD6BE2C96093800AAA [I] Sep 27 05:04:35 kernel: usb-storage 1-2.4:1.0: USB Mass Storage device detected [I] Sep 27 05:04:35 kernel: scsi host2: usb-storage 1-2.4:1.0 [I] Sep 27 05:04:36 kernel: sd 2:0:0:0: [sdc] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) [I] Sep 27 05:04:36 kernel: sd 2:0:0:0: [sdc] Write Protect is off [I] Sep 27 05:04:36 kernel: sd 2:0:0:0: [sdc] Mode Sense: 65 44 09 30 [I] Sep 27 05:04:36 kernel: sd 2:0:0:0: [sdc] No Caching mode page found [I] Sep 27 05:04:36 kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through [I] Sep 27 05:04:36 kernel: sdc: sdc1 sdc2 [I] Sep 27 05:04:36 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 05:04:36 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 05:04:36 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 05:04:36 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 05:04:36 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 05:04:36 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 05:04:36 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 05:04:36 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". I removed the disk and when I checked with gparted, the partitions were standing. I rebooted my router with no disk and inserted the disk. Again, there was no partition. But other discs were fine. Spoiler [I] Sep 26 09:49:08 kernel: sd 0:0:0:0: [sda] 1220942646 4096-byte logical blocks: (5.00 TB/4.55 TiB) [I] Sep 26 09:49:08 kernel: sd 0:0:0:0: [sda] Write Protect is off [I] Sep 26 09:49:08 kernel: sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08 [I] Sep 26 09:49:08 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [I] Sep 26 09:49:08 kernel: sda: sda1 [I] Sep 26 09:49:08 kernel: sd 0:0:0:0: [sda] Attached SCSI disk [I] Sep 26 09:49:08 ndm: Storage::Manager: "Media0": enabled a disk spin down. [I] Sep 26 09:49:08 ndm: Storage::Manager: created "Media0", port 1. [I] Sep 26 09:49:08 ndm: Storage::Partition: ext4 "f3cff6b6-fe95-d701-0085-f6b6fe95d701:": filesystem initialized. [I] Sep 26 09:49:06 ndm: Storage::Manager: created "Media1", port 2. [I] Sep 26 09:49:06 ndm: Storage::Partition: ext4 "9e1f4c42-b45a-d701-9003-4c42b45ad701:": filesystem initialized. [W] Sep 26 09:49:07 kernel: EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended [I] Sep 26 09:49:07 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [I] Sep 26 09:49:07 ndm: Storage::Manager: "Media1": registered partition "9e1f4c42-b45a-d701-9003-4c42b45ad701:". [I] Sep 27 05:04:36 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 05:04:36 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 05:04:36 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 05:04:36 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 05:04:36 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 05:04:36 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 05:04:36 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 05:04:36 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". Run e2fsck: I rebooted the device and also tried inserting the disk into another usb port. Spoiler [I] Sep 27 05:29:19 kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk [I] Sep 27 05:29:19 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 05:29:19 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 05:29:19 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 05:29:19 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 05:29:19 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 05:29:19 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 05:29:19 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 05:29:19 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [I] Sep 27 05:29:37 ndm: Storage::Manager: started "Media2" eject. [I] Sep 27 05:29:37 ndm: Core::FileSystem::Repository: unregistering "29bf1f34-afcb-4e89-b976-0e9033e236fe:" filesystem... [I] Sep 27 05:29:37 ndm: Ntce::Database: cleared classification data. [I] Sep 27 05:29:37 kernel: ndm (1832): drop_caches: 3 [I] Sep 27 05:29:37 ndm: Storage::Manager: "Media2": unregistered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [W] Sep 27 05:29:37 kernel: sd 2:0:0:0: [sdc] Stopping disk [I] Sep 27 05:29:37 ndm: Storage::Manager: "Media2": ejected. [I] Sep 27 05:29:37 ndm: Storage::Manager: "Media2": removed partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [I] Sep 27 05:29:37 ndm: Storage::Manager: removed "Media2", port 2. [I] Sep 27 05:30:31 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 05:30:31 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 05:30:31 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 05:30:31 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 05:30:31 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 05:30:31 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 05:30:31 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 05:30:31 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". I put the USB hub and disks back. Error occurred on my disk with OPKG. Spoiler [W] Sep 27 05:30:15 kernel: EXT4-fs warning (device sdb1): ext4_end_bio:307: I/O error -5 writing to inode 242019 (offset 0 size 16384 starting block 973409) [W] Sep 27 05:30:15 kernel: JBD2: Detected IO errors while flushing file data on sdb1-8 [E] Sep 27 05:30:15 kernel: Aborting journal on device sdb1-8. I just unplugged that usb and plugged it back in. Spoiler [I] Sep 27 05:35:27 kernel: scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [I] Sep 27 05:35:27 kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0 [I] Sep 27 05:35:28 kernel: sd 2:0:0:0: [sdc] 2015232 512-byte logical blocks: (1.03 GB/984 MiB) [I] Sep 27 05:35:28 kernel: sd 2:0:0:0: [sdc] Write Protect is off [I] Sep 27 05:35:28 kernel: sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00 [I] Sep 27 05:35:28 kernel: sd 2:0:0:0: [sdc] No Caching mode page found [I] Sep 27 05:35:28 kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through [I] Sep 27 05:35:28 kernel: sdc: sdc1 [I] Sep 27 05:35:28 kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk [I] Sep 27 05:35:28 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 05:35:28 ndm: Storage::Manager: created "Media2", port 2. [I] Sep 27 05:35:28 ndm: Storage::Partition: ext4 "9e1f4c42-b45a-d701-9003-4c42b45ad701:": filesystem initialized. [W] Sep 27 05:35:34 kernel: EXT4-fs (sdc1): warning: maximal mount count reached, running e2fsck is recommended [I] Sep 27 05:35:34 kernel: EXT4-fs (sdc1): 284 orphan inodes deleted [I] Sep 27 05:35:34 kernel: EXT4-fs (sdc1): recovery complete [I] Sep 27 05:35:36 kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [I] Sep 27 05:35:36 ndm: Storage::Manager: "Media2": registered partition "9e1f4c42-b45a-d701-9003-4c42b45ad701:". [I] Sep 27 05:35:37 kernel: EXT4-fs (sdc1): re-mounted. Opts: (null) Seeing suggestions to do e2fsck, I checked the other 2 disks. I rebooted the router and inserted the disks. Again the same media2 did not have a partition. Other discs are fine. Spoiler [I] Sep 27 05:54:40 kernel: sd 0:0:0:0: [sda] Attached SCSI disk [I] Sep 27 05:54:40 ndm: Storage::Manager: "Media0": enabled a disk spin down. [I] Sep 27 05:54:40 ndm: Storage::Manager: created "Media0", port 1. [I] Sep 27 05:54:40 ndm: Storage::Partition: ext4 "f3cff6b6-fe95-d701-0085-f6b6fe95d701:": filesystem initialized. [I] Sep 27 05:54:41 kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [I] Sep 27 05:54:41 ndm: Storage::Manager: "Media0": registered partition "f3cff6b6-fe95-d701-0085-f6b6fe95d701:". [I] Sep 27 05:56:37 kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk [I] Sep 27 05:56:37 ndm: Storage::Manager: "Media1": enabled a disk spin down. [I] Sep 27 05:56:37 ndm: Storage::Manager: created "Media1", port 2. [I] Sep 27 05:56:37 ndm: Storage::Partition: ext4 "9e1f4c42-b45a-d701-9003-4c42b45ad701:": filesystem initialized. [I] Sep 27 05:56:37 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [I] Sep 27 05:56:37 ndm: Storage::Manager: "Media1": registered partition "9e1f4c42-b45a-d701-9003-4c42b45ad701:". [I] Sep 27 05:56:53 kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk [I] Sep 27 05:56:53 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 05:56:53 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 05:56:53 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 05:56:53 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 05:56:53 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 05:56:53 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 05:56:53 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 05:56:53 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". I tried 1-2 more times by plugging it into a different port. Spoiler [I] Sep 27 06:00:18 kernel: usb 1-2.4: new high-speed USB device number 7 using xhci-mtk [I] Sep 27 06:00:19 kernel: usb 1-2.4: New USB device found, idVendor=0930, idProduct=6544 [I] Sep 27 06:00:19 kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [I] Sep 27 06:00:19 kernel: usb 1-2.4: Product: TransMemory [I] Sep 27 06:00:19 kernel: usb 1-2.4: Manufacturer: TOSHIBA [I] Sep 27 06:00:19 kernel: usb 1-2.4: SerialNumber: 001D92AD6BE2C96093800AAA [I] Sep 27 06:00:19 kernel: usb-storage 1-2.4:1.0: USB Mass Storage device detected [I] Sep 27 06:00:19 kernel: scsi host2: usb-storage 1-2.4:1.0 [I] Sep 27 06:00:20 kernel: scsi 2:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0 [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: [sdc] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: [sdc] Write Protect is off [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: [sdc] Mode Sense: 65 44 09 30 [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: [sdc] No Caching mode page found [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through [I] Sep 27 06:00:20 kernel: sdc: sdc1 sdc2 [I] Sep 27 06:00:20 kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk [I] Sep 27 06:00:20 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 06:00:20 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 06:00:20 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 06:00:20 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 06:00:20 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 06:00:20 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 06:00:20 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 06:00:20 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [I] Sep 27 06:01:55 ndm: Storage::Manager: started "Media2" eject. [I] Sep 27 06:01:55 ndm: Core::FileSystem::Repository: unregistering "29bf1f34-afcb-4e89-b976-0e9033e236fe:" filesystem... [I] Sep 27 06:01:55 ndm: Ntce::Database: cleared classification data. [I] Sep 27 06:01:55 kernel: ndm (5107): drop_caches: 3 [I] Sep 27 06:01:55 ndm: Storage::Manager: "Media2": unregistered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [W] Sep 27 06:01:55 kernel: sd 2:0:0:0: [sdc] Stopping disk [I] Sep 27 06:01:55 ntce-pace2: stopped. [I] Sep 27 06:01:55 ndm: Storage::Manager: "Media2": ejected. [I] Sep 27 06:01:55 ndm: Storage::Manager: "Media2": removed partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [I] Sep 27 06:01:55 ndm: Storage::Manager: removed "Media2", port 2. [I] Sep 27 06:02:20 kernel: usb 1-2.1.3: New USB device found, idVendor=0930, idProduct=6544 [I] Sep 27 06:02:20 kernel: usb 1-2.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [I] Sep 27 06:02:20 kernel: usb 1-2.1.3: Product: TransMemory [I] Sep 27 06:02:20 kernel: usb 1-2.1.3: Manufacturer: TOSHIBA [I] Sep 27 06:02:20 kernel: usb 1-2.1.3: SerialNumber: 001D92AD6BE2C96093800AAA [I] Sep 27 06:02:20 kernel: usb-storage 1-2.1.3:1.0: USB Mass Storage device detected [I] Sep 27 06:02:20 kernel: scsi host2: usb-storage 1-2.1.3:1.0 [I] Sep 27 06:02:21 kernel: scsi 2:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 [I] Sep 27 06:02:21 kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0 [I] Sep 27 06:02:21 kernel: sd 2:0:0:0: [sdc] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) [I] Sep 27 06:02:21 kernel: sd 2:0:0:0: [sdc] Write Protect is off [I] Sep 27 06:02:21 kernel: sd 2:0:0:0: [sdc] Mode Sense: 65 44 09 30 [I] Sep 27 06:02:21 kernel: sd 2:0:0:0: [sdc] No Caching mode page found [I] Sep 27 06:02:21 kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through [I] Sep 27 06:02:21 kernel: sdc: sdc1 sdc2 [I] Sep 27 06:02:21 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 06:02:21 ndm: Storage::Manager: created "Media2", port 2. [E] Sep 27 06:02:21 ndm: Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. [E] Sep 27 06:02:21 ndm: Storage::Manager: "Media2": failed to create a new partition. [C] Sep 27 06:02:21 ndm: FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. [I] Sep 27 06:02:21 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 06:02:21 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 06:02:21 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". In the interface, I deleted the /tmp entry under the smb application. The disk was mounted. And I rebooted. Finally the partition is back. Spoiler [I] Sep 27 06:00:39 kernel: EXT4-fs (sdb1): recovery complete [I] Sep 27 06:00:39 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [I] Sep 27 06:00:39 ndm: Storage::Manager: "Media1": registered partition "9e1f4c42-b45a-d701-9003-4c42b45ad701:". [I] Sep 27 06:00:39 ndm: Storage::Manager: "Media2": enabled a disk spin down. [I] Sep 27 06:00:39 kernel: br0: port 1(eth2.1) received tcn bpdu [I] Sep 27 06:00:39 kernel: br0: topology change detected, propagating [I] Sep 27 06:00:39 ndm: Storage::Manager: created "Media2", port 2. [I] Sep 27 06:00:39 ndm: Storage::Partition: ext3 "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:": filesystem initialized. [I] Sep 27 06:00:39 kernel: EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem [W] Sep 27 06:00:39 https-dns-proxy: Query received before bootstrapping is completed, discarding. [W] Sep 27 06:00:39 https-dns-proxy: Query received before bootstrapping is completed, discarding. [I] Sep 27 06:00:39 kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [I] Sep 27 06:00:39 ndm: Storage::Manager: "Media2": registered partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". [I] Sep 27 06:00:39 ndm: Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. [I] Sep 27 06:00:39 kernel: Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k [I] Sep 27 06:00:39 ndm: Storage::Manager: "Media2": registered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". [I] Sep 27 06:00:39 ndm: Storage::Manager: "Media0": enabled a disk spin down. [I] Sep 27 06:00:39 ndm: Storage::Manager: created "Media0", port 1. [I] Sep 27 06:00:39 kernel: EXT4-fs (sdb1): re-mounted. Opts: (null) [I] Sep 27 06:00:39 ndm: Opkg::Manager: /tmp/mnt/9e1f4c42-b45a-d701-9003-4c42b45ad701 mounted to /tmp/mnt/9e1f4c42-b45a-d701-9003-4c42b45ad701. [I] Sep 27 06:00:39 ndm: Opkg::Manager: /tmp/mnt/9e1f4c42-b45a-d701-9003-4c42b45ad701 mounted to /opt/. [I] Sep 27 06:00:39 ndm: Opkg::Manager: /tmp/mnt/9e1f4c42-b45a-d701-9003-4c42b45ad701 initialized. [I] Sep 27 06:00:39 ndm: Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 36976. [I] Sep 27 06:00:39 ndm: Wireguard::Interface: "Wireguard0": adding default route via Wireguard0. [I] Sep 27 06:00:40 ndm: Storage::Partition: ext4 "f3cff6b6-fe95-d701-0085-f6b6fe95d701:": filesystem initialized. I didn't know how to deal with this situation. Why can this problem occur with more than one disk? Why am I getting this result on all the different disks I use to save syslog? @Le ecureuil Quote Link to comment Share on other sites More sharing options...
0 Le ecureuil Posted September 28, 2021 Share Posted September 28, 2021 Your logs clearly states that you have TWO partitions with the same label "TEMP". Do you really have them? Quote Link to comment Share on other sites More sharing options...
0 KYTECHNGAMING Posted September 30, 2021 Author Share Posted September 30, 2021 On 9/28/2021 at 9:41 PM, Le ecureuil said: Your logs clearly states that you have TWO partitions with the same label "TEMP". Do you really have them? This question point the same issue which I informed. No. I am using only one partition which name is TEMP. This usb have 2 partition ext3(temp) and ext4(swap) That's the issue. When the partition is lost, just delete this partition label in smb settings and reboot. Everything should work. Quote Link to comment Share on other sites More sharing options...
Question
KYTECHNGAMING
Ext3 disks are not recognized.
It happened in Hero DSL with 3.7.2 Beta and earlier software as well.
Look Media4 👇
Link to comment
Share on other sites
40 answers to this question
Recommended Posts
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.