Seite 1 von 2 12 LetzteLetzte
Ergebnis 1 bis 10 von 13

Thema: Medion P89625 1 TB "Volumen" wird nicht mehr erkannt

  1. #1
    Cadet
    Registriert seit
    01.05.2016
    Beiträge
    9
    Mein NAS
    Medion P89625 (MD 86517)

    Standard Medion P89625 1 TB "Volumen" wird nicht mehr erkannt

    Hallo,

    ich hatte kürzlich Probleme, mich mit meiner Medion Life P89625 1TB NAS zu verbinden; nach Reboot wurde auch mal ein Hardware-Fehler angezeigt (rote LED). Nach dem großen Reset (10 sek. auf reset-Knopf) konnte ich die NAS wieder sehen und darauf zugreifen, aber das "interne Volumen" hat den Status "Gegenwärtig sind keine Volumen vorhanden". Der Speicherstatus macht mir mehr Hoffnung: er lautet "41% verwendet"

    Im Protokoll habe ich die Fehlermeldung "Cannot init applets:[Erno2] No such file or directory:´/i-data/md0/.system´"

    Firmware ist 1.01(UZD.2); ich kann mit dem Link "nas-server/r36258,/adv,/cgi-bin/remote_help-cgi?type=backdoor" die telnet-backdoor aktivieren* und als "admin" in das Verzeichnis sehen (aber nicht nach /i-data/md0 wechseln) und bekomme diese Antworten auf...
    cat /proc/partitions
    major minor #blocks name
    7 0 90112 loop0
    31 0 131072 mtdblock0
    31 1 256 mtdblock1
    31 2 3584 mtdblock2
    31 3 512 mtdblock3
    31 4 10240 mtdblock4
    31 5 10240 mtdblock5
    31 6 10240 mtdblock6
    31 7 96000 mtdblock7
    8 0 976762584 sda
    8 1 514048 sda1
    8 2 976245952 sda2


    cat /proc/mounts
    rootfs / rootfs rw 0 0
    /proc /proc proc rw,relatime 0 0
    /sys /sys sysfs rw,relatime 0 0
    none /proc/bus/usb usbfs rw,relatime 0 0
    devpts /dev/pts devpts rw,relatime,uid=0,gid=5,mode=620 0 0
    /dev/mtdblock7 /zyxel/mnt/sysdisk yaffs2 ro,relatime 0 0
    /dev/mtdblock6 /zyxel/mnt/info yaffs2 ro,relatime 0 0
    /dev/loop0 /ram_bin ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /usr ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/security ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/modules ext2 ro,relatime,errors=continue 0 0
    /dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/var tmpfs rw,relatime,size=5120k 0 0
    /dev/mtdblock5 /etc/zyxel yaffs2 rw,relatime 0 0
    /dev/mtdblock5 /usr/local/apache/web_framework/data/config yaffs2 rw,relatime 0 0

    (das sagt mir NIX, aber danach wurde von Mijzelf in einem anderen Post gefragt, der dasselbe Problem beschrieb, aber leider versandet ist...)

    Kennt jemand dieses Problem? Gibts evtl. eine Lösung dafür, oder wie könnte ich es anstellen, an meine Daten zu kommen - hauptsächlich Musik...

    Danke fürs Lesen und Grüße,
    Pixi

    ~~~
    telnet-Verbindung for Dummies:
    - ggf. Telnet-Client unter Windows erst aktivieren, wie z.B. hier beschrieben
    - im Browser die NAS-Verwaltungsseite aufrufen und den admin anmelden
    - dann den Link "nas-server/r36258,/adv,/cgi-bin/remote_help-cgi?type=backdoor" aufrufen, der den Telnet-Port der NAS aktiviert; es wird im Erfolgsfall eine weiße Seite angezeigt, wie von Mijzelf hier beschrieben
    - Kommandozeile (cmd.exe) aufrufen, Kommando "telnet nas-server" absetzen (oder statt dem Alias "nas-server" die IP-Adresse der NAS)
    - wenn die Verbindung klappt, wird nun Name und Passwort abgefragt, mit dem man sich auch auf der NAS-Browserseite angemeldet hat
    - wenn die Anmeldung klappt, ist man im System der NAS und muss Linux sprechen, z.b. die o.g. Status abfragen oder das Passwort vom Root-Account generieren, wie in den folgenden Posts bzw. von Mijzelf beschrieben
    Geändert von pixi (11.08.2016 um 22:21 Uhr) Grund: Telnet Beschreibung

  2. #2

    Standard

    Zitat Zitat von pixi Beitrag anzeigen
    8 0 976762584 sda
    8 1 514048 sda1
    8 2 976245952 sda2
    The disk is recognized, and the partition table is read. But according to /proc/mounts the partitions are not mounted. You can try to mount them manually, to see which errors it gives. For the 1st partition:
    Code:
    # Create mountpoint 
    mkdir /mnt/sda1
    # mount it
    mount /dev/sda1 /mnt/sda1

  3. #3
    Cadet
    Registriert seit
    01.05.2016
    Beiträge
    9
    Mein NAS
    Medion P89625 (MD 86517)

    Standard

    Hi Mijzelf,
    I was quite looking forward for an answer of you, thanks a lot for taking the time!
    I'm late today, but I was able to find out a bit more. I'll post all I did, hoping it might be useful for other forum users enduring similar problems.
    And I'll switch to english, too, although posting to the german forum, but seeing you prefer this language I think it's at least polite.

    First I used telnet again to log the predefined "admin"-account in again. I'm able to connect with my own altered admin-passwd, so that I don't need to reset the password to default again to do so.
    I tried to create the /mnt/sda1 directory and failed as follows (predictably, mabe, but nevertheless):

    / $ mkdir /mnt/sda1
    mkdir: can't create directory '/mnt/sda1': Permission denied


    I now tried to connect as account NsaRescueAngel (what a name) I've read about in the backdoor-description you recently posted elsewhere -- and was successful though on firmware 1.01(UZD.2), using the logged in "admin" to create the angel's passwd by entering /sbin/makekey before.
    This is what the angel was capable of:

    BusyBox v1.17.2 (2012-07-13 19:54:28 CST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.
    / # whoami
    root
    / #
    / # mkdir /mnt/sda1
    / # cd /mnt
    /mnt # ls -lr
    drwxrwxrwx 2 root root 0 May 2 15:54 sda1
    drwxrwxrwx 2 root root 0 Jul 13 2012 ram2
    drwxrwxrwx 2 root root 0 Jul 13 2012 ram1
    drwxrwxrwx 5 root root 0 May 2 15:41 mediaShares
    /mnt # mount /dev/sda1 /mnt/sda1
    mount: mounting /dev/sda1 on /mnt/sda1 failed: No such device or address


    So, maybe a hero of the copy-and-paste, I'm stuck again -- because indeed /dev/sda1 exists (although even the angel can't cd to it):

    /dev # ls -lrt sda1
    brw-rw---- 1 root root 8, 1 Jul 13 2012 sda1

    I don't really have a clue about unix-derivated file systems. Never saw a "b" leading the permission-string (what doesn't mean anything) -- b for broken?? Gulp.
    Maybe you are in the mood to advice again? Would be very appreciated.
    Many thanks in advance. Will presumeably again not be able to respond during daylight, though.
    Pixi

  4. #4

    Standard

    Zitat Zitat von pixi Beitrag anzeigen
    And I'll switch to english, too, although posting to the german forum, but seeing you prefer this language I think it's at least polite.
    You are right, it's a German forum. Alas I can't write German, although I can read it fairly well.
    Code:
    /mnt # mount /dev/sda1 /mnt/sda1
    mount: mounting /dev/sda1 on /mnt/sda1 failed: No such device or address
    Strange. Is the sda1 partition still listed in /proc/partitions?
    indeed /dev/sda1 exists (although even the angel can't cd to it)
    /dev/sda1 is not a disk or something, it's a device node.
    Code:
    /dev # ls -lrt sda1
    brw-rw----    1 root     root        8,   1 Jul 13  2012 sda1
    This shows pretty much all information inside. The 'b' means block device, and the 8, 1 means 'device type' 8,subnumber 1 (counted from zero). Device type 8 is a sata disk, and subnumber 1 is the first partition on the first disk. (subnumber 0 is the first disk itself)

    That file can exist without the partition it is pointing to. But in that case when mount searches for device 8:1, it can't be found. The file /proc/partitions is a peek inside the kernel (all /proc/ files are. It's a virtual filesystem) and tells the current known list of block devices in the kernel (with their major and minor numbers. Helpful if you need to create a device node). If sda existed on boot, but disappeared later, I guess you have a problem with either the disk or the sata port. You can run 'dmesg' to see all kernel messages. Maybe it gives a clear reason for the disappearing partition.

  5. #5
    Cadet
    Registriert seit
    01.05.2016
    Beiträge
    9
    Mein NAS
    Medion P89625 (MD 86517)

    Standard

    Mijzelf, thanks again for sharing your time and even more, your knowledge. I think I even understood some bits of what you told me.

    Zitat Zitat von Mijzelf Beitrag anzeigen
    Strange. Is the sda1 partition still listed in /proc/partitions?
    You were right, the entries were missing all of a sudden. I restarted the box, and they came back for this time -- an I even was able to mount them this time, as you teached me. Indeed, did it for both, sda1 and sda2.

    AND THEN I WAS ABLE TO SEE MY FILES AGAIN.

    Then I restarted again to see whether they would stay with me now AND THEY DID.

    I'm so happy, I can't tell . Thank you over and over again. As soon as I find the +1 button...
    Now this was a shot across the bow to me. I'll have some serious thinking about securing data and will have to spend some money for more reliable technology. And keep the medion thing to play with the NasRescueAngel and learn more about mounts and stuff.

    Btw, I did also run a dmesg afterwards, all the while not being able to set what mesg-level I want to see and thus getting loads of output. It reads quite normal until the end, where it recommends running e2fsck:

    ADDRCONF(NETDEV_UP): egiga0: link is not ready
    EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
    NTFS driver 2.1.29 [Flags: R/O MODULE].
    egiga0: link up, 1000Mbps, full-duplex, using pause, lpa 0xDDE1
    ADDRCONF(NETDEV_CHANGE): egiga0: link becomes ready
    XFS mounting filesystem sda2
    Starting XFS recovery on filesystem: sda2 (logdev: internal)
    Ending XFS recovery on filesystem: sda2 (logdev: internal)
    Adding 524280k swap on /i-data/.system/swap_ul6545p. Priority:-1 extents:1 across:524280k
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110169
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110171
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110171
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110173
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110171
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110173
    EXT2-fs error (device sda1): ext2_lookup: deleted inode referenced: 110173


    But that is more for your entertainment and doesn't need to be commented, I'll try to look it up first. You did enough, you did good, my case is solved.
    Thanks again, Mijzelf.
    Best whishes, Pixi

  6. #6
    Experte
    Registriert seit
    27.03.2008
    Ort
    Cologne / Germany
    Beiträge
    4.919
    Mein NAS
    N2B1 & IB4220 & WNDR3700v2 with OpenWRT

    Standard

    Hallo,

    ext2 wirklich ...

    Bitte mal die Ausgabe von
    Code:
    cat /proc/filesystems
    posten.

    EDIT:
    Vergessen warum ..
    Normalerweise sollte die Kiste ext3 können, ext3 hat ein Journal und kann es teilweise "abrollen". Das verhindert das Problem von Dateisystemfehlern die du jetzt hast und deshalb kann(konnte) das Device nicht gemountet werden.
    Geändert von ElektromAn (03.05.2016 um 22:42 Uhr)
    Some random kernel coder
    Lots of stuff attached to serial console
    https://github.com/ulli-kroll

  7. #7
    Cadet
    Registriert seit
    01.05.2016
    Beiträge
    9
    Mein NAS
    Medion P89625 (MD 86517)

    Standard

    Hi ElektromAn,
    auch erstmal Danke fürs Interesse:

    / # cat /proc/filesystems
    nodev sysfs
    nodev rootfs
    nodev bdev
    nodev proc
    nodev sockfs
    nodev usbfs
    nodev pipefs
    nodev anon_inodefs
    nodev tmpfs
    nodev inotifyfs
    nodev devpts
    reiserfs
    ext3
    ext2
    ext4
    nodev ramfs
    vfat
    msdos
    iso9660
    hfsplus
    nodev nfs
    nodev nfsd
    nodev cifs
    nodev fuse
    fuseblk
    nodev fusectl
    udf
    xfs
    yaffs
    yaffs2
    nodev mqueue
    nodev rpc_pipefs
    ntfs

    Grüße
    Pixi

  8. #8

    Standard

    Starting XFS recovery on filesystem: sda2 (logdev: internal)
    Ending XFS recovery on filesystem: sda2 (logdev: internal)
    This is caused by the stupid firmware. The box has no usable way to power it off. You only have that silly switch which just cuts the power, with all filesystems mounted. That is begging for problems.
    I wrote an applet in my Tweaks package, which supports 'fake powerdown'. It basically will unmount all filesystems, switch off all leds (except the green network led, which isn't software controllable), and then waits forever, until the power is cut.

    I think a filesystem error kept the box from mounting the filesystems. But that won't remove the blockdevice from /proc/partitions. That can only be caused by a hardware error, I think.



  9. #9
    Cadet
    Registriert seit
    01.05.2016
    Beiträge
    9
    Mein NAS
    Medion P89625 (MD 86517)

    Standard

    Blast, I was celebrating too early. I saved as much as I could yesterday, about 40 GB to free space I had left on a HD; I had difficulties, though, lost contact and had to do everything dicussed above again -- but finally, while my copying long done and the NAS running idle for a while, it went astray again and since then I have lost the HD-entries in the partition table which reads now:

    / # cat /proc/partitions
    major minor #blocks name

    7 0 90112 loop0
    31 0 131072 mtdblock0
    31 1 256 mtdblock1
    31 2 3584 mtdblock2
    31 3 512 mtdblock3
    31 4 10240 mtdblock4
    31 5 10240 mtdblock5
    31 6 10240 mtdblock6
    31 7 96000 mtdblock7
    / #

    No self-repairing this time by reset. Am I right assuming that this is just hardening the HD-defect theory and finally the rest of data is lost , or is there some Linux-wizardry again to bring back these entryies?
    Hoping again for anyone out there to help
    Thanks in advance
    Pixi

  10. #10

    Standard

    If the disk isn't recognized at all, you're stuck. Dmesg can tell. Depending on the value of the data you can try professional data recovery. That will cost you at least a few 100's of euro's. But if your data is that valueable, you would have had a backup, wouldn't you?

    If you are lucky, the problem is not the disk, but the NAS itself. (internal power supply for the disk, or the sata interface). In that case you can get out the disk, and connect the disk to any Linux PC, which should be able to mount and read the disk without problems.

Ähnliche Themen

  1. P89626 Medion NAS [P89626] wird nicht mehr erkannt..
    Von 9639 im Forum Medion
    Antworten: 1
    Letzter Beitrag: 17.04.2016, 14:13
  2. Antworten: 4
    Letzter Beitrag: 27.11.2013, 11:52
  3. Medion NAS wird nicht erkannt
    Von 9639 im Forum Netzwerkaufbau
    Antworten: 16
    Letzter Beitrag: 01.08.2013, 10:54
  4. Antworten: 2
    Letzter Beitrag: 13.01.2011, 13:40

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •