Keine Daten auf dem Transponder

[Ducktrick]

AW: Keine Daten auf dem Transponder

was sagt

mount /dev/sda4 /media/sda4

 

[oldtime]

AW: Keine Daten auf dem Transponder

ArgusVIP:~# mount /dev/sda4 /media/sda4
mount: mounting /dev/sda4 on /media/sda4 failed: Invalid argument
ArgusVIP:~#

 

[Ducktrick]

AW: Keine Daten auf dem Transponder

dann ist die partition bestimmt kaputt. kannst ja mal nach dem mot befeht dmesg machen da steht sicher was am ende

 

[Pilot]

AW: Keine Daten auf dem Transponder

Danke für den Tip Pilot, aber das habe ich schon lange gemacht. Ich habe sogar immer schon einen 2. Stick fertig, falls es mal wieder alles abkackt dann wird der Stick

Handelt es sich dabei um Sticks der gleichen Marke......?

 

[oldtime]

AW: Keine Daten auf dem Transponder

Den mot Befehl kennt der nicht. Meinst du mount? Ich hab jetzt mal mount eingegeben und dann dmesg.

Spoiler

usb-storage: device scan completesd 2:0:0:0: [sdb] Mode Sense: 38 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb:
usb 1-1.4: new full speed USB device using stm-ehci and address 5
sdb1
input: fulan front panel buttons as /devices/virtual/input/input0
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI disk
usb 1-1.4: configuration #1 chosen from 1 choice
aotom_vip1: exports duplicate symbol I2C_bus_add (owned by aotom)
tune2fs: sending ioctl 127c to a partition!
tune2fs: sending ioctl 127c to a partition!
tune2fs: sending ioctl 127c to a partition!
tune2fs: sending ioctl 127c to a partition!
tune2fs: sending ioctl 127c to a partition!
tune2fs: sending ioctl 127c to a partition!
usb 1-1.1: reset high speed USB device using stm-ehci and address 3
umount: sending ioctl 4c01 to a partition!
umount: sending ioctl 4c01 to a partition!
EXT2-fs: sda2: couldn't mount because of unsupported optional features (240).
EXT4-fs (sda2): mounted filesystem with ordered data mode
Slow work thread pool: Starting up
Slow work thread pool: Ready
EXT2-fs: sda4: couldn't mount because of unsupported optional features (240).
EXT4-fs (sda4): bad geometry: block count 7372800 exceeds size of device (3441312 blocks)
EXT2-fs: sdb1: couldn't mount because of unsupported optional features (240).
EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sdb1): mounted filesystem with ordered data mode
stmcore-display: STx7109c3 display: probed
device probe found 2 display pipelines
stmfb: Starting HDMI Output hdmi = 8b8c0000
[DETECT] -> Boxdetect for Argus Boxes
[DETECT] -> Boxtype = Vip2
[DETECT] -> Tuner1 = sharp7306
[DETECT] -> Tuner2 = sharp7306
[AVS]: A/V switch handling for vip2_avs
[AVS]: init success
[AVS]: Set Encoder = (1)ON
snd_pseudo snd_pseudo.0: firmware: requesting downmix.fw
pti: module license 'NO' taints kernel.
Disabling lock debugging due to kernel taint
pti loaded (videoMem = 2048, waitMS = 20, camRouting = 0, enableStatistic = 0)
DVB: registering new adapter (STM Streamer)
Load real TC Code
TC_Data = b9238000, TC_Code = b923c000
Readback TC ... successfull
using videoMem = 385024 (packets = 2048)
pti: pti_buffer_pool_init: allocate 94 pages (385024 bytes)
DMA(0) base = 525b000, top = 52b9000, buffer = 525b000, size 385024
freeBuffer(): free = 1
pti: pti_buffer_pool_init: allocate 94 pages (385024 bytes)
DMA(1) base = 5400000, top = 545e000, buffer = 5400000, size 385024
freeBuffer(): free = 2
pti_task: using 2 dma channel
DVB: registering adapter 0 frontend 0 (Sharp7306 Plug&Play (VIP2) )...
DVB: registering adapter 0 frontend 1 (Sharp7306 Plug&Play (VIP2) )...
Free session: 0
Using session 0
Free session: 1
Using session 1
Free session: 2
Using session 2
input: TDT RC event driver as /devices/virtual/input/input1
lirc_dev: lirc_register_driver: sample_rate: 0
[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
Adding 65528k swap on /dev/sda3. Priority:-1 extents:1 across:65528k
eth0: device MAC address 00:80:e1:12:06:30
STMMAC MII Bus: probed
eth0: PHY ID 0181b8a0 at 2 IRQ 11 (0:02) active
stmmac_timer: (eth0) sh_tmu Timer (freq 256Hz)
No MAC Management Counters available
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbcore: registered new interface driver ftdi_sio
PHY: 0:02 - Link is Up - 100/Full
[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
[AVS]: avs_command_kernel (5)
[AVS]: vip2_avs_command_kernel: SAA command (5)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set mode
[AVS]: vip2_avs_set_mode RGB 1
[AVS]: avs_command_kernel (11)
[AVS]: vip2_avs_command_kernel: SAA command (11)
[AVS]: vip2_avs_command_kernel SAAIOSMODE src sel
[AVS]: Not Supported (vip2_avs_src_sel)
[AVS]: avs_command_kernel (4103)
[AVS]: vip2_avs_command_kernel: AVSIOSET command
[AVS]: vip2_avs_command_kernel AVSIOSVOL set volume
[AVS]: vip2_avs_set_volume (0)
[AVS]: vip2_avs_set_volume: c = (62)
stmhdmiio_set_audio_source - 8b8c0000
stmfb: Starting HDMI Output hdmi = 8b8c0000
stmfb: Starting HDMI Output hdmi = 8b8c0000
[AVS]: avs_command_kernel (4104)
[AVS]: vip2_avs_command_kernel: AVSIOSET command
[AVS]: vip2_avs_command_kernel AVSIOSVOL set mute
[AVS]: type Mute 0 (SCART_AUDHI=0 Kackt beim Zappen)
[AVS]: vip2_avs_set_mute: t_mute = (0)
[AVS]: Hier Knackt es wenn SCART_AUDHI auf 0 gestellt wird für lauteren Sound...pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 1f360, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 2, 35
pti_hal_set_source(): 2, 35
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 193e8, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)(da 0, 3)(da 0, 3)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 12a28, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)(da 0, 3)(da 0, 3)pti_buffer_free(8b94c168, 385024) - delta 0x 3025c, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 574c8, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 8954, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)(da 0, 3)(da 0, 3)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 44348, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)(da 0, 3)(da 0, 3)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 221a4, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 51550, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x d380, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 2, 35
[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_hal_set_source(): 0, 32
getBuffer(): free = 2
pti_buffer_get(385024) => 8b94c168
(da 0, 1)(da 0, 2)[AVS]: avs_command_kernel (10)
[AVS]: vip2_avs_command_kernel: SAA command (10)
[AVS]: vip2_avs_command_kernel SAAIOSMODE set wss
[AVS]: vip2_avs_set_wss
[AVS]: avs_set_wss SAA_WSS_169F = (1)
pti_buffer_free(8b94c168, 385024) - delta 0x 527ac, thr 0x1
freeBuffer(): free = 2
pti_hal_set_source(): 2, 35
ArgusVIP:~#

Das sind zwei völlig unterschiedliche Sticks, andere Marke, andere größe.

 

[Ducktrick]

AW: Keine Daten auf dem Transponder

ich meinte natürlich mount -a und dann dmesg, schätze mal die partition mit ext4 kann einfach nicht mehr gelesen werden

EDIT

Da stehts doch bereits

EXT4-fs (sda4): bad geometry: block count 7372800 exceeds size of device (3441312 blocks)
EXT2-fs: sdb1: couldn't mount because of unsupported optional features (240).
EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sdb1): mounted filesystem with ordered data mode

