Is there any way to remove the reference to the seventh drive that it keeps looking for? That expansion failed after only a few seconds so it never did expand to that space.
Beiträge von Luxo
-
-
Bad news indeed. One drive expansion attempt and all is lost.
-
Code
root@openmediavault:~# mount -t ext4 /dev/md127 /media/test mount: wrong fs type, bad option, bad superblock on /dev/md127, missing codepage or helper program, or other error (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) In some cases useful info is found in syslog - try dmesg | tail or so
-
root@openmediavault:~# mkdir -p /media/test
root@openmediavault:~# mount /dev/md127 /media/test
mount: you must specify the filesystem type
root@openmediavault:~# -
Waited a long time after this and it still fails to mount.
Code
Alles anzeigenroot@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdfg] --verbose --force mdadm: looking for devices for /dev/md127 mdadm: /dev/sda is identified as a member of /dev/md127, slot 1. mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 0. mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5. mdadm:/dev/md127 has an active reshape - checking if critical section needs to be restored mdadm: added /dev/sda to /dev/md127 as 1 mdadm: added /dev/sdb to /dev/md127 as 2 mdadm: added /dev/sdc to /dev/md127 as 3 mdadm: added /dev/sdd to /dev/md127 as 4 mdadm: added /dev/sdg to /dev/md127 as 5 mdadm: no uptodate device for slot 6 of /dev/md127 mdadm: added /dev/sdf to /dev/md127 as 0 mdadm: /dev/md127 has been started with 6 drives (out of 7). root@openmediavault:~# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid5 sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1] 9766914560 blocks super 1.2 level 5, 512k chunk, algorithm 2 [7/6] [UUUUUU_] md126 : inactive sdh[6](S) 1953383512 blocks super 1.2 unused devices: <none> root@openmediavault:~# root@openmediavault:~# cat /proc/mdstat -bash: root@openmediavault:~#: command not foundP ersonalities : [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid5 sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1] 9766914560 blocks super 1.2 level 5, 512k chunk, algorithm 2 [7/6] [UUUUUU_] md126 : inactive sdh[6](S) 1953383512 blocks super 1.2 unused devices: <none> root@openmediavault:~# root@openmediavault:~# Personalities : [raid6] [raid5] [raid4] -bash: Personalities: command not found root@openmediavault:~# md127 : active (auto-read-only) raid5 sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1] -bash: syntax error near unexpected token `(' root@openmediavault:~# 9766914560 blocks super 1.2 level 5, 512k chunk, algorithm 2 [7/6] [UUUUUU_] -bash: 9766914560: command not found root@openmediavault:~# root@openmediavault:~# md126 : inactive sdh[6](S) -bash: syntax error near unexpected token `(' root@openmediavault:~# 1953383512 blocks super 1.2 -bash: 1953383512: command not found root@openmediavault:~# root@openmediavault:~# unused devices: <none> -bash: syntax error near unexpected token `newline' root@openmediavault:~# root@openmediavault:~# -bash: root@openmediavault:~#: command not found root@openmediavault:~#
-
Code
Alles anzeigenroot@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdfg] --verbose --force mdadm: looking for devices for /dev/md127 mdadm: /dev/sda is identified as a member of /dev/md127, slot 1. mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 0. mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5. mdadm: Marking array /dev/md127 as 'clean' mdadm:/dev/md127 has an active reshape - checking if critical section needs to be restored mdadm: added /dev/sda to /dev/md127 as 1 mdadm: added /dev/sdb to /dev/md127 as 2 mdadm: added /dev/sdc to /dev/md127 as 3 mdadm: added /dev/sdd to /dev/md127 as 4 mdadm: added /dev/sdg to /dev/md127 as 5 mdadm: no uptodate device for slot 6 of /dev/md127 mdadm: added /dev/sdf to /dev/md127 as 0 mdadm: /dev/md127 has been started with 6 drives (out of 7). root@openmediavault:~#
-
Is the rebuild finished when the RAID shows up in the GUI? After running the CLI commands it finishes by saying that 6 of 7 are completed. Then the RAID is listed in the GUI. It fails when I try to mount it and I have to reboot and start over. Is it possible to make the system forget the failed attempt to add drive 7?
-
Code
root@openmediavault:~# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1] 11720301072 blocks super 1.2 unused devices: <none>
Code
Alles anzeigen# cat /proc/mdstat -bash: root@openmediavault:~#: command not found root@openmediavault:~# Personalities : [raid6] [raid5] [raid4] -bash: Personalities: command not found root@openmediavault:~# md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1] -bash: md127: command not found root@openmediavault:~# 11720301072 blocks super 1.2 -bash: 11720301072: command not found root@openmediavault:~# root@openmediavault:~# unused devices: <none> -bash: syntax error near unexpected token `newline' root@openmediavault:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=61341bc8-96ea-4048-b6b6-cd2e4786133d / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=b8330aef-aede-45bd-b288-7ef0da62d7ce none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 tmpfs /tmp tmpfs defaults 0 0 # >>> [openmediavault] UUID=521c3cfc-210a-4778-bb9f-c2be2ec00356 /media/521c3cfc-210a-4778-bb9f-c2be2ec00356 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 # <<< [openmediavault]
Coderoot@openmediavault:~# blkid /dev/sda: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="81f2c8c2-297e-be 0f-5775-9603ebcb88fa" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdb: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="a94506be-8b62-af 4a-79db-5e8422057948" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdd: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="e7e608d9-2085-5c ac-8f60-8c75a2134be9" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdc: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="03ffbb2d-5203-f3 4c-d217-bf5231ac331e" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sde1: UUID="61341bc8-96ea-4048-b6b6-cd2e4786133d" TYPE="ext4" /dev/sde5: UUID="b8330aef-aede-45bd-b288-7ef0da62d7ce" TYPE="swap" /dev/sdf: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="bc580f54-8994-47 ad-c653-9582a35a3927" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdg: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="18ede836-ad14-2f a1-caf3-e561c5403093" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
-
Pool will not mount. "Communication error" Is it looking for drive 7 that never finished expanding?
-
Best support on the net here!
Code
Alles anzeigenroot@openmediavault:~# mdadm --stop /dev/md127 mdadm: stopped /dev/md127 root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdfg] --verbose --f orce mdadm: looking for devices for /dev/md127 mdadm: /dev/sda is identified as a member of /dev/md127, slot 1. mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 0. mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5. mdadm: Marking array /dev/md127 as 'clean' mdadm:/dev/md127 has an active reshape - checking if critical section needs to be restored mdadm: added /dev/sda to /dev/md127 as 1 mdadm: added /dev/sdb to /dev/md127 as 2 mdadm: added /dev/sdc to /dev/md127 as 3 mdadm: added /dev/sdd to /dev/md127 as 4 mdadm: added /dev/sdg to /dev/md127 as 5 mdadm: no uptodate device for slot 6 of /dev/md127 mdadm: added /dev/sdf to /dev/md127 as 0 mdadm: /dev/md127 has been started with 6 drives (out of 7).
Code
Alles anzeigenroot@openmediavault:~# mdadm --stop /dev/md127 mdadm: stopped /dev/md127 root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdfg] --verbose --f orce mdadm: looking for devices for /dev/md127 mdadm: /dev/sda is identified as a member of /dev/md127, slot 1. mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 0. mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5. mdadm: Marking array /dev/md127 as 'clean' mdadm:/dev/md127 has an active reshape - checking if critical section needs to be restored mdadm: added /dev/sda to /dev/md127 as 1 mdadm: added /dev/sdb to /dev/md127 as 2 mdadm: added /dev/sdc to /dev/md127 as 3 mdadm: added /dev/sdd to /dev/md127 as 4 mdadm: added /dev/sdg to /dev/md127 as 5 mdadm: no uptodate device for slot 6 of /dev/md127 mdadm: added /dev/sdf to /dev/md127 as 0 mdadm: /dev/md127 has been started with 6 drives (out of 7). root@openmediavault:~# root@openmediavault:~# mdadm --stop /dev/md127 -bash: root@openmediavault:~#: command not found mdadm: stopped /dev/md127 root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdfg] --verbose --f orce mdadm: looking for devices for /dev/md127 mdadm: /dev/sda is identified as a member of /dev/md127, slot 1. mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 0. mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5. mdadm: Marking array /dev/md127 as 'clean' mdadm:/dev/md127 has an active reshape - checking if critical section needs to be restored mdadm: added root@openmediavault:~# mdadm: stopped /dev/md127 -bash: mdadm:: command not found root@openmediavault:~# root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sd[abcdfg] --verbose --f orce -bash: root@openmediavault:~#: command not found root@openmediavault:~# mdadm: looking for devices for /dev/md127 -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/sda is identified as a member of /dev/md127, slot 1. -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2. -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3. -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4. -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/sdf is identified as a member of /dev/md127, slot 0. -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5. -bash: mdadm:: command not found root@openmediavault:~# mdadm: Marking array /dev/md127 as 'clean' -bash: mdadm:: command not found root@openmediavault:~# mdadm:/dev/md127 has an active reshape - checking if critical section needs to be restored -bash: mdadm:/dev/md127: No such file or directory root@openmediavault:~# mdadm: added /dev/sda to /dev/md127 as 1 -bash: mdadm:: command not found root@openmediavault:~# mdadm: added /dev/sdb to /dev/md127 as 2 -bash: mdadm:: command not found root@openmediavault:~# mdadm: added /dev/sdc to /dev/md127 as 3 -bash: mdadm:: command not found root@openmediavault:~# mdadm: added /dev/sdd to /dev/md127 as 4 -bash: mdadm:: command not found root@openmediavault:~# mdadm: added /dev/sdg to /dev/md127 as 5 -bash: mdadm:: command not found root@openmediavault:~# mdadm: no uptodate device for slot 6 of /dev/md127 -bash: mdadm:: command not found root@openmediavault:~# mdadm: added /dev/sdf to /dev/md127 as 0 -bash: mdadm:: command not found root@openmediavault:~# mdadm: /dev/md127 has been started with 6 drives (out of 7). -bash: syntax error near unexpected token `('
Since I have removed the seventh drive that I was trying to add and shape what should I do next? Adding that drive caused the entire failure.When should I mount the filesystem? The RAID is currently marked clean, degraded with the missing drive #7.
-
Code
Personalities : [raid6] [raid5] [raid4] md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1] 11720301072 blocks super 1.2 unused devices: <none>
Code/dev/sda: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="81f2c8c2-297e-be0f-5775-9603ebcb88fa" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdb: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="a94506be-8b62-af4a-79db-5e8422057948" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdd: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="e7e608d9-2085-5cac-8f60-8c75a2134be9" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdc: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="03ffbb2d-5203-f34c-d217-bf5231ac331e" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sde1: UUID="61341bc8-96ea-4048-b6b6-cd2e4786133d" TYPE="ext4" /dev/sde5: UUID="b8330aef-aede-45bd-b288-7ef0da62d7ce" TYPE="swap" /dev/sdf: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="bc580f54-8994-47ad-c653-9582a35a3927" LABEL="openmediavault:Pool" TYPE="linux_raid_member" /dev/sdg: UUID="161d27f1-6d6b-5b9b-925d-630ad00256e6" UUID_SUB="18ede836-ad14-2fa1-caf3-e561c5403093" LABEL="openmediavault:Pool" TYPE="linux_raid_member"
Code
Alles anzeigenDisk /dev/sdb: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/sdd doesn't contain a valid partition table Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdc doesn't contain a valid partition table Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/sda doesn't contain a valid partition table Disk /dev/sde: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00020dbd Device Boot Start End Blocks Id System /dev/sde1 * 2048 224860159 112429056 83 Linux /dev/sde2 224862206 234440703 4789249 5 Extended /dev/sde5 224862208 234440703 4789248 82 Linux swap / Solaris Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdf doesn't contain a valid partition table Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdg doesn't contain a valid partition table
-
I added a new drive to my RAID 5. The grow process was successful after 12 hours and then the resize went well.
Next I added another drive to repeat the same process. The drive was recognized and the grow function started but
soon threw a communication error with no details. At this point the system was frozen and non-responsive from CLI or GUI.After a hard boot It tried to recover the journal (I don't know if FSCK was successful) and my RAID has now disappeared.
I have disconnected the new drive that failed to grow and the system will boot but the pool with 6TB of data is missing.
Expert advice is welcomed.
Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdf[0] sdg[5] sdd[4] sdc[3] sdb[2] sda[1]
11720301072 blocks super 1.2unused devices: <none>
-
It can be difficult to get Asset UPnP configured to scan the music folder on the OMV NAS. The instructions given on the Asset forum to set the path have not worked for several people I have seen seeking help, including me.
The path must include the UUID of the shared media folder in OMV.
e.g.
xxx= the UUID you will find in your config.xml by searching for "media" -
Clonezilla was not able to create a bootable SSD from my thumbdrive. So a fresh install and reconfiguration is working great now.
The issue with getting Asset UPnP to scan the music directory has also been solved. For those who are interested in this terrific plugin I have posted the details here Asset UPNP
This has been tricky for myself and others with their music on NAS. -
Understood.
So back to my original question, can a thumbdrive installation be converted to an SSD?
-
Thank you for the quick reply!
How do I import the original config.xml to the fresh install?
I could use some command line assistance in saving the original file which I have on my thumbdrive and writing it to my new install on the SSD.
Actually my new install on the SSD is running well after I manually configured it except for one thing. I am running a plugin, Asset UPnP. I had a great deal of difficulty getting it configured to scan my music folder on the original thumbdrive installation. In the Asset configuration I had to include the drive UUID in the path to the music folder and finally got it to scan. On the new install the same method is not working. I believe the UUID changed in the new install but even that new number is not working to satisfy the path.
If I import my original config.xml will there be a UUID conflict?
I am very close to making this work if I can get the path sorted in Asset UPnP then I am done.
-
I have been using Asset now for a while and it is very good in conjunction with BubbleUPnP.
The Internet radio functionality with the paid version is mostly useless, almost never loads a station. Otherwise it is the best I have tried. Much better than the MiniDNLA plugin currently available for OMV. 12% lower CPU load than MiniDLNA. -
I have been testing OMV on a USB stick with good success managing 14TB. Now I would like to permanently move my OS to an SSD from the thumbdrive.
I have cloned with Clonezilla but the SSD does not finish booting.
There does not seem to be a way of moving my config to a new install. What is the best practice here?
-
Thanks for the help. Got it working. The only problem I had was Chrome won't load the config page. Had to use IExplorer from windows.
Curious how Asset UPNP has worked out for you. Did you test any others?
-