KYTECHNGAMING Posted September 7, 2021 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
0 KYTECHNGAMING Posted October 1, 2021 Author Posted October 1, 2021 13 hours ago, yerebakan said: 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. Quote
0 Le ecureuil Posted October 1, 2021 Posted October 1, 2021 Handling of two partitions having the same label was fixed and will be available in the next release. 1 Quote
0 KYTECHNGAMING Posted October 1, 2021 Author Posted October 1, 2021 (edited) 10 hours ago, Le ecureuil said: Handling of two partitions having the same label was fixed and will be available in the next release. Good news 💙🤞 But my problem description was other previous message which it is quoted below. On 9/30/2021 at 7:40 PM, yerebakan said: 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. Why is partition lost? When checking partition, no such issue. I will record a video if it will be happen again. Edited October 1, 2021 by yerebakan Quote
0 Le ecureuil Posted October 2, 2021 Posted October 2, 2021 It's hard to say, but I personally will bet on hardware issues in "usb-port/usb-cable/usb-drive" chain. Logs of disconnections are greatly welcome, so we can properly handle incorrect drive disappearing from USB bus. 1 Quote
0 KYTECHNGAMING Posted October 2, 2021 Author Posted October 2, 2021 1 hour ago, Le ecureuil said: It's hard to say, but I personally will bet on hardware issues in "usb-port/usb-cable/usb-drive" chain. Logs of disconnections are greatly welcome, so we can properly handle incorrect drive disappearing from USB bus. It is very rare that my OPKG disk in the same hub is not visible after restarting the modem. Very rare though. In this case, I just have to unplug the usb and plug it back in. But in case of lost partition, re-mounting it doesn't work. I need to remove /tmp/3947347kdfdnf path from SMB. Quote
0 KYTECHNGAMING Posted October 2, 2021 Author Posted October 2, 2021 (edited) 3 hours ago, Le ecureuil said: It's hard to say, but I personally will bet on hardware issues in "usb-port/usb-cable/usb-drive" chain. Logs of disconnections are greatly welcome, so we can properly handle incorrect drive disappearing from USB bus. 1 hour ago, yerebakan said: It is very rare that my OPKG disk in the same hub is not visible after restarting the modem. Very rare though. In this case, I just have to unplug the usb and plug it back in. But in case of lost partition, re-mounting it doesn't work. I need to remove /tmp/3947347kdfdnf path from SMB. Wow! I've realized now. The disc was gone again at around 6 in the morning. I/O failure hub or disk? I think this recording is what you want to tell me. But on the same hub, the OPKG disk continues to work without any problems. 10.101.0.1 Oct 2 06:06:31 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:31 10.101.0.1 kern err kernel usb 1-2.4: device descriptor read/64, error -71 10.101.0.1 Oct 2 06:06:32 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:32 10.101.0.1 kern warning kernel usb 1-2.4: Device not responding to setup address. 10.101.0.1 Oct 2 06:06:33 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:33 10.101.0.1 kern err kernel usb 1-2.4: device descriptor read/all, error -71 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: device firmware changed 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: USB disconnect, device number 10 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel Aborting journal on device sdc1-8. 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel JBD2: Error -5 detected when updating journal superblock for sdc1-8. 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x2a 2a 00 00 03 4e 58 00 00 08 00 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel blk_update_request: I/O error, dev sdc, sector 216664 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel EXT4-fs warning (device sdc1): ext4_end_bio:307: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 27084) 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel Buffer I/O error on device sdc1, logical block 26827 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern crit kernel EXT4-fs error (device sdc1) in ext4_writepages:2810: IO failure 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel EXT4-fs warning (device sdc1): ext4_end_bio:307: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 27084) 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel Buffer I/O error on device sdc1, logical block 26827 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel sd 2:0:0:0: [sdc] Stopping disk 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: new high-speed USB device number 11 using xhci-mtk 10.101.0.1 Oct 2 06:06:34 10.101.0.1 user info ndm Core::FileSystem::Repository: unregistering "29bf1f34-afcb-4e89-b976-0e9033e236fe:" filesystem... 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: New USB device found, idVendor=0930, idProduct=6544 10.101.0.1 Oct 2 06:06:34 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 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: Product: TransMemory 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: Manufacturer: TOSHIBA 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: SerialNumber: 001D92AD6BE2C96093800AAA 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb-storage 1-2.4:1.0: USB Mass Storage device detected 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel scsi host3: usb-storage 1-2.4:1.0 10.101.0.1 Oct 2 06:06:34 10.101.0.1 user info ndm Ntce::Database: cleared classification data. 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern crit kernel EXT4-fs error (device sdc1): ext4_journal_check_start:56: Detected aborted journal 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern crit kernel EXT4-fs (sdc1): Remounting filesystem read-only 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel ------------[ cut here ]------------ 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel WARNING: CPU: 3 PID: 15846 at fs/fs-writeback.c:2197 __mark_inode_dirty+0x264/0x284 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel bdi-block not registered 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel Modules linked in: eip93_cryptoapi(O) nf_nat_sip nf_conntrack_sip fastvpn(PO) xhci_mtk xhci_hcd nf_nat_ftp nf_conntrack_ftp zram ntc(PO) ensoc_dsl(PO) ensoc_dmt(PO) ensoc_flt(O) nnfm(O) mt7615_ap(PO) ubifs ubi ensoc_eth(PO) nacct(PO) rndis_host qcserial cdc_ether huawei_cdc_ncm asix qmi_wwan option cdc_ncm ccm usb_wwan usbextras(O) gcm seqiv authenc exfat(O) nls_utf8 esp4 zstd kalmia cp210x thfsplus(O) nf_nat_rtsp(O) nls_cp1251 cypress_m8 ax88179_178a usb_storage cdc_acm l2tp_ppp usblp dm9601 sd_mod sr_mod nls_cp437 sierra sg usbnet ext4 tfat(PO) zstd_decompress xfrm_user deflate nls_cp866 chacha20poly1305 echainiv tntfs(PO) af_key pl2303 jffs2 cdc_wdm ghash_generic r8152 l2tp_core rtl8150 zstd_compress aead ftdi_sio ch341 usbserial nf_nat_pptp nf_nat_h323 usbcore nf_conntrack_pptp wireguard 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel xfrm_interface crc32c_generic libphy cdrom tunnel6 resetnds(PO) hmac des_generic mtdoops_proc(O) ansi_cprng ctr jitterentropy_rng gf128mul nf_conntrack_h323 xt_esp chacha_generic zlib_deflate jbd2 nls_base ip6_udp_tunnel poly1305_generic xxhash sch_cake(O) nf_conntrack_proto_gre phr(PO) mbcache nf_conntrack_rtsp(O) xt_policy ndm_storage dummy ip_gre zlib_inflate crc16 loop xfrm4_mode_tunnel md5 scsi_mod udp_tunnel crypto_null xfrm4_mode_transport cbc tsmb(PO) drbg usb_common sit nf_nat_proto_gre xfrm_algo xfrm4_tunnel 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel CPU: 3 PID: 15846 Comm: syslog-ng Tainted: P O 4.9-ndm-5 #2 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel Stack : 00000000 00000000 80528152 00000048 00000048 80528150 8045d2c0 00000009 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 80444f38 830d6f8c 804b4e83 80523ecc 00000895 00000000 77bfeb18 77c05000 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 77c05000 8008de54 00000000 0000000a 80528152 00000000 8044ae28 8aef7c2c 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 8044d404 8008b048 00000895 00000000 00000003 00003de6 8aef7c2c 80444f38 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel ... 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel Call Trace: 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<f3332257>] show_stack+0x2c/0x88 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<8a339aee>] dump_stack+0x9c/0xd4 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<8c645cd5>] __warn+0xe0/0x114 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<04186378>] warn_slowpath_fmt+0x34/0x40 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<0a9ce964>] __mark_inode_dirty+0x264/0x284 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<91040a7c>] generic_update_time+0xa4/0x104 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<0cafa713>] file_update_time+0xc0/0x130 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<75c39b06>] __generic_file_write_iter+0xb8/0x280 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<674566b3>] ext4_llseek+0xb6c/0xf9c [ext4] 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<13864622>] ep_scan_ready_list.constprop.0+0x98/0x21c 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel ---[ end trace a57548a6aa657f34 ]--- 10.101.0.1 Oct 2 06:06:34 Keenetic-0615 syslog err syslog-ng[917] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Oct 2 06:06:34 Keenetic-0615 syslog notice syslog-ng[917] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel ndm (15856): drop_caches: 3 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user err ndm Core::FileSystem::Native: unable to disable swap: no device found. 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user info ndm Storage::Manager: "Media2": unregistered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user info ndm Storage::Manager: "Media2": removed partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user info ndm Core::FileSystem::Repository: unregistering "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:" filesystem... 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel scsi 3:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: Attached scsi generic sg2 type 0 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Write Protect is off 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Mode Sense: 65 44 09 30 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] No Caching mode page found 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Assuming drive cache: write through 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Attached SCSI removable disk 10.101.0.1 Oct 2 06:06:49 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 Oct 2 06:06:49 10.101.0.1 user err ndm Storage::Partition: failed to unmount. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: "Media2": unregistered partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". 10.101.0.1 Oct 2 06:06:49 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 Oct 2 06:06:49 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 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: "Media2": removed partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user crit ndm Storage::Manager: "Media2": a media was unsafely unplugged without ejecting. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: removed "Media2", port 2. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: "Media3": enabled a disk spin down. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: created "Media3", port 2. 10.101.0.1 Oct 2 06:07:34 Keenetic-0615 syslog notice syslog-ng[917] Error suspend timeout has elapsed, attempting to write again; fd='5' 10.101.0.1 Oct 2 06:07:34 Keenetic-0615 syslog err syslog-ng[917] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Oct 2 06:07:34 Keenetic-0615 syslog notice syslog-ng[917] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Oct 2 06:08:34 Keenetic-0615 syslog notice syslog-ng[917] Error suspend timeout has elapsed, attempting to write again; fd='5' 10.101.0.1 Oct 2 06:08:34 Keenetic-0615 syslog err syslog-ng[917] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Oct 2 06:08:34 Keenetic-0615 syslog notice syslog-ng[917] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Oct 2 06:08:46 10.101.0.1 user info ndm Core::Scgi::AuthPool: cleanup: 15 -> 14. opkg disk is mounted on the same hub and usb modem. @Le ecureuil Edited October 2, 2021 by yerebakan Quote
0 Le ecureuil Posted October 2, 2021 Posted October 2, 2021 It's definitely a hardware problem: maybe power is not enough, or connect is not so good. BTW, having disk and modem with pingcheck on the same hub is awful decision. You disk will perform unsafe restart on each pingcheck run and it can lead to hardware damage (or software issues). Quote
0 KYTECHNGAMING Posted October 2, 2021 Author Posted October 2, 2021 21 minutes ago, Le ecureuil said: It's definitely a hardware problem: maybe power is not enough, or connect is not so good. BTW, having disk and modem with pingcheck on the same hub is awful decision. You disk will perform unsafe restart on each pingcheck run and it can lead to hardware damage (or software issues). I am using 5v 5a adapter for usb hub. The modem is plugged in and the switch is not active. Also, ping check is disabled in the settings. I think it might be better to buy a new usb hub or remove the modem. Quote
0 KYTECHNGAMING Posted October 2, 2021 Author Posted October 2, 2021 (edited) This time the usb is seriously injured. 🙃 Edited October 2, 2021 by yerebakan Quote
0 KYTECHNGAMING Posted October 16, 2021 Author Posted October 16, 2021 I have not been experiencing the problems we have written above for more than 10 days. Disk / partition does not disappear when the router is turned off and on or suddenly. A new USB hub seems to have fixed the issues. But I had a similar situation recently when I re-inserted my OPKG disk after safe removal. The disc did not appear. Looks like the xhci(?) driver isn't clearing the registers properly when ejecting disks on a hub. @Le ecureuil Thanks for all. Quote
Question
KYTECHNGAMING
Ext3 disks are not recognized.
It happened in Hero DSL with 3.7.2 Beta and earlier software as well.
Look Media4 👇
{ "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)" }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.