ganz klar partition kaputt

EXT4-fs (sda4): bad geometry: block count 7372800 exceeds size of device (3441312 blocks)

kannst du aber reparieren mit

fdisk /dev/sda

dann kannst du m für hilfe drücken, dort steht dann buchstabe zum löschen der partition, ( delate patition )z.B. d
danach fragt er welche der 4 du löschen willst, da drückst du eben 4, anschliessend wieder m drücken und buchstabe für partition erstellen, dann fragt er primar oder secon.... da wählst du primär und danach alles anndere mit enter duchgehen, jetzt wählst du den buchstaben für write and exit ( ebenfalls mit m schauen welcher das ist)
jetzt nur noch formatieren und mounten mit

mkfs.ext4 /dev/sda4
mount -a

edit edit

so schaut das aus

ArgusVIP:~# fdisk /dev/sda

Command (m for help): m
Command Action
a       toggle a bootable flag
b       edit bsd disklabel
c       toggle the dos compatibility flag
d       delete a partition
l       list known partition types
n       add a new partition
o       create a new empty DOS partition table
p       print the partition table
q       quit without saving changes
s       create a new empty Sun disklabel
t       change a partition's system id
u       change display/entry units
v       verify the partition table
w       write table to disk and exit

Command (m for help):

also wäre es d,4,n,(1 für Proimare),enter, enter, w

 

