Deluge load Transmission list

I seriously hope you’re right, that would save me SO much work. I’m glad I didn’t format it yet since I wasn’t able to backup the stick, I used win32diskimager but it crashes half way through.

The fsck.ext2 thing was exactly why I asked your opinion, it looked strange to me.
If it is corrupted though and unreachable I’m more concerned with what CAUSED the problem if there is no solution because if something in the code F’s it up it has to be hunted down ofcourse :).

Anyway back on topic.

I did an OSMC installation first but I decided to flash my old SD install of RaspBMC on my SD. So it’s not a USB install, I manually switched it USB and just added the image to a USB stick a long time ago aswell.

If I start RaspBMC it mentions “Removeable Hardware Detected” so it does recognize it because I disconnected the other USB devices.

ls dev/* output:

root@raspbmc:/home/pi# ls dev/*
ls: cannot access dev/*: No such file or directory

dmesg output, i’m not sure if I got everything because my KiTTY screen won’t scroll up any further:

    .bss : 0xc09ef94c - 0xc0a42fe9   ( 334 kB)
Preemptible hierarchical RCU implementation.
NR_IRQS:394
sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967ms
Switching to timer-based delay loop
Console: colour dummy device 80x30
console [tty0] enabled
Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00        BogoMIPS (lpj=10000)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys bfqio
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc04d8b60 - 0xc04d8bbc
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
NET: Registered protocol family 16
DMA: preallocated 4096 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
bcm2708.uart_clock = 0
mailbox: Broadcom VideoCore Mailbox driver
bcm2708_vcio: mailbox at f200b880
bcm_power: Broadcom power driver
bcm_power_open() -> 0
bcm_power_request(0, 8)
bcm_mailbox_read -> 00000080, 0
bcm_power_request -> 0
Serial: AMBA PL011 UART driver
dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83, base_baud = 0) is a PL011 rev3
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switched to clocksource stc
FS-Cache: Loaded
CacheFiles: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
bcm2708_dma: DMA manager at f2007000
bcm2708_gpio: bcm2708_gpio_probe c09c61f0
vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
FS-Cache: Netfs 'nfs' registered for caching
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
msgmni has been set to 617
Key type asymmetric registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered
io scheduler bfq registered (default)
BFQ I/O-scheduler version: v7r4
BCM2708FB: allocated DMA memory 532c0000
BCM2708FB: allocated DMA channel 0 @ f2007000
Console: switching to colour frame buffer device 240x67
uart-pl011 dev:f1: no DMA platform data
brd: module loaded
loop: module loaded
vchiq: vchiq_init_state: slot_zero = 0xd4804000, is_master = 0
bcm2708_spi bcm2708_spi.0: master is unqueued, this is deprecated
bcm2708_spi bcm2708_spi.0: SPI Controller at 0x20204000 (irq 80)
usbcore: registered new interface driver ax88179_178a
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver cdc_ncm
dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Core Release: 2.80a
Setting default values for core params
Finished setting default values for core params
Using Buffer DMA mode
Periodic Transfer Interrupt Enhancement - disabled
Multiprocessor Interrupt Enhancement - disabled
OTG VER PARAM: 0, OTG VER FLAG: 0
Dedicated Tx FIFOs mode
WARN::dwc_otg_hcd_init:1042: FIQ DMA bounce buffers: virt = 0xd4c27000 dma = 0x5       3318000 len=9024
FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
dwc_otg: Microframe scheduler enabled
WARN::hcd_init:473: FIQ at 0xc037ce44
WARN::hcd_init:474: FIQ ASM at 0xc037d0f8 length 36
WARN::hcd_init:500: MPHI regs_base at 0xd4c1c000
dwc_otg bcm2708_usb: DWC OTG Controller
dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
Init: Port Power? op_state=1
Init: Power Port (0)
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DWC OTG Controller
usb usb1: Manufacturer: Linux 3.12.21 dwc_otg_hcd
usb usb1: SerialNumber: bcm2708_usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
dwc_otg: FIQ enabled
dwc_otg: NAK holdoff enabled
dwc_otg: FIQ split-transaction FSM enabled
Module dwc_common_port init
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: dm-devel@redhat.com
bcm2835-cpufreq: min=1100000 max=1100000 cur=1100000
bcm2835-cpufreq: switching to governor ondemand
bcm2835-cpufreq: switching to governor ondemand
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci: Enable low-latency mode
mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMA
mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
zram: Created 1 device(s) ...
TCP: westwood registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
Key type dns_resolver registered
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 4376K (c0572000 - c09b8000)
mmc0: new high speed SDHC card at address 59b4
mmcblk0: mmc0:59b4 NCard 7.37 GiB
 mmcblk0: p1 p2
Indeed it is in host mode hprt0 = 00021501
usb 1-1: new high-speed USB device number 2 using dwc_otg
Indeed it is in host mode hprt0 = 00001101
usb 1-1: New USB device found, idVendor=0424, idProduct=9512
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 3 ports detected
usb 1-1.1: new high-speed USB device number 3 using dwc_otg
usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
smsc95xx v1.0.4
smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx US       B 2.0 Ethernet, b8:27:eb:35:bd:ed
usb 1-1.2: new high-speed USB device number 4 using dwc_otg
usb 1-1.2: New USB device found, idVendor=8564, idProduct=1000
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2: Product: Mass Storage Device
usb 1-1.2: Manufacturer: JetFlash
usb 1-1.2: SerialNumber: 3361965122
usb-storage 1-1.2:1.0: USB Mass Storage device detected
scsi0 : usb-storage 1-1.2:1.0
scsi 0:0:0:0: Direct-Access     JetFlash Transcend 16GB   1.00 PQ: 0 ANSI: 6
sd 0:0:0:0: [sda] 30867456 512-byte logical blocks: (15.8 GB/14.7 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
sd 0:0:0:0: [sda] Write cache: disabled, read cache: disabled, doesn't support D       PO or FUA
 sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI removable disk
EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
udevd[154]: starting version 175
bcm2708_i2c_init_pinmode(0,0)
bcm2708_i2c_init_pinmode(0,1)
bcm2708_i2c bcm2708_i2c.0: BSC0 Controller at 0x20205000 (irq 79) (baudrate 1000       00)
bcm2708_i2c_init_pinmode(1,2)
bcm2708_i2c_init_pinmode(1,3)
bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x20804000 (irq 79) (baudrate 1000       00)
bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
pcm512x 1-004c: Failed to reset device: -5
pcm512x: probe of 1-004c failed with error -5
EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
bcm2835-cpufreq: switching to governor performance
bcm2835-cpufreq: switching to governor performance
FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt.        Please run fsck.
ip_tables: (C) 2000-2006 Netfilter Core Team
Console: switching to colour dummy device 80x30
nf_conntrack version 0.5.0 (5008 buckets, 20032 max)
NET: Registered protocol family 10
smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Plea       se run fsck.
EXT4-fs (sda2): warning: mounting fs with errors, running e2fsck is recommended
bcm2835-cpufreq: switching to governor ondemand
bcm2835-cpufreq: switching to governor ondemand
usb 1-1.2: reset high-speed USB device number 4 using dwc_otg
usb 1-1.2: reset high-speed USB device number 4 using dwc_otg
bcm2708 watchdog, heartbeat=10 sec (nowayout=0)
usb 1-1.2: reset high-speed USB device number 4 using dwc_otg
usb 1-1.2: reset high-speed USB device number 4 using dwc_otg
usb 1-1.2: reset high-speed USB device number 4 using dwc_otg
sd 0:0:0:0: Device offlined - not ready after error recovery
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda]
Result: hostbyte=0x05 driverbyte=0x00
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x2a: 2a 00 00 02 50 00 00 00 08 00
end_request: I/O error, dev sda, sector 151552
Buffer I/O error on device sda2, logical block 0
lost page write due to I/O error on sda2
EXT4-fs (sda2): recovery complete
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda2): error count: 66
EXT4-fs (sda2): initial error at 5: ext4_lookup:1437: inode 2
EXT4-fs (sda2): last error at 3: ext4_lookup:1437: inode 2

Sorry, I meant /dev/* not dev/*

Your dmesg seems to show the USB is on its last legs there I’m afraid. Did you notice it going bad on Raspbmc at all

S

On it’s last legs as in, it’s going to corrupt or it’s going to die on me because this thing is brand new and (as you can see in the dmesg) it was an expensive Transcend.

I noticed absolutely nothing, it ran buttery smooth during the night, I woke up, switched the channel to my Rpi and suddenly a kernel panic. I never unmounted it or did anything else with it, it just sat in my Pi running my OS 24/7 since uhmm October last year, maybe a little earlier but not that long.

here is my ls /dev/*

[code]root@raspbmc:/home/pi# ls /dev/*
/dev/autofs /dev/ptmx /dev/tty1 /dev/tty36 /dev/tty62
/dev/btrfs-control /dev/ram0 /dev/tty10 /dev/tty37 /dev/tty63
/dev/cachefiles /dev/ram1 /dev/tty11 /dev/tty38 /dev/tty7
/dev/console /dev/ram10 /dev/tty12 /dev/tty39 /dev/tty8
/dev/cpu_dma_latency /dev/ram11 /dev/tty13 /dev/tty4 /dev/tty9
/dev/fb0 /dev/ram12 /dev/tty14 /dev/tty40 /dev/ttyAMA0
/dev/full /dev/ram13 /dev/tty15 /dev/tty41 /dev/ttyprintk
/dev/fuse /dev/ram14 /dev/tty16 /dev/tty42 /dev/uinput
/dev/i2c-0 /dev/ram15 /dev/tty17 /dev/tty43 /dev/urandom
/dev/i2c-1 /dev/ram2 /dev/tty18 /dev/tty44 /dev/vc-mem
/dev/kmsg /dev/ram3 /dev/tty19 /dev/tty45 /dev/vchiq
/dev/log /dev/ram4 /dev/tty2 /dev/tty46 /dev/vcs
/dev/loop-control /dev/ram5 /dev/tty20 /dev/tty47 /dev/vcs1
/dev/loop0 /dev/ram6 /dev/tty21 /dev/tty48 /dev/vcs2
/dev/loop1 /dev/ram7 /dev/tty22 /dev/tty49 /dev/vcs3
/dev/loop2 /dev/ram8 /dev/tty23 /dev/tty5 /dev/vcs4
/dev/loop3 /dev/ram9 /dev/tty24 /dev/tty50 /dev/vcs5
/dev/loop4 /dev/random /dev/tty25 /dev/tty51 /dev/vcs6
/dev/loop5 /dev/sda /dev/tty26 /dev/tty52 /dev/vcsa
/dev/loop6 /dev/sda1 /dev/tty27 /dev/tty53 /dev/vcsa1
/dev/loop7 /dev/sda2 /dev/tty28 /dev/tty54 /dev/vcsa2
/dev/mem /dev/sndstat /dev/tty29 /dev/tty55 /dev/vcsa3
/dev/mmcblk0 /dev/spidev0.0 /dev/tty3 /dev/tty56 /dev/vcsa4
/dev/mmcblk0p1 /dev/spidev0.1 /dev/tty30 /dev/tty57 /dev/vcsa5
/dev/mmcblk0p2 /dev/stderr /dev/tty31 /dev/tty58 /dev/vcsa6
/dev/network_latency /dev/stdin /dev/tty32 /dev/tty59 /dev/watchdog
/dev/network_throughput /dev/stdout /dev/tty33 /dev/tty6 /dev/xconsole
/dev/null /dev/tty /dev/tty34 /dev/tty60 /dev/zero
/dev/ppp /dev/tty0 /dev/tty35 /dev/tty61 /dev/zram0

/dev/block:
179:0 1:0 1:11 1:14 1:3 1:6 1:9 7:1 7:4 7:7 8:2
179:1 1:1 1:12 1:15 1:4 1:7 253:0 7:2 7:5 8:0
179:2 1:10 1:13 1:2 1:5 1:8 7:0 7:3 7:6 8:1

/dev/bsg:
0:0:0:0

/dev/bus:
usb

/dev/char:
10:130 153:0 1:5 4:1 4:19 4:28 4:37 4:46 4:55 4:7 7:129 7:6
10:235 153:1 1:7 4:10 4:2 4:29 4:38 4:47 4:56 4:8 7:130 89:0
10:236 162:0 1:8 4:11 4:20 4:3 4:39 4:48 4:57 4:9 7:131 89:1
10:237 189:0 1:9 4:12 4:21 4:30 4:4 4:49 4:58 5:0 7:132
10:60 189:1 204:64 4:13 4:22 4:31 4:40 4:5 4:59 5:1 7:133
10:61 189:2 251:0 4:14 4:23 4:32 4:41 4:50 4:6 5:2 7:134
10:62 189:3 252:0 4:15 4:24 4:33 4:42 4:51 4:60 5:3 7:2
10:63 1:1 253:0 4:16 4:25 4:34 4:43 4:52 4:61 7:0 7:3
116:33 1:11 29:0 4:17 4:26 4:35 4:44 4:53 4:62 7:1 7:4
13:63 1:3 4:0 4:18 4:27 4:36 4:45 4:54 4:63 7:128 7:5

/dev/disk:
by-id by-path by-uuid

/dev/fd:
0 1 2 3

/dev/input:
mice

/dev/mapper:
control

/dev/net:
tun

/dev/pts:
0

/dev/raw:
rawctl

/dev/shm:

/dev/snd:

[/code]

A USB drive can die after 3 mins or 5 years no matter how expensive it is.
Sam is saying it’s about to die, so it needs to be replaced.

Running since October maybe even reading and writing almost constantly 24/7 is a lot of reads and writes. That means it will reach it’s estimated usage in a very short time. USB drives are not estimated to run 24/7 ever :slight_smile:

Yeah but come on, that’s one F-ing expensinve hobby to run a Pi off of USB then!
Ofcourse it had more reads and writes, Couchpotato was running, Transmission was running, Sickrage was running and the OS was running but nothing was physically stored on the OS itself, all of that went to the USB HDD.

I just checked the package though, it says limited lifetime warranty so I might actually be able to get a free new one :P.

But still, are you guys certain it’s running on it’s last legs? Out of what do you exactly get that information?
I really noticed no reduction in speed, response time or anything. It was working exactly as it did when I first bought it and the next morning this happened.

If this is really the case though I wonder 2 things,

  1. How long would a Vero’s internal storage last?
  2. if I could run SickGear and Couchpotato on a PC (one that is always on anyway) with uTorrent and then stream my videos (including 1080p) to my Pi.someway, I have no idea if that’s even possible though.

Think I’d still be able to retrieve my databases from it though?

I figured out how to set up everything in windows so I can just run a normal SD setup of OSMC and add network dirs for my videos. That should work according to what I’ve seen on youtube and stuff and should at least get me up and running again but the question now is, could I still retrieve the data from the damaged USB (it’s literally 2 files lol) so I can dump them on my windows setup or do I have to start alllllll over again :P. Which I really hope is not the case.

I checked the warrenty, if I’m able to scrub the data so it’s not absolutely obvious I was running an OS from it I’ll just get a replacement for it :smiley:

Still trying to get this to work, no luck yet.

It gets mounted but can’t access it.
If I try fsck.ext4 /dev/sda2 it tells me it can’t because it’s mounted so I umount it and run the same and get a fsck.ext4 -f /dev/sda2 e2fsck 1.42.5 (29-Jul-2012) fsck.ext4: No such device or address while trying to open /dev/sda2 Possibly non-existent or swap device?

I reaaaallly want to save those databases, so if I could just reach them for a sec…it would save me so much work (and trust me, it’s less work dabbling trying to get it to work all day then it would be setting the entire thing up from scratch again).