Asus RT-N13U B1 - DD-wrt thread
- Thread starter dinjo
- Start date
yes, i am.
am facing an issue in transmission. night, i put anything for download. in the morning when i check, i see that the downloads have paused with the error - 'no data found! set location blah blah blah....'
the location for downloads is clearly defined. any suggestions?
the location for downloads is clearly defined. any suggestions?
will do, when i see the error the next time.
am using ext3.
perhaps its something to do with what i had attempted a few days back. i had removed my currently operating flash-drive (with the present optware transmission on it, set-up for me by a forum-member), and then attached a 'test' flash-drive in place of it, to learn about installing optware packages and transmission practically on it. after i was done, i had re-attached the original flash-drive back and re-applied the start-up script in the router (an atheros one). seeing this issue since then.
am using ext3.
perhaps its something to do with what i had attempted a few days back. i had removed my currently operating flash-drive (with the present optware transmission on it, set-up for me by a forum-member), and then attached a 'test' flash-drive in place of it, to learn about installing optware packages and transmission practically on it. after i was done, i had re-attached the original flash-drive back and re-applied the start-up script in the router (an atheros one). seeing this issue since then.
+1.[DOUBLEPOST=1409630604][/DOUBLEPOST]I tried to install optware. I got stuck at wget hxxp://www.3iii.dk/linux/optware/optware-install-ddwrt.sh -O /tmp/optware-install.sh
The file was not downloaded. Anyways I pulled the script manually and created the file using vi. However when I went ahead to run the script, I got error "No default Gateway set"
My N13u is set as repeater-bridge. It extends my primary wifi connection (N10E). Can i still set it up?
Last edited:
Working finally.
In repeater bridge setup, the route was pointing to quad-zero. So there was no internet connectivity. Under Advance Routing, I added permanent route for quad-zero to gateway. And it worked.
Link in OP is not working. I used this tutorial to set up. (Someone shared this link 2 pages back..
)
@RajeshJ Check the link in my post.
In repeater bridge setup, the route was pointing to quad-zero. So there was no internet connectivity. Under Advance Routing, I added permanent route for quad-zero to gateway. And it worked.
Code:
$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0 <<<<< was missingLink in OP is not working. I used this tutorial to set up. (Someone shared this link 2 pages back..
)@RajeshJ Check the link in my post.
received the same error today again in the morning. got the dmesg output. here it is:
Code:
root@NETROUTER ~ # dmesg
<7>[ 0.500000] PCI: CLS 0 bytes, default 32
<5>[ 0.500000] gpio_proc: module loaded and /proc/gpio/ created
<5>[ 0.500000] wl0gpio_proc: module loaded and /proc/wl0gpio/ created
<6>[ 0.500000] squashfs: version 3.0 (2006/03/15) Phillip Lougher
<6>[ 0.500000] msgmni has been set to 246
<6>[ 0.500000] io scheduler noop registered
<6>[ 0.500000] io scheduler deadline registered (default)
<6>[ 0.500000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
<6>[ 0.510000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
<6>[ 0.820000] console [ttyS0] enabled
<0>[ 0.830000] guessed flashsize = 8M
<0>[ 0.830000] scanning for root partition
<0>[ 0.840000] tplink uboot detected
<0>[ 0.840000] guessed bootloader size = 20000
<0>[ 0.850000]
<0>[ 0.850000] found squashfs at 130000
<5>[ 0.850000] Creating 8 MTD partitions on "ar7240-nor0":
<5>[ 0.860000] 0x000000000000-0x000000020000 : "RedBoot"
<5>[ 0.870000] 0x000000020000-0x0000007e0000 : "linux"
<5>[ 0.870000] 0x000000130000-0x0000007c0000 : "rootfs"
<5>[ 0.880000] mtd: partition "rootfs" set to be root filesystem
<5>[ 0.880000] 0x0000007c0000-0x0000007e0000 : "ddwrt"
<5>[ 0.890000] 0x0000007e0000-0x0000007f0000 : "nvram"
<5>[ 0.900000] 0x0000007f0000-0x000000800000 : "board_config"
<5>[ 0.900000] 0x000000000000-0x000000800000 : "fullflash"
<5>[ 0.910000] 0x000000000000-0x000000020000 : "fullboot"
<6>[ 0.920000] libphy: Fixed MDIO Bus: probed
<6>[ 0.920000] tun: Universal TUN/TAP device driver, 1.6
<6>[ 0.930000] tun: (C) 1999-2004 Max Krasnyansky <[EMAIL]maxk@qualcomm.com[/EMAIL]>
<6>[ 0.930000] PPP generic driver version 2.4.2
<6>[ 0.940000] PPP BSD Compression module registered
<6>[ 0.940000] PPP Deflate Compression module registered
<6>[ 0.950000] PPP MPPE Compression module registered
<6>[ 0.950000] NET: Registered protocol family 24
<6>[ 0.970000] u32 classifier
<6>[ 0.980000] Performance counters on
<6>[ 0.980000] input device check on
<6>[ 0.980000] Actions configured
<6>[ 0.990000] Netfilter messages via NETLINK v0.30.
<6>[ 0.990000] nf_conntrack version 0.5.0 (1974 buckets, 7896 max)
<4>[ 1.000000] nf_conntrack_rtsp v0.6.21 loading
<4>[ 1.000000] nf_nat_rtsp v0.6.21 loading
<6>[ 1.010000] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 1.010000] TCP: westwood registered
<6>[ 1.020000] TCP: hybla registered
<6>[ 1.020000] TCP: vegas registered
<6>[ 1.020000] NET: Registered protocol family 17
<5>[ 1.030000] Bridge firewalling registered
<6>[ 1.030000] 8021q: 802.1Q VLAN Support v1.8
<6>[ 1.040000] searching for nvram
<6>[ 1.040000] nvram size = 0
<6>[ 1.070000] Atheros AR71xx hardware watchdog driver version 0.1.0
<6>[ 1.080000] ar71xx-wdt: timeout=15 secs (max=107) ref freq=40000000
<6>[ 1.090000] VFS: Mounted root (squashfs filesystem) readonly on device 31: 2.
<6>[ 1.100000] Freeing unused kernel memory: 208K (8030c000 - 80340000)
<7>[ 3.430000] ar71xx-wdt: enabling watchdog timer
<6>[ 3.620000] switch0: Atheros AR8327 switch registered on ag71xx-mdio.0
<6>[ 5.360000] libphy: ag71xx_mdio: probed
<6>[ 5.360000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
<6>[ 5.920000] ag71xx ag71xx.0 eth0: connected to PHY at ag71xx-mdio.0:00 [ui d=004dd033, driver=Atheros AR8216/AR8236/AR8316]
<6>[ 7.170000] Loading modules backported from Linux version master-2013-06-2 7-0-gdcfa6d5
<6>[ 7.180000] Backport generated by backports.git backports-20130617-4-ge322 0f5
<6>[ 7.330000] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 7.330000] cfg80211: World regulatory domain updated:
<6>[ 7.340000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_ gain, max_eirp)
<6>[ 7.350000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 7.350000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
<6>[ 7.360000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
<6>[ 7.370000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 7.380000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<7>[ 7.930000] ath: EEPROM regdomain: 0x0
<7>[ 7.930000] ath: EEPROM indicates default country code should be used
<7>[ 7.930000] ath: doing EEPROM country->regdmn map search
<7>[ 7.930000] ath: country maps to regdmn code: 0x3a
<7>[ 7.930000] ath: Country alpha2 being used: US
<7>[ 7.930000] ath: Regpair used: 0x3a
<7>[ 7.940000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<6>[ 7.940000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=78
<7>[ 7.950000] ath: EEPROM regdomain: 0x0
<7>[ 7.950000] ath: EEPROM indicates default country code should be used
<7>[ 7.950000] ath: doing EEPROM country->regdmn map search
<7>[ 7.950000] ath: country maps to regdmn code: 0x3a
<7>[ 7.950000] ath: Country alpha2 being used: US
<7>[ 7.950000] ath: Regpair used: 0x3a
<7>[ 7.950000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
<6>[ 7.950000] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=72
<6>[ 7.960000] cfg80211: Calling CRDA for country: US
<6>[ 7.970000] cfg80211: Regulatory domain changed to country: US
<6>[ 7.980000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_ gain, max_eirp)
<6>[ 7.980000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
<6>[ 7.990000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
<6>[ 8.000000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 8.010000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 8.020000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 8.020000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
<6>[ 8.030000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
<6>[ 8.480000] usbcore: registered new interface driver usbfs
<6>[ 8.480000] usbcore: registered new interface driver hub
<6>[ 8.490000] usbcore: registered new device driver usb
<6>[ 8.570000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>[ 8.610000] ar71xx-ehci ar71xx-ehci.0: Atheros AR91xx built-in EHCI contro ller
<6>[ 8.620000] ar71xx-ehci ar71xx-ehci.0: new USB bus registered, assigned bu s number 1
<4>[ 8.630000] ehci_reset Intialize USB CONTROLLER in host mode: 13
<4>[ 8.640000] ehci_reset Port Status 1c000000
<6>[ 8.670000] ar71xx-ehci ar71xx-ehci.0: irq 3, io mem 0x1b000000
<6>[ 8.690000] ar71xx-ehci ar71xx-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 8.690000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 8.700000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumb er=1
<6>[ 8.710000] usb usb1: Product: Atheros AR91xx built-in EHCI controller
<6>[ 8.710000] usb usb1: Manufacturer: Linux 3.10.2 ehci_hcd
<6>[ 8.720000] usb usb1: SerialNumber: platform
<6>[ 8.720000] hub 1-0:1.0: USB hub found
<6>[ 8.730000] hub 1-0:1.0: 1 port detected
<6>[ 8.790000] ehci-pci: EHCI PCI platform driver
<6>[ 8.980000] eth0: link up (1000Mbps/Full duplex)
<5>[ 9.040000] SCSI subsystem initialized
<6>[ 9.090000] usb 1-1: new high-speed USB device number 2 using ar71xx-ehci
<6>[ 9.270000] usbcore: registered new interface driver usb-storage
<6>[ 9.300000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
<6>[ 9.300000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumbe r=0
<6>[ 9.310000] usb 1-1: Product: USB2.0 Hub
<6>[ 9.340000] hub 1-1:1.0: USB hub found
<6>[ 9.340000] hub 1-1:1.0: 4 ports detected
<6>[ 9.410000] usbcore: registered new interface driver usblp
<6>[ 9.630000] usb 1-1.1: new high-speed USB device number 3 using ar71xx-ehc i
<6>[ 9.740000] usb 1-1.1: New USB device found, idVendor=18a5, idProduct=0302
<6>[ 9.740000] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNum ber=3
<6>[ 9.750000] usb 1-1.1: SerialNumber: 12070570000489
<6>[ 9.760000] usb-storage 1-1.1:1.0: USB Mass Storage device detected
<6>[ 9.770000] scsi0 : usb-storage 1-1.1:1.0
<6>[ 9.850000] usb 1-1.2: new high-speed USB device number 4 using ar71xx-ehc i
<6>[ 9.960000] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5567
<6>[ 9.960000] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNum ber=3
<6>[ 9.970000] usb 1-1.2: Product: Cruzer Blade
<6>[ 9.970000] usb 1-1.2: Manufacturer: SanDisk
<6>[ 9.980000] usb 1-1.2: SerialNumber: 2906800C99B1DB0F
<6>[ 9.990000] usb-storage 1-1.2:1.0: USB Mass Storage device detected
<6>[ 10.000000] scsi1 : usb-storage 1-1.2:1.0
<4>[ 10.950000] lzma_compress: module license 'unspecified' taints kernel.
<4>[ 10.960000] Disabling lock debugging due to kernel taint
<5>[ 11.010000] scsi 1:0:0:0: Direct-Access SanDisk Cruzer Blade 8.02 PQ: 0 ANSI: 0 CCS
<5>[ 11.020000] sd 1:0:0:0: [sda] 7856127 512-byte logical blocks: (4.02 GB/3. 74 GiB)
<5>[ 11.040000] sd 1:0:0:0: [sda] Write Protect is off
<7>[ 11.040000] sd 1:0:0:0: [sda] Mode Sense: 45 00 00 08
<3>[ 11.040000] sd 1:0:0:0: [sda] No Caching mode page present
<3>[ 11.050000] sd 1:0:0:0: [sda] Assuming drive cache: write through
<3>[ 11.060000] sd 1:0:0:0: [sda] No Caching mode page present
<3>[ 11.060000] sd 1:0:0:0: [sda] Assuming drive cache: write through
<6>[ 11.080000] sda: sda1 sda2
<3>[ 11.080000] sd 1:0:0:0: [sda] No Caching mode page present
<3>[ 11.090000] sd 1:0:0:0: [sda] Assuming drive cache: write through
<5>[ 11.100000] sd 1:0:0:0: [sda] Attached SCSI removable disk
<5>[ 11.240000] scsi 0:0:0:0: Direct-Access Verbatim PQ: 0 ANSI: 4
<5>[ 11.250000] sd 0:0:0:0: [sdb] 62259200 512-byte logical blocks: (31.8 GB/2 9.6 GiB)
<5>[ 11.270000] sd 0:0:0:0: [sdb] Write Protect is off
<7>[ 11.280000] sd 0:0:0:0: [sdb] Mode Sense: 43 00 00 00
<3>[ 11.290000] sd 0:0:0:0: [sdb] No Caching mode page present
<3>[ 11.290000] sd 0:0:0:0: [sdb] Assuming drive cache: write through
<3>[ 11.310000] sd 0:0:0:0: [sdb] No Caching mode page present
<3>[ 11.310000] sd 0:0:0:0: [sdb] Assuming drive cache: write through
<6>[ 11.330000] sdb: sdb1
<3>[ 11.330000] sd 0:0:0:0: [sdb] No Caching mode page present
<3>[ 11.340000] sd 0:0:0:0: [sdb] Assuming drive cache: write through
<5>[ 11.340000] sd 0:0:0:0: [sdb] Attached SCSI removable disk
<6>[ 11.370000] jffs2: version 2.2. (NAND) (ZLIB) (LZMA) (RTIME) (CMODE_SIZE) © 2001-2006 Red Hat, Inc.
<3>[ 11.390000] jffs2: Too few erase blocks (2)
<6>[ 12.480000] kjournald starting. Commit interval 5 seconds
<4>[ 12.480000] EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 12.600000] EXT3-fs (sda1): using internal journal
<6>[ 12.750000] EXT3-fs (sda1): recovery complete
<6>[ 12.750000] EXT3-fs (sda1): mounted filesystem with writeback data mode
<6>[ 12.790000] device vlan1 entered promiscuous mode
<6>[ 12.790000] device eth0 entered promiscuous mode
<6>[ 12.820000] br0: port 1(vlan1) entered forwarding state
<6>[ 12.830000] br0: port 1(vlan1) entered forwarding state
<6>[ 13.710000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
<6>[ 14.050000] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 14.060000] cfg80211: World regulatory domain updated:
<6>[ 14.060000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_ gain, max_eirp)
<6>[ 14.070000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 14.080000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
<6>[ 14.090000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
<6>[ 14.090000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 14.100000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
<6>[ 14.150000] cfg80211: Calling CRDA for country: GB
<6>[ 14.160000] cfg80211: Regulatory domain changed to country: GB
<6>[ 14.160000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_ gain, max_eirp)
<6>[ 14.170000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 200 0 mBm)
<6>[ 14.180000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 200 0 mBm)
<6>[ 14.190000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 200 0 mBm)
<6>[ 14.200000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 270 0 mBm)
<6>[ 14.200000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
<6>[ 14.830000] br0: port 1(vlan1) entered forwarding state
<6>[ 14.920000] device ath0 entered promiscuous mode
<6>[ 15.300000] br0: port 2(ath0) entered forwarding state
<6>[ 15.300000] br0: port 2(ath0) entered forwarding state
<6>[ 17.300000] br0: port 2(ath0) entered forwarding state
<6>[ 18.470000] device vlan2 entered promiscuous mode
<6>[ 18.550000] device vlan2 left promiscuous mode
<6>[ 47.110000] kjournald starting. Commit interval 5 seconds
<4>[ 47.120000] EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 47.130000] EXT3-fs (sda1): using internal journal
<6>[ 47.130000] EXT3-fs (sda1): mounted filesystem with writeback data mode
<6>[ 172.250000] kjournald starting. Commit interval 5 seconds
<4>[ 172.250000] EXT3-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 172.270000] EXT3-fs (sdb1): using internal journal
<6>[ 172.270000] EXT3-fs (sdb1): recovery complete
<6>[ 172.280000] EXT3-fs (sdb1): mounted filesystem with writeback data mode
<6>[ 2661.750000] device vlan2 entered promiscuous mode
<6>[ 2661.770000] device vlan2 left promiscuous mode
<6>[ 2752.880000] device vlan2 entered promiscuous mode
<6>[ 2752.900000] device vlan2 left promiscuous mode
<6>[12147.110000] device vlan2 entered promiscuous mode
<6>[12147.130000] device vlan2 left promiscuous modesomething seems fishy towards the end (the 'e2fsck is recommended' lines). any suggestions?
P.S. - sdb1 is the drive where the downloads are stored. am guessing that mtnl resets the connection by morning, and it is when this happens.
Last edited:
axis.meister
Disciple
Have you done that already? Have you run e2fsck on the USB-Stick on a Linux Machine. Would suggest you do that. I can see you are using EXT3 so there should not be any corruption issues due to disconnection. But it wouldn't hurt to just let it run on the stick once.
thanks for the response! yes; i made an entry for sdb1 in fstab, but the only change it has made is, the downloads now i see in the morning are paused, instead of showing up the data-location error, as it used to happen earlier. i have been contemplating either re-installing rtorrent (had been unsuccessful in running that properly earlier), or re-install optware & xmission. then a few minutes back, it struck me why not try e2fsck, and then suddenly i saw your post!
yes, i had refrained from running e2fsck earlier, as i deemed it to be a bit risky. but will run it today & see.
yes, i had refrained from running e2fsck earlier, as i deemed it to be a bit risky. but will run it today & see.
Last edited:
so i ran 'fsck' in ubuntu, for the drive containing optware. this is the output i got (finished in no time):
for the storage flash-drive, i had run fsck, but forgot to record its output. it had found one (bad?) superblock, IIRC. i took a back-up of the contents and reformatted it. will check the downloads-status tomorrow morning and see. if i encounter the error again, will then re-schedule fsck-check and alter the mount-counts and then see. even if that fails (though i doubt), will then re-install transmission in another flash-drive (have kept a fresh flash-drive with optware installed prepared).
Code:
root@ohtiam-virtual-machine:~# fsck.ext3 -C 0 -y -v -f /dev/sdb1
e2fsck 1.42.9 (4-Feb-2014)
Backing up journal inode block information.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
OPTWARE: ***** FILE SYSTEM WAS MODIFIED *****
7904 inodes used (6.05%, out of 130560)
33 non-contiguous files (0.4%)
11 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 952/21/0
82685 blocks used (15.84%, out of 522081)
0 bad blocks
0 large files
5400 regular files
2422 directories
0 character device files
0 block device files
0 fifos
0 links
73 symbolic links (73 fast symbolic links)
0 sockets
------------
7895 filesfor the storage flash-drive, i had run fsck, but forgot to record its output. it had found one (bad?) superblock, IIRC. i took a back-up of the contents and reformatted it. will check the downloads-status tomorrow morning and see. if i encounter the error again, will then re-schedule fsck-check and alter the mount-counts and then see. even if that fails (though i doubt), will then re-install transmission in another flash-drive (have kept a fresh flash-drive with optware installed prepared).
glad to tell you all that the issue seems to have been resolved! no more download pauses or errors seen in xmission in the morning. i ran fsck on the optware as well as the storage flash-drives, and indeed that seems to have cured the malady. now remains rescheduling the checks and altering the mount-counts.
(for anyone who might be wanting to run fsck but not knowing where to start from, this is what i did:
- connected each flash-drive to my Ubuntu-VM
- check the mount-points by issuing the cmd
- note the partition/mount-point of your flash-drive
- issue the unmount cmd
[where, supposing, /dev/sdb1 is the partition of the flash-drive to be unmounted]
- then, typed the code
[my flash-drive has ext3 filesystem; use 'fsck.ext2' in the cmd, or simply, 'fsck', if your flash-drive has ext2 FS or anything else]
- one could also use the code
[this will just check the filesystem for any errors, and if none encountered, will cease the operation; to anyway continue even if the filesystem is clean, include the '-f' parameter too in the cmd, and to answer 'yes' to go ahead with each step for which fsck will ask you permission for, also include the '-y' parameter in the cmd]
- remount, and check if everything's well
)[DOUBLEPOST=1410420321][/DOUBLEPOST]but one thing which i have not been able to rectify still. my first download that i did with transmission, it keeps adding back to the daemon even if deleted and trashed alongwith the data, everytime (done manually too, using WinSCP). this started after i upgraded xmission from v2.82 to v2.84. to do that, i had first uninstalled (not purged; just removed using the 'opkg remove >pkg>' cmd on optware) the earlier version, then installed the latest version. any suggestions on how to rectify that?
(for anyone who might be wanting to run fsck but not knowing where to start from, this is what i did:
- connected each flash-drive to my Ubuntu-VM
- check the mount-points by issuing the cmd
Code:
mount- issue the unmount cmd
Code:
umount /dev/sdb1- then, typed the code
Code:
fsck.ext3 -y -v -f -C 0 /dev/sdb1- one could also use the code
Code:
fsck.ext3 -v -C 0 /dev/sdb1- remount, and check if everything's well
Code:
mount -a
Last edited:
is anyone here using pyload to DL videos off youtube?
alright. thanks! i downloaded a few ebooks using pyload, but not anything from any file-sharing site. had also read a bit about youtube-dl, but didn't know we could use it on a headless server too. will need to read how to install and get it working on my atheros router.
and am using rtorrent+ntorrent+avalanche-rt now on my router, instead of transmission. combo working well.
and am using rtorrent+ntorrent+avalanche-rt now on my router, instead of transmission. combo working well.
rutorrent failed to run, despite numerous tweaks in settings, and the support in the rutorrent forums is next-to-none.
will check qbittorrent too, but as this is also not in the repo, am doubtful that it would run. will try though.
will check qbittorrent too, but as this is also not in the repo, am doubtful that it would run. will try though.