[oldtime]

AW: Keine Daten auf dem Transponder

ArgusVIP:~# fdisk /dev/sda


The number of cylinders for this disk is set to 14786.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)


Command (m for help): m
Command Action
a       toggle a bootable flag
b       edit bsd disklabel
c       toggle the dos compatibility flag
d       delete a partition
l       list known partition types
n       add a new partition
o       create a new empty DOS partition table
p       print the partition table
q       quit without saving changes
s       create a new empty Sun disklabel
t       change a partition's system id
u       change display/entry units
v       verify the partition table
w       write table to disk and exit


Command (m for help): d
Partition number (1-4): 4


Command (m for help): fdisk /dev/sda
f: unknown command
Command Action
a       toggle a bootable flag
b       edit bsd disklabel
c       toggle the dos compatibility flag
d       delete a partition
l       list known partition types
n       add a new partition
o       create a new empty DOS partition table
p       print the partition table
q       quit without saving changes
s       create a new empty Sun disklabel
t       change a partition's system id
u       change display/entry units
v       verify the partition table
w       write table to disk and exit


Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Selected partition 4
First cylinder (1345-14786, default 1345): Using default value 1345
Last cylinder or +size or +sizeM or +sizeK (1345-14786, default 14786): Using default value 14786


Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
ArgusVIP:~#

Das Laufwerk ist in Benutzung. Daher geht das nicht. Aber brauch ich diese Partition eigentlich? Ich habe eine Festplatte mit angeschlossen und habe nicht vor irgendwas auf dem Stick aufzunehmen. Kann das schaden wenn die Partition defekt ist?

 

[Ducktrick]

AW: Keine Daten auf dem Transponder

die kann nicht benutzt sein wenn sie nicht gemountet ist... demnach ist da was ganz anderes an dem stick faul, es geht nicht darum ob du sie brauchst oder nicht, es geht darum das wenn da schon nur read möglich ist aber write nicht dann stimmt was generell nicht. ist eine Partition nicht gemountet muss sie änder bar sein

 

[oldtime]

AW: Keine Daten auf dem Transponder

Ok. Hab ich denn jetzt was falsch gemacht oder ist jetzt was mit dem Stick nicht OK. Ich hatte das ich nur lesen konnte ja auch mal auf sda1. Als ich einen anderen Kernel testen sollte. Das war nach einem Neustart wieder weg glaub ich.

 

[Ducktrick]

AW: Keine Daten auf dem Transponder

am besten mal nen lowlevel format vom stick udn dann backup drauf packen. irgend was stimmt da mal garnicht