Ärger mit externe Festplatte

[Fly]

Moin,

ich habe mir einen WLAN-Router (ericsson W25) und eine externe Festplatte von Maxtor (OneTouch4) mit 500GB zugelegt. Diese externe Platte habe ich gleich zuerst auf ext3 Formatiert anschließend via USB an W25 angeschlossen und das hat nicht funktioniert, ich konnte nicht darauf zugreifen. Mit ReiserFS Filesystem kommt der W25 nicht zurecht (unsupported Filesystem). Jetzt habe ich mit ext2 Formatiert... und siehe Logfile der W25.



Feb 12 13:16:33 (none) user.info kernel: usb 1-4: new high speed USB device using ehci_hcd and address 88
Feb 12 13:16:33 (none) user.info kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Feb 12 13:16:38 (none) user.notice kernel: Vendor: Maxtor Model: OneTouch Rev: 0125
Feb 12 13:16:38 (none) user.notice kernel: Type: Direct-Access ANSI SCSI revision: 04
Feb 12 13:16:38 (none) user.notice kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
Feb 12 13:16:38 (none) user.err kernel: sda: assuming drive cache: write through
Feb 12 13:16:38 (none) user.notice kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
Feb 12 13:16:38 (none) user.err kernel: sda: assuming drive cache: write through
Feb 12 13:16:39 (none) user.info kernel: sda5 >
Feb 12 13:16:39 (none) user.notice kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Feb 12 13:16:39 (none) user.warn kernel: scsi: On host 0 channel 0 id 0 only 511 (max_scsi_report_luns) of 208539300 luns reported, try increasing max_scsi_report_luns.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3530203530203330 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3437342031353939 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3834382030203438 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x323539203532350a has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x6370753020313230 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3530203530203330 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3437342031353939 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3834382030203438 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x323539203532350a has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x696e747220363931 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3632353636203020 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3630302031332030 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x2030203136393131 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3734203020312030 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x2030203020302030 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x2030203020373138 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x2030203020363732 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3239373335203136 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3732343720373330 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x3738203020302030 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x2030203020302030 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x2030203020302030 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x0a63747874203937 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x343230350a627469 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x6d65203132303238 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x30353238360a7072 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x6f63657373657320 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x31363636390a7072 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x6f63735f72756e6e has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x696e6720360a7072 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x6f63735f626c6f63 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x6b656420300a0000 has a LUN larger than currently supported.
Feb 12 13:16:39 (none) user.warn kernel: scsi: host 0 channel 0 id 0 lun 0x0000000600000010 has a LUN larger than currently supported.
Feb 12 13:16:40 (none) daemon.info handle-storage: Storage device partition /dev/sda5 (label "" and serial "762dd0c2-c9cd-68d4-496a-792508614014") is being added.
Feb 12 13:16:41 (none) daemon.err nmbd[2154]: [2008/02/12 13:16:41, 0] nmbd/nmbd.c:terminate(58)
Feb 12 13:16:41 (none) daemon.err nmbd[2154]: Got SIGTERM: going down...
Feb 12 13:16:44 (none) daemon.info handle-storage: Storage device partition /dev/sda2 (label "unknown volume type" and serial "unknownvolumetype") is being added.
Feb 12 13:16:44 (none) daemon.err handle-storage: Unsupported filesystem unknown volume type.
Feb 12 13:16:44 (none) daemon.err handle-storage: Failed to mount /dev/sda2 on /mnt/unknownvolumetype.
Feb 12 13:16:45 (none) daemon.err nmbd[16762]: [2008/02/12 13:16:45, 0] nmbd/nmbd.c:terminate(58)
Feb 12 13:16:45 (none) daemon.err nmbd[16762]: Got SIGTERM: going down...
Feb 12 13:17:17 (none) daemon.notice wuid_log[2426]: Session ID authentication for user (noesro) failed!
Feb 12 13:17:17 (none) daemon.notice wuid_log[2426]: Session id not found (na)
Feb 12 13:22:32 (none) daemon.err nmbd[16831]: [2008/02/12 13:22:32, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Feb 12 13:22:32 (none) daemon.err nmbd[16831]: *****
Feb 12 13:22:32 (none) daemon.err nmbd[16831]:
Feb 12 13:22:32 (none) daemon.err nmbd[16831]: Samba name server FWT is now a local master browser for workgroup TEST on subnet 192.168.1.1
Feb 12 13:22:32 (none) daemon.err nmbd[16831]:
Feb 12 13:22:32 (none) daemon.err nmbd[16831]: *****
Feb 12 13:26:18 (none) daemon.info wuid_log[2426]: Changing to UID: 1000 GID: 1000
Feb 12 13:26:22 (none) daemon.info wuid_log[2426]: Changing to UID: 0 GID: 0
Feb 12 13:26:26 (none) daemon.info wuid_log[2426]: Changing to UID: 1000 GID: 1000
Feb 12 13:26:27 (none) daemon.err wuid_log[2426]: RESULT: 0


Wollte mich hier erkundigen ob mir hier jemand helfen kann bzw. erkennen kann wo das Problem liegt... Bin mit Latein schon am Ende denn mit 3 verschiedene Filesysteme versucht habe... Habe auch nachgesehen ob es ein Firmwware Update für W25 gibt, leider nicht...

[marce]

Poste mal die Ausgabe von fdisk -l /dev/$usb-platte, wenn Du die Platte an einem normalen PC angeschlossen hast.

[Fly]

Komisch, jetzt fällt es mir auf, dass immer wieder eine doesn't contain a falid partition table zurückkommt.. egal welches Dateisystem ich nehme... warum kann ich dann dieses Dateisystem mounten bzw. schreiben?



root@ubuntu:~# fdisk -l /dev/sda5

Disk /dev/sda5: 500.0 GB, 500096991744 bytes
255 heads, 63 sectors/track, 60799 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda5 doesn't contain a valid partition table
root@ubuntu:~# umount /dev/sda5
root@ubuntu:~# fdisk -l /dev/sda5

Disk /dev/sda5: 500.0 GB, 500096991744 bytes
255 heads, 63 sectors/track, 60799 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda5 doesn't contain a valid partition table
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~# mkfs.ext3 /dev/sda5
mke2fs 1.38 (30-Jun-2005)
warning: 424 blocks unused.

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
61166016 inodes, 122093568 blocks
6104699 blocks (5.00%) reserved for the super user
First data block=0
3726 block groups
32768 blocks per group, 32768 fragments per group
16416 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
root@ubuntu:~# tune2fs -c 0 -L onetouch4 /dev/sda5
tune2fs 1.38 (30-Jun-2005)
Setting maximal mount count to -1
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~# fdisk -l /dev/sda5

Disk /dev/sda5: 500.0 GB, 500096991744 bytes
255 heads, 63 sectors/track, 60799 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda5 doesn't contain a valid partition table
root@ubuntu:~# mount -t ext3 /dev/sda5 /mnt
root@ubuntu:~# cd /mnt/
root@ubuntu:/mnt# ls -l
total 16
drwx------ 2 root root 16384 Feb 12 16:52 lost+found
root@ubuntu:/mnt# mkdir testdir
root@ubuntu:/mnt# touch test.txt
root@ubuntu:/mnt# ls -l
total 20
drwx------ 2 root root 16384 Feb 12 16:52 lost+found
-rw-r--r-- 1 root root 0 Feb 12 16:55 test.txt
drwxr-xr-x 2 root root 4096 Feb 12 16:55 testdir
root@ubuntu:/mnt# cd /;
root@ubuntu:/# umount /dev/sda5
root@ubuntu:/# fdisk -l /dev/sda5

Disk /dev/sda5: 500.0 GB, 500096991744 bytes
255 heads, 63 sectors/track, 60799 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda5 doesn't contain a valid partition table
root@ubuntu:/#


Was mache ich hier falsch?

[marce]

wenn die Platte am PC dran ist ist sollte sie eigentlich nicht sda5, sondern sda sein - poste mal die komplette Ausgabe von fdisk -l

Ansonsten sieht es so aus, wie wenn einfach die Partitionstabelle nicht ok wäre - evtl. also einfach noch mal alle Partitionen auf der Platte löschen und neu einrichten.

[Fly]

Die Partitiontabelle wird schön aufgelistet, lt. LOG vom W25 wird die ext3 Partition als ext2 gemountet...

Na endlich kann ich jetzt die Share mounten, jedoch nicht schreiben aufgrund mangelnder Berechtigung... Leider gibt es auf dem W25 Router keine Konfigurationseinstellungen bzw. Userverwaltung für Samba Shares. Was könnte ich stattdessen machen, dass ich darauf schreiben kann? Habe die Samba Share wie folgend gemountet (User und pwd ist das welches ich für die Webinterface für W25 brauche)



mount -t smbfs -o username=user,password=geheim //192.168.1.1/onetouch4 /mnt


smbclient -L -U user -W TEST 192.168.1.1 gibt folgendes aus:



WARNING: The "printer admin" option is deprecated
Password:
Domain=[TEST] OS=[Unix] Server=[Samba 3.0.23c]

Sharename Type Comment
--------- ---- -------
onetouch4 Disk
IPC$ IPC IPC Service (FWT server (Samba 3.0.23c))
Domain=[TEST] OS=[Unix] Server=[Samba 3.0.23c]

Server Comment
--------- -------
FWT FWT server (Samba 3.0.23c)
WINSERVER

Workgroup Master
--------- -------
TEST FWT
TESTDOMAIN.AX HOMESERVER


FWT=192.168.1.1

[basti1985]

probier doch mal die platte an den rechner an zu schließen und die berechtigung zu ändern (als root)


chmod
bzw.
chown

auf die werte mit denen du dich anmeldest (d.h. dessen benutzernamen)

p.s. wie hast du das mit der "valid partition table" hinbekommen ?? - hab das selbe problem bei meinem raid

[Fly]

Das ist mir schon klar, dass man mit chmod die Berechtigung ändern kann, aber es ist doch irgendwie blöd, dass man dort keine Berechtigungen bzw. User verwalten kann...

Das mit der "valid partition table" dürfte aufgetreten sein, als ich einfach das USB Kabel vom W25 ausgesteckt habe...