Agent-Orange
-
Posts
46 -
Joined
-
Last visited
Posts posted by Agent-Orange
-
-
It was a problem with the CPU, Ubuntu has some problems with Skylake CPU's
I ended up in delete the raid and created a new one.
-
I cant even run an Ubuntu Live Version from an USB stick. I always got a black screen after I made a choice in the GRUB menu. Is that a driver problem?
-
Nope, I didnt tried a Linux Live distribution to read the missing data, thats something I could try
-
is there nothing else I could try? Its not importing data, but it would pisses me off, to download all the Movies/series....
-
Unfortunately my existing Raid 5 crashed caused of that. DSM said one disk wasnt initialized anymore so I repaired it and run a consistency check over night. Now the disk group status is normal, all drives are normal (no smart errors) but the status of the volume on this disk group is "crashed". What can I do, that I dont lose my data? The data on this drive arent that important, that I would save them external, just some movies and series.
The crashed volume is volume2 on vg1 and /dev/md2
Thats what I can say so far:
cat /proc/mdstat:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md3 : active linear sda3[0] sdc3[1]
15618409088 blocks super 1.2 64k rounding [2/2] [uU]
md2 : active raid5 sdl3[0] sdg3[6] sdk3[4] sdj3[3] sdi3[2] sdh3[1]
19510818880 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [uUUUUU]
md4 : active raid1 sdf5[0]
1948683456 blocks super 1.2 [1/1]
md1 : active raid1 sda2[0] sdc2[1] sdf2[2] sdg2[3] sdh2[4] sdi2[5] sdj2[6] sdk2[7] sdl2[8]
2097088 blocks [12/9] [uUUUUUUUU___]
md0 : active raid1 sda1[6] sdc1[8] sdf1[7] sdg1[0] sdh1[3] sdi1[2] sdj1[4] sdk1[5] sdl1[1]
2490176 blocks [12/9] [uUUUUUUUU___]
mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Sun Feb 14 21:29:19 2016
Raid Level : raid5
Array Size : 19510818880 (18606.97 GiB 19979.08 GB)
Used Dev Size : 3902163776 (3721.39 GiB 3995.82 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Sun May 22 22:55:33 2016
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : MatternetNAS1:2
UUID : 62ecb900:75a271c3:e16afda9:7aadf653
Events : 309
Number Major Minor RaidDevice State
0 8 179 0 active sync /dev/sdl3
1 8 115 1 active sync /dev/sdh3
2 8 131 2 active sync /dev/sdi3
3 8 147 3 active sync /dev/sdj3
4 8 163 4 active sync /dev/sdk3
6 8 99 5 active sync /dev/sdg3
lvm vgscan:
Reading all physical volumes. This may take a while...
Found volume group "vg1000" using metadata type lvm2
Found volume group "vg2" using metadata type lvm2
Found volume group "vg1" using metadata type lvm2
Lvdisplay:
--- Logical volume ---
LV Name /dev/vg1/volume_2
VG Name vg1
LV UUID uAJ200-oQvN-3Fo2-heSS-A3lN-mfq5-IjzE2k
LV Write Access read/write
LV Status available
# open 0
LV Size 18.17 TB
Current LE 4763380
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 4096
Block device 253:4
lvm pvscan:
PV /dev/md4 VG vg1000 lvm2 [1.81 TB / 0 free]
PV /dev/md3 VG vg2 lvm2 [14.55 TB / 0 free]
PV /dev/md2 VG vg1 lvm2 [18.17 TB / 0 free]
Total: 3 [2.53 TB] / in use: 3 [2.53 TB] / in no VG: 0 [0 ]
lvm lvscan:
ACTIVE '/dev/vg1000/lv' [1.81 TB] inherit
ACTIVE '/dev/vg2/syno_vg_reserved_area' [12.00 MB] inherit
ACTIVE '/dev/vg2/volume_3' [14.55 TB] inherit
ACTIVE '/dev/vg1/syno_vg_reserved_area' [12.00 MB] inherit
ACTIVE '/dev/vg1/volume_2' [18.17 TB] inherit
mount:
1. mkdir /mnt/syno
2. mount /dev/vg1/volume_2 /mnt/syno
mount: mounting /dev/vg1/volume_2 on /mnt/syno failed: No such device
# e2fsck -vnf /dev/md2
e2fsck 1.42.6 (21-Sep-2012)
Warning! /dev/md2 is in use.
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/md2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
Dsmeg:
2.509976] md: Autodetecting RAID arrays.
[ 2.555128] md: invalid raid superblock magic on sda3
[ 2.555130] md: sda3 does not have a valid v0.90 superblock, not importing!
[ 2.601175] md: invalid raid superblock magic on sdc3
[ 2.601176] md: sdc3 does not have a valid v0.90 superblock, not importing!
[ 2.602861] md: invalid raid superblock magic on sdf5
[ 2.602862] md: sdf5 does not have a valid v0.90 superblock, not importing!
[ 2.660901] md: invalid raid superblock magic on sdg3
[ 2.660902] md: sdg3 does not have a valid v0.90 superblock, not importing!
[ 2.715268] md: invalid raid superblock magic on sdh3
[ 2.715287] md: sdh3 does not have a valid v0.90 superblock, not importing!
[ 2.768305] md: invalid raid superblock magic on sdi3
[ 2.768323] md: sdi3 does not have a valid v0.90 superblock, not importing!
[ 2.840546] md: invalid raid superblock magic on sdj3
[ 2.840547] md: sdj3 does not have a valid v0.90 superblock, not importing!
[ 2.903760] md: invalid raid superblock magic on sdk3
[ 2.903761] md: sdk3 does not have a valid v0.90 superblock, not importing!
[ 2.976482] md: invalid raid superblock magic on sdl3
[ 2.976482] md: sdl3 does not have a valid v0.90 superblock, not importing!
[ 2.976484] md: Scanned 27 and added 18 devices.
[ 2.976485] md: autorun ...
[ 2.976485] md: considering sda1 ...
[ 2.976487] md: adding sda1 ...
[ 2.976488] md: sda2 has different UUID to sda1
[ 2.976490] md: adding sdc1 ...
[ 2.976491] md: sdc2 has different UUID to sda1
[ 2.976492] md: adding sdf1 ...
[ 2.976493] md: sdf2 has different UUID to sda1
[ 2.976495] md: adding sdg1 ...
[ 2.976496] md: sdg2 has different UUID to sda1
[ 2.976497] md: adding sdh1 ...
[ 2.976499] md: sdh2 has different UUID to sda1
[ 2.976500] md: adding sdi1 ...
[ 2.976501] md: sdi2 has different UUID to sda1
[ 2.976502] md: adding sdj1 ...
[ 2.976504] md: sdj2 has different UUID to sda1
[ 2.976505] md: adding sdk1 ...
[ 2.976506] md: sdk2 has different UUID to sda1
[ 2.976507] md: adding sdl1 ...
[ 2.976508] md: sdl2 has different UUID to sda1
[ 2.976517] md: created md0
-
Yeah, it seems that I smashed my existing raid 5. DSM said that 1 Disk failed, in the HDD/SSD overview one of the 6 WD wasn't initialized or something like that. So I had to run a "Consistency check or repair process" on this disk-group, which took about 9hours. Now the disk group status is normal, but the status of the volume is still crashed
When I click on manage, I had the possibility to run a "Data rubbing process" which I started about 3hours ago. When I run cat /proc/mdstat
it seems that this is a resync process, cause it sais "resync = 37.8% (1478646144/3902163776) finish=322.8min speed=125113K/sec"
-
The run with the sas controller, I could create a disk group, that wasnt the problem. The problem is, that DSM doesnt recognises the 2 WD drives anymore, which are on the same SAS-port like the 8TB drives. And the controller bios recognises all drives.
Possible a firmware update would help, but on the Fujitsu page I couldnt find a newer firmware and the firmware on the LSI page arent working with this controller.
At the moment the 8TB drives are connected directly with the motherboard sata ports and DSM recognises all 8 drives now.
-
Hi all
I just wanted to add 2 8TB Seagate drives to create a new Raid0. I already have a Raid5 with 6 4TB WD drives. They are all connected with a Fujitsu CP400i 12GB (SAS3108) SAS controller. After I added the 2 8TB drives the other 2 4TB drives won't be recognised anymore in the DSM storage manager. In the controller Bios I see all drives.
Now I connected the 2 8TB drives directly with the sata-ports on my mainboard, except that my raid5 has been degraded and I have to repair it now.
But I that a problem of the DSM or the raid controller? It sill runs with an IR-Firmware, cause there isnt a IT-Firmware for that controller. But at least I can switch to JBOD mode inside the controller Bios.
Any help would be great, cause I want to run all drives with the sas controller.
EDIT: Unfortunately my existing Raid 5 crashed caused of that. DSM said one disk wasnt initialized anymore so I repaired it and run a consistency check over night. Now the disk group status is normal, all drives are normal (no smart errors) but the status of the volume on this disk group is "crashed". What can I do, that I dont lose my data? The data on this drive arent that important, that I would save them external, just some movies and series.
thanks for any help
-
Cool, cant wait to get my NAS finally working. I hope the updated megaraid drivers works
-
Mit dieser Anleitung hab ich es versucht, aber hat nicht funktioniert. Der Controller wird nur mit der LSI App StorCLI erkannt, mit SAS3FLASH erkennt er den Controller nicht. Der Controller hat auch keinen Jumper zum Überbrücken, nur leere Lötstellen und wenn ich diese überbrücke, blinkt zwar die LED nicht mehr, aber der Controller wird gar nicht mehr erkannt.
Aber anscheinend liegt es am Treiber, welcher nicht ganz ausreicht für meine Karte.
-
Thanks for any help
I found some informations on fujitsu website:
PRAID CP400i (D3307) (PCIe to 8-port SAS-3.0 RAID HBA (LSI 3008)) (driver megaraid_sas) PRAID EP400i (D3216) (PCIe to 8-port SAS-3.0 RAID HBA (LSI 3108)) (driver megaraid_sas) PRAID EP420i (D3216) (PCIe to 8-port SAS-3.0 RAID HBA (LSI 3108)) (driver megaraid_sas) PRAID EP420e (PCIe to 8-port SAS-3.0 RAID HBA (LSI 3108)) (driver megaraid_sas) PSAS CP400e (PCIe to 8-port SAS-3.0 HBA (LSI SAS3008)) (driver mpt3sas)
Your adapter is supported by the megaraid_sas driver.
I think the version included in XPEnoboot is not enought recent to support your card.
I will look to update it.
It has to be a driver problem, cause with a Linux Live Distribution I see the controller and the drives. Would be awesome when you can upgrade the driver
-
I have a Fujitsu PRAID CP400i which actually has a LSI SAS3008 chip on in, but either the mpt3sas or the megaraid_sas are working. Cant see any drives in the storage manager. So I think its a driver problem.
Dirvers can be found here:
http://support.ts.fujitsu.com/Download/ ... =0&NavIDs=
Thanks for any help
-
Es handelt sich um ein Fujitsu CP400i.
Ja, werde das mit der Linux Live Distro mal versuchen.
Es ist schon komisch, wenn ich per UEFI Stick boote um die FW zu flashen, kommt mit SAS2FLASH & SAS3FLASH immer die Meldung, dass kein LSI Controller gefunden wurde. Entweder ist das ein Spezieller Controller oder Fujitsu Flashed diese mit speziellen Firmwares.
Edit: Habe noch etwas im Netz geforscht. Es scheint so, als wäre der PRAID CP400i ein LSI Megaraid 9341-8i. Ich konnte jedenfalls ein neues Firmware vom 9341-8i auf den Controller Flashen. Leider gibt es auf der LSI Homepage aber keine Hinweise bezüglich IT oder IR Firmware zu diesem Controller.
Jedenfalls hätte ich im syslinux folgendes schreiben müssen "insmod=megaraid_sas", was ich jetzt mal getan habe. Und mit dmesg | grep megaraid sehe ich etwas, was vorher nicht da war als das megaraid modul noch nicht in der Syslinux Datei hinterlegt war. Nur wird mir mit dmesg eigentlich 1zu1 der inhalt der Syslinux datei gezeigt und die Festplatten sind immer noch nicht ersichtlich.
-
So habe nun die Zeilen hinter die SN im Syslinux File hinterlegt, aber der Controller wird immer noch nicht erkannt.
Es müsste ja egal sein, welche FW ich installiert habe, er müsste ja trotzdem mit "dmseg | grep LSI" angezeigt werden oder?
-
Hi sfu420
Hast du vielleicht noch die Firmware dazu? Weil jene die ich habe geht anscheinend nicht bzw. ich das Dos-Flashtool meldet immer es hat keinen LSI controller gefunden.
Beim Syslinux.cfg habe ich bereits die Zeilen mit "insmod=mpt3sas" ergänzt, aber habe es im Gegensatz zu dir einfach zuletzt hingeschrieben. Macht das einen Unterschied?
Gruss
-
@sfu420
Thanks for your help.
That means the syslinux.cfg would look like that:
LABEL xpenology
MENU LABEL XPEnology DSM 5.2-5644
KERNEL /zImage
APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 insmod=mpt3sas
Edit: tried it but still dont the see controller or the drives.
-
Hy guys
I have a LSI3008 from Fujitsu (CP400i) and I installed it on my new Xpenology NAS, but the controller wont be recognized by the OS. If installed the driver to the syslinux.cfg file, which was on my USBdrive. I added the lines into the file and copied the driver on the root of the USB drive. Should be correct or?
Is there something other what I have to do?
-
Habe es nun so gemacht, dass ich einfach noch eine alte SSD angeschlossen habe und so DSM installiert. Weil ich konnte mich einfach nicht einloggen, weder mit dem admin noch per Root. Nachher ging es dann ohne Probleme.
Danach habe ich die RC.local datei erzeugt mit dem Befehl aus dem genannten Link. Diese wurde erzeugt aber der Controller bzw. die Festplatten am Controller werden trotzdem nicht erkannt. Habe es dann nach dieser Anleitung probiert- > viewtopic.php?f=2&t=6772 Was aber auch keinen Erfolg gebracht hat.
Wenn ich dmesg | grep LSI eingebe kommen nur zwei Einträge:
Copyright © 1999-2008 LSI Corporation
LSI 3ware SAS/SATA-RAID Controller device driver for Linux v3.26.02.000.
Was mache ich falsch?
-
Hmm, würde jedenfalls das Problem erklären. Nur habe ich ein Problem, ich kann mich nicht einloggen über die Konsole. Obwohl ich mit dem Assistent das PW gesetzt habe, wird es nicht akzeptiert, obwohl der Name des NAS übernommen wurde.
Gibts da ein Root PW oder so?
-
Hallo Zusammen
Ich wollte mir ein neues NAS zusammenstellen basierend auf einem LGA1151 CPU und einem LSI3008 SAS3 Controller von Fujitsu. Bootstick funktioniert, das XPEnology kriegt eine IP und mit dem Assistent finde ich das NAS auch gleich. Nur bekomme ich beim Installieren des DSMs immer die Fehlermeldung 38, was gemäss meinen Recherchen auf eine nicht vorhandene HD deutet. Ich habe momenten 6 Stück 4TB Sata Platte am SAS Controller angeschlossen und die werden im Controller auch angezeigt.
Zu beginn habe ich die Festplatten direkt im Raid Controller als Raid5 konfiguiert und danach als JBOD, aber leider beide Male ohne Erfolg. Jetzt weiss ich nicht, ob es am Boot-Image liegt oder am Controller. Wenn ich das richtig gelesen habe, müsste der Treiber für LSI3008 ja im Image "XPEnoboot_DS3615xs_5.2-5644.4" integriert worden sein.
Muss ich den Controller in den IT-Mode umflashen? Dazu hätte ich sogar eine FW gefunden
Wäre für Tipps sehr dankbar.
Lg
Agent-ORange
DSM not recognises all HDD & volume crashed now
in Archives
Posted
I mean, when I tried to boot with an Ubuntu Live USB Stick (v. 16.04), but it always hang after the GRUB menu. It seems that ubuntu has a problem with skylake CPU's, there are some threads in the net.