Beiträge von Qnappily
-
-
Hallo Zusammen.
Hier bei Interesse noch kurz die Geschichte zu meinem Qnap-Support-Teamviewer-Termin von heute:
Es gab natürlich gemecker über das alter der Anlage etc., aber ansonsten war der Mitarbeiter motiviert und legte wie folgt los:
Vielleicht die gute Nachricht vorweg: Sicherung läuft...
(Besser wohl nicht allein zuhaus nachmachen , aber vielleicht ist der erste Teil, wie man an den md-checker kommt interessant):
Code
Alles anzeigen[~] # wget http://download.qnap.com/Storage/tsd/utility/md_checker --2024-04-09 11:39:15-- http://download.qnap.com/Storage/tsd/utility/md_checker Resolving download.qnap.com (download.qnap.com)... 18.154.63.127, 18.154.63.84, 18.154.63.111, ... Connecting to download.qnap.com (download.qnap.com)|18.154.63.127|:80... connect ed. HTTP request sent, awaiting response... 200 OK Length: 13812 (13K) [binary/octet-stream] Saving to: ‘md_checker.1’ md_checker.1 100%[=====================>] 13.49K --.-KB/s in 0s 2024-04-09 11:39:15 (41.3 MB/s) - ‘md_checker.1’ saved [13812/13812] [~] # ./md_checker Welcome to MD superblock checker (v1.4) - have a nice day~ Scanning system... Legacy Firmware Detected! Scanning disks... RAID metadata found! UUID: 21920cf2:22e16ed4:06b8eed4:757559b9 Level: raid1 Devices: 2 Name: md0 Chunk Size: - md Version: 00.90.00 Creation Time: Nov 16 18:48:35 2009 Status: ONLINE (md0) [UU] =============================================================================== Disk | Device | # | Status | Last Update Time | Events | Array State =============================================================================== 1 /dev/sda3 0 active Apr 9 11:39:24 2024 0.108701 aa 3 /dev/sdc3 1 active Apr 9 11:39:24 2024 0.108701 aa =============================================================================== RAID metadata found! UUID: f78d9418:94e1aaf5:ab3bbe31:ffec1010 Level: raid1 Devices: 2 Name: md1 Chunk Size: - md Version: 00.90.00 Creation Time: Sep 17 21:14:08 2010 Status: ONLINE (md1) [UU] =============================================================================== Disk | Device | # | Status | Last Update Time | Events | Array State =============================================================================== 2 /dev/sdb3 0 active Apr 9 11:39:24 2024 0.3348743 aa 4 /dev/sdd3 1 active Apr 9 11:39:24 2024 0.3348743 aa =============================================================================== [~] # df Filesystem Size Used Available Use% Mounted on /dev/ramdisk 151.1M 127.6M 23.5M 84% / tmpfs 64.0M 472.0k 63.5M 1% /tmp tmpfs 502.8M 24.0k 502.8M 0% /dev/shm tmpfs 16.0M 0 16.0M 0% /share /dev/sda4 371.0M 271.8M 99.2M 73% /mnt/ext /dev/md9 509.5M 134.5M 375.0M 26% /mnt/HDA_ROOT /dev/mapper/md0 3.6T 2.8T 781.5G 79% /share/MD0_DATA tmpfs 1.0M 0 1.0M 0% /mnt/rf/nd [~] # mount -t ext4 /dev/md1 /share/MD MD0_DATA/ MD1_DATA/ [~] # mount -t ext4 /dev/md1 /share/MD MD0_DATA/ MD1_DATA/ [~] # mount -t ext4 /dev/md1 /share/MD MD0_DATA/ MD1_DATA/ [~] # mount -t ext4 /dev/md1 /share/MD1_DATA/ mount: /dev/md1 already mounted or /share/MD1_DATA/ busy [~] # mount /proc on /proc type proc (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) sysfs on /sys type sysfs (rw) tmpfs on /tmp type tmpfs (rw,size=64M) tmpfs on /dev/shm type tmpfs (rw) tmpfs on /share type tmpfs (rw,size=16M) none on /proc/bus/usb type usbfs (rw) /dev/sda4 on /mnt/ext type ext3 (rw) /dev/md9 on /mnt/HDA_ROOT type ext3 (rw,data=ordered) /dev/mapper/md0 on /share/MD0_DATA type ext4 (rw,usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl) tmpfs on /mnt/rf/nd type tmpfs (rw,size=1m) none on /sys/kernel/config type configfs (rw) [~] # mount -t ext4 -o ro,noload /dev/md1 /share/MD1_DATA/ mount: /dev/md1 already mounted or /share/MD1_DATA/ busy [~] # e2fsck -vfp -C 0 /dev/md1 e2fsck: Device or resource busy while trying to open /dev/md1 Filesystem mounted or opened exclusively by another program? [~] # lsof | grep /dev/md1 [~] # ps | grep /dev/md1 27705 admin 532 S grep /dev/md1 [~] # /etc/init.d/services.sh stop Stop qpkg service: No handlers could be found for logger "cc" Stopping... pidfile /tmp/.cloudconnector/CloudBackupSync/backup/QAt.pid does not exist. Not running? No handlers could be found for logger "cc" Stopping... Stopped Stopping... pidfile /tmp/.cloudconnector/CloudBackupSync/sync/QAt.pid does not exist. Not running? Stopping... Stopped Stopping... Stopped Exception KeyError: KeyError(3063522284L,) in <module 'threading' from '/share/MD0_DATA/.qpkg/CloudBackupSync/python/lib/python2.7/threading.pyc'> ignored No handlers could be found for logger "cc" This model is not support HAL. /share/MD0_DATA/.qpkg/HybridBackup/cgi/externalID.cgi shiftup Job400 killall: RTRR: no process killed killall: RTRR_DAEMON: no process killed Starting QSync manitor: OK Shutting down rsync services: rsync. Starting rsync services: rsync. /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:26: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/ganglia/etc/init.d/ganglia-monitor' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:27: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/ganglia/etc/init.d/ganglia-monitor' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:32: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/mockingbird/etc/init.d/hawkeye-agent.sh' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:33: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/mockingbird/etc/init.d/hawkeye-agent.sh' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:39: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/mockingbird/etc/init.d/mockingbird.sh' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:40: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/mockingbird/etc/init.d/mockingbird.sh' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:44: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/mockingbird/etc/init.d/route-monitor.sh' /share/MD0_DATA/.qpkg/Qcenter-Agent/monit/etc/monitrc:45: Warning: Program does not exist: '/mnt/ext/opt/hawkeye/mockingbird/etc/init.d/route-monitor.sh' monitd_agent: Error opening the log file '/mnt/ext/opt/hawkeye/monit/var/log/monit.log' for writing -- No such file or directory killall: monitd_agent: no process killed + exec /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:22: Program does not exist: '/mnt/ext/opt/qnap-cms/ganglia/etc/init.d/ganglia-monitor' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:23: Program does not exist: '/mnt/ext/opt/qnap-cms/ganglia/etc/init.d/ganglia-monitor' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:28: Program does not exist: '/mnt/ext/opt/qnap-cms/qnap-cms/bin/gmetad-python.sh' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:29: Program does not exist: '/mnt/ext/opt/qnap-cms/qnap-cms/bin/gmetad-python.sh' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:35: Program does not exist: '/mnt/ext/opt/qnap-cms/qnap-cms/bin/hawkeyed.sh' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:36: Program does not exist: '/mnt/ext/opt/qnap-cms/qnap-cms/bin/hawkeyed.sh' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:46: Program does not exist: '/mnt/ext/opt/qnap-cms/qnap-cms/bin/mongod.sh' /share/MD0_DATA/.qpkg/Qcenter/monit/etc/monitrc:47: Program does not exist: '/mnt/ext/opt/qnap-cms/qnap-cms/bin/mongod.sh' Error opening the log file '/mnt/ext/opt/qnap-cms/monit/var/log/monit.log' for writing -- No such file or directory killall: monit: no process killed + exec Stopping MongoDB daemon... 2024-04-09T11:42:07.542+0200 2024-04-09T11:42:07.542+0200 warning: 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability. 2024-04-09T11:42:07.542+0200 There doesn't seem to be a server running with dbpath: /share/MD0_DATA/.qpkg/Qcenter/mongo/db Failed stop Removing Python file links... killall: mpd: no process killed BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: mktemp [-dq] TEMPLATE Creates a temporary file with its name based on TEMPLATE. TEMPLATE is any name with six `Xs' (i.e., /tmp/temp.XXXXXX). Options: -d Make a directory instead of a file -q Fail silently if an error occurs
Dann sagte er, es ginge so wohl nicht, auch da der Raid immer busy blieb, was er auch tat.
Also: Runterfahren, Festplatten etwas rausziehen, ohne Platte wieder hochfahren und dann weiter im Text...
Ich hab das Ganze bei Interesse als PDF angehängt (Besser wohl ÜBERHAUPT NICHT allein zuhaus nachmachen... )
Am Ende wollte er fast aufgeben, aber ich wollte mal wieder auf die WEBGui schauen und siehe da, der Raid war lesbar.
Er wußte zwar nicht wie er dass am Ende gemacht hat, aber hey.....
Meine neue externe 8 TB Platte erkennt er am USB Port, initialisiert er aber nicht, der Win/mac/nfs Dienst streikt und meine Netzlaufwerke sind getrennt, aber Filezilla läuft nun und läuft und läuft, aber hey......
Vielen Dank an FSC830 und DR_Mike, tolles Engagement so far, Helden!
Wenn es was über Paypal zu Spenden gibt um das Projekt zu unterstützen, sagt gerne wo.
Erleichterte Grüße
-
Siehe unten, morgen 11.30 Teamviewer mit Qnapsupport, bin gespannt.
Code[~] # e2fsck -f -v -C 0 /dev/md1 e2fsck 1.41.4 (27-Jan-2009) e2fsck: Device or resource busy while trying to open /dev/md1 Filesystem mounted or opened exclusively by another program?
Hier nochmal die ganze Routine:
Code
Alles anzeigen[~] # /etc/init.d/services.sh stop && /etc/init.d/opentftp.sh stop && /etc/init.d/Qthttpd.sh stop Stop qpkg service: killall: monitd_agent: no process killed + exec Stopping mockingbird:. Stopping hawkeye-agent:. Stopping route-monitor:. killall: monit: no process killed + exec killall: python -m hawkeye.api_fallback: no process killed killall: hawkeyed --fallback: no process killed RTNETLINK answers: No such process RTNETLINK answers: No such process Stopping MongoDB daemon... 2024-04-08T10:51:12.365+0200 2024-04-08T10:51:12.365+0200 warning: 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability. 2024-04-08T10:51:12.365+0200 There doesn't seem to be a server running with dbpath: /share/MD0_DATA/.qpkg/Qcenter/mongo/db Failed Python is disabled. killall: mpd: no process killed BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: mktemp [-dq] TEMPLATE Creates a temporary file with its name based on TEMPLATE. TEMPLATE is any name with six `Xs' (i.e., /tmp/temp.XXXXXX). Options: -d Make a directory instead of a file -q Fail silently if an error occurs /etc/rcK.d/QK106SurveillanceStation: line 1676: ${cron_file}: ambiguous redirect sed: Filename required for -i BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: crontab [-c dir] {file|-}|[-u|-l|-e|-d user] file <opts> replace crontab from file - <opts> replace crontab from stdin -u user specify user -l [user] list crontab for user -e [user] edit crontab for user -d [user] delete crontab for user -c dir specify crontab directory BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: rm [OPTION]... FILE... Remove (unlink) the FILE(s). You may use '--' to indicate that all following arguments are non-options. Options: -i always prompt before removing each destination -f remove existing destinations, never prompt -r or -R remove the contents of directories recursively BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: mktemp [-dq] TEMPLATE Creates a temporary file with its name based on TEMPLATE. TEMPLATE is any name with six `Xs' (i.e., /tmp/temp.XXXXXX). Options: -d Make a directory instead of a file -q Fail silently if an error occurs /etc/rcK.d/QK106SurveillanceStation: line 1688: ${cron_file}: ambiguous redirect /etc/rcK.d/QK106SurveillanceStation: line 1689: ${cron_file}: ambiguous redirect BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: crontab [-c dir] {file|-}|[-u|-l|-e|-d user] file <opts> replace crontab from file - <opts> replace crontab from stdin -u user specify user -l [user] list crontab for user -e [user] edit crontab for user -d [user] delete crontab for user -c dir specify crontab directory BusyBox v1.01 (2024.01.30-19:11+0000) multi-call binary Usage: rm [OPTION]... FILE... Remove (unlink) the FILE(s). You may use '--' to indicate that all following arguments are non-options. Options: -i always prompt before removing each destination -f remove existing destinations, never prompt -r or -R remove the contents of directories recursively Usage: /etc/init.d/s3_callback.sh {suspend|resume} . Stop service: vpn_openvpn.sh vpn_pptp.sh ldap_server.sh antivirus.sh iso_mount.sh qbox.sh qsyncman.sh rsyslog.sh snmp lunportman.sh iscsitrgt.sh twonkymedia.sh init_iTune.sh ImRd.sh crond.sh nvrd.sh StartMediaService.sh mariadb.sh btd.sh mysqld.sh recycled.sh Qthttpd.sh atalk.sh nfs ftp.sh smb.sh versiond.sh . [~] # lsof +f -- /dev/md1 lsof: not a file system: /dev/md1 lsof 4.85 latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/ latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man usage: [-?abhKlnNoOPRtUvVX] [+|-c c] [+|-d s] [+D D] [+|-f[gG]] [+|-e s] [-F [f]] [-g [s]] [-i [i]] [+|-L [l]] [+m [m]] [+|-M] [-o [o]] [-p s] [+|-r [t]] [-s [p:s]] [-S [t]] [-T [t]] [-u s] [+|-w] [-x [fl]] [--] [names] Use the ``-h'' option to get more help information. [~] # umount /dev/md0 umount: /dev/md0: not mounted [~] # umount /dev/md1 umount: /dev/md1: not mounted [~] # e2fsck_64 -f -v -C 0 /dev/md1 -sh: e2fsck_64: command not found [~] # e2fsck -f -v -C 0 /dev/md1 e2fsck 1.41.4 (27-Jan-2009) e2fsck: Device or resource busy while trying to open /dev/md1 Filesystem mounted or opened exclusively by another program?
und ein paar weitere Infos:
Code
Alles anzeigencat /etc/config/raidtab raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/sda3 raid-disk 0 device /dev/sdc3 raid-disk 1 raiddev /dev/md1 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/sdb3 raid-disk 0 device /dev/sdd3 raid-disk 1 # cat /etc/config/mdadm.conf Keine Tätigkeit....... cat /etc/storage.conf [VOLUME 1] device name = /dev/md0 raid level = 1 raid disks = 1,3 spare raid disks = status = 0 record_time = Mon Apr 8 10:15:09 2024 filesystem = 104 [VOLUME 2] device name = /dev/md1 raid level = 1 raid disks = 2,4 spare raid disks = status = -3 record_time = Mon Apr 8 10:15:09 2024 filesystem = 104 [Global] Available Disk = 4
-
Danke für die etwas Hoffnung machende Aussage, werde ich machen, sobald der eine Raid gesichert ist...
Hi, habe jetzt den Link von FSC830 probiert:
Code
Alles anzeigen[~] # /etc/init.d/services.sh stop && /etc/init.d/opentftp.sh stop &&/etc/init.d/Qthttpd.sh stop Stop qpkg service: . Stop service: vpn_openvpn.sh vpn_pptp.sh ldap_server.sh antivirus.sh iso_mount.sh qbox.sh qsyncman.sh rsyslog.sh snmp lunportman.sh iscsitrgt.sh twonkymedia.sh init_iTune.sh ImRd.sh crond.sh nvrd.sh StartMediaService.sh mariadb.sh btd.sh mysqld.sh recycled.sh Qthttpd.sh atalk.sh nfs ftp.sh smb.sh versiond.sh . [~] # lsof +f -- /dev/md1 lsof: not a file system: /dev/md1 lsof 4.85 latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/ latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man usage: [-?abhKlnNoOPRtUvVX] [+|-c c] [+|-d s] [+D D] [+|-f[gG]] [+|-e s] [-F [f]] [-g [s]] [-i [i]] [+|-L [l]] [+m [m]] [+|-M] [-o [o]] [-p s] [+|-r [t]] [-s [p:s]] [-S [t]] [-T [t]] [-u s] [+|-w] [-x [fl]] [--] [names] Use the ``-h'' option to get more help information. [~] # umount /dev/md1 umount: /dev/md1: not mounted [~] # e2fsck_64 -f -v -c 0 /dev/md1 -sh: e2fsck_64: command not found [~] # reboot
Leider keine Veränderung ...
-
Hinterher bin ich ja wenigstens immer schlauer geworden und mache den Fehler kein zweites Mal
Werde jetzt auch keinen Raid mehr machen, sondern von einer Platte Software Backup auf die andere, wenn es dann was zu backuppen gibt.
Mache jetzt erstmal ein frisches Backup vom funktionierenden zweiten Raid.
Der Tipp vom Support mit storage_boot_init 2 hat auch nicht geklappt:
Code
Alles anzeigen[~] # storage_boot_init 2 storage_boot_init 2 ... mdadm: device /dev/md1 already active - cannot assemble it mdadm: fail to stop array /dev/md1: Device or resource busy mdadm: device /dev/md1 already active - cannot assemble it mdadm: fail to stop array /dev/md1: Device or resource busy storage_boot_init.c: Stop raid device /dev/md1 succeeded storage_boot_init.c: Start raid device /dev/md1 with checking devices successfully md1 : active raid1 sdb3[0] sdd3[1] md1 : active raid1 sdb3[0] sdd3[1] storage_boot_init.c: /dev/md1 is active. storage_boot_init.c: Check filesystem on /dev/mapper/md1. storage_boot_init.c: Cannot mount /dev/md1. storage_boot_init.c: check_last_degrade_error...
Werde dann dein CLI manuel versuchen.
Dann nochmal Linux um die die Fehler von dort zu melden.
Bei einer alten Raid-Platte von einem Freund hat diskinternals die sofort auslesen können
Bis hierhin erstmal Danke.
Gruss
Hi FSC830.
Aktualisierung: Linux Mint zeigt das Laufwerk, aber wenn ich es öffnen will, ist die Fehlermeldung:
Gruss
...ach und falls Du noch die App hast, die md_checker ermöglicht, wäre ich nochmals dankbar.
-
TS-439
QTS 4.2.6 Build 20240131
2 x RAID1 (Disk 1+3 sowie Disk 2+4)
4x Western Digital 4TB WD40EFR
Hallo in den Club.
Ich bin neu hier, habe folgendes Problem und hoffe auf Hilfe:
Ich habe das Upgrade auf 4.2.6 durchgeführt. Dann lief bis letzten Montag alles ganz normal ohne Fehler und Ausfälle. Nach einem Reboot verweigert der RAID 1 mit den Platten 2+4 den Dienst und ist unmounted / entladen. Die LED über Bay 4 war Rot. Habe eine neue Platte eingelegt, der Raid wurde rebuilded, LED über der Bay grün, Raid aber immer noch unmounted. Status LED blinkt schnell.
Meldung:
CodeWarning 2024/04/04 11:22:12 System 127.0.0.1 localhost [Mirror Disk Volume: Drive 2 4] The file system is not clean. It is suggested that you go to [Storage Manager] to run "Check File System".
Leider ist diese Funktion in der WebGUI gegraut. SMART Festplattencheck ist mehrfach durchgelaufen und fehlerfrei. NAS war auch schon Stunden aus, hilft auch nicht. Also bin ich seit einigen Tagen per Putty im System und studiere Forenbeiträge. Parallel hierzu läuft ein Ticket bei QNAP mit bisher mäßigem Erfolg. Habe deshalb einige Daten zur Analyse zusammengetragen. In den Foren habe ich schon über das Problem gelesen, aber noch keine Lösung die funktioniert hat. Leider nur Massen an Antworten die zum Problem kein Stück weiterhelfen aber den Betroffenen sagen, wie blöd sie doch sind.
Als Idee aus dem Forum habe ich eine Platte ausgebaut um ein Backup zu machen. Leider läßt sich die Platte weder mit Diskinternals noch mit Linux vom Stick mappen. Auch ein Start mit einer entfernten Platte führt nicht zu einer Möglichkeit die verbleibende Platte im Einzelmodus auszulesen. Komme also auch hier nicht richtig weiter. Bin momentan so ziemlich am Ende und hoffe das irgendjemand eine Idee hat, wie ich hier weiterkomme. Und weil immer die Frage kommt warum man kein Backup hat nehme ich die Antwort gleich vorweg. Ich habe ein älteres Backup auf ext. HD. Wollte nach dem FW Update ein neues Backup anlegen, was mir dann aber nicht mehr gelungen ist.
Vielleicht hat ja jemand noch eine Idee, wäre cool. Schonmal Danke vorab.
Code
Alles anzeigenfdisk -l: Disk /dev/sdx: 128 MB, 128057344 bytes 8 heads, 32 sectors/track, 977 cylinders Units = cylinders of 256 * 512 = 131072 bytes Device Boot Start End Blocks Id System /dev/sdx1 1 8 1008 83 Linux /dev/sdx2 9 440 55296 83 Linux /dev/sdx3 441 872 55296 83 Linux /dev/sdx4 873 977 13440 5 Extended /dev/sdx5 873 913 5232 83 Linux /dev/sdx6 914 977 8176 83 Linux You must set cylinders. You can do this from the extra functions menu. Disk /dev/sda: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 267350 2147483647+ ee EFI GPT Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 0, 1) logical=(0, 0, 2) Partition 1 has different physical/logical endings: phys=(1023, 254, 63) logical=(267349, 89, 4) Disk /dev/sda4: 469 MB, 469893120 bytes 2 heads, 4 sectors/track, 114720 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/sda4 doesn't contain a valid partition table You must set cylinders. You can do this from the extra functions menu. Disk /dev/sdb: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 267350 2147483647+ ee EFI GPT Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 0, 1) logical=(0, 0, 2) Partition 1 has different physical/logical endings: phys=(1023, 254, 63) logical=(267349, 89, 4) You must set cylinders. You can do this from the extra functions menu. Disk /dev/sdc: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 1 267350 2147483647+ ee EFI GPT Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 0, 1) logical=(0, 0, 2) Partition 1 has different physical/logical endings: phys=(1023, 254, 63) logical=(267349, 89, 4) You must set cylinders. You can do this from the extra functions menu. Disk /dev/sdd: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 1 267350 2147483647+ ee EFI GPT Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 0, 1) logical=(0, 0, 2) Partition 1 has different physical/logical endings: phys=(1023, 254, 63) logical=(267349, 89, 4) Disk /dev/md9: 542 MB, 542769152 bytes 2 heads, 4 sectors/track, 132512 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md9 doesn't contain a valid partition table Disk /dev/md4: 542 MB, 542851072 bytes 2 heads, 4 sectors/track, 132532 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md4 doesn't contain a valid partition table Disk /dev/md0: 0 MB, 0 bytes 2 heads, 4 sectors/track, 0 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 0 MB, 0 bytes 2 heads, 4 sectors/track, 0 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md1 doesn't contain a valid partition table
Code
Alles anzeigen[~] # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb3[0] sdd3[1] 3905449600 blocks [2/2] [UU] bitmap: 1/233 pages [4KB], 8192KB chunk md0 : active raid1 sda3[0] sdc3[1] 3905449600 blocks [2/2] [UU] bitmap: 0/233 pages [0KB], 8192KB chunk md4 : active raid1 sdd2[4](S) sdc2[3](S) sdb2[2] sda2[0] 530128 blocks super 1.0 [2/2] [UU] md13 : active raid1 sdb4[0] sdd4[3] sdc4[2] sda4[1] 458880 blocks [4/4] [UUUU] bitmap: 0/57 pages [0KB], 4KB chunk md9 : active raid1 sdb1[0] sdd1[3] sdc1[2] sda1[1] 530048 blocks [4/4] [UUUU] bitmap: 0/65 pages [0KB], 4KB chunk unused devices: <none>
Code
Alles anzeigen[~] # cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext2 rw,relatime,errors=continue 0 0 /proc /proc proc rw,relatime 0 0 none /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /tmp tmpfs rw,relatime,size=65536k 0 0 tmpfs /dev/shm tmpfs rw,relatime 0 0 tmpfs /share tmpfs rw,relatime,size=16384k 0 0 none /proc/bus/usb usbfs rw,relatime 0 0 /dev/sda4 /mnt/ext ext3 rw,relatime,errors=continue,barrier=1,data=writeback 0 0 /dev/md9 /mnt/HDA_ROOT ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0 /dev/mapper/md0 /share/MD0_DATA ext4 rw,relatime,noacl,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user 0 0 tmpfs /mnt/rf/nd tmpfs rw,relatime,size=1024k 0 0 none /sys/kernel/config configfs rw,relatime 0 0