Hy ryecoaaron, I had understood that the 2.X version was already released...I wait updates.
Thanks for your clarification.
Posts by daniele82
-
-
Hi at all,
I tried all you suggest but I continue to have problems to update my system. At the beginning, I had the same error that give the name at the thread. Removing the file /etc/apt/apt.conf I'm able to upgrade the system from the version 1.18 to 1.19. After this, I tried to update the system at the 2.X version without result. I also execute the command omv-mkconf omvextrasorg aptclean, apt-get clean, update, upgrade and dist-upgrade but always with negative result, the system tells me I haven't nothing to update. Any idea?
Thanks in advanced. -
Is as if after the upgrade, many configuration files are missing and saving again, the configuration files are restored or fixed.
-
Ok, now I can see all folders...I don't know whats happen but seem all works fine.
I do others test but for the moment, thanks a lot for your support and patience.
This community is amazing, solve all problems in a very shortly time
-
Guys, has happen something of strange. I have four shared folders. To try the tekkb suggestion, I removed from SMB/CIFS section one folder (where I haven't files) and recreated the sharing option. After, i opened the window manager at my \\ip_of_nas and now I see and I can browse the others three folder, but not the folder where I recreated the setting. Any suggestion?
-
tekkb, yes. I reboot the server many times, I'm trying to solve this specific problem from yesterday, when I finish to resolve the problems encountered after the upgrade.
subzero79, yes we talking about SMB. I execute your command and I receive this output:
Coderoot@openmediavaultNAS:~# ps ax | grep 'nmbd\|smbd' 2566 ? Ss 0:00 /usr/sbin/nmbd -D 2569 ? Ss 0:00 /usr/sbin/smbd -D 2581 ? S 0:00 /usr/sbin/smbd -D 2967 ? S 0:00 /usr/sbin/smbd -D 3165 ? S 0:00 /usr/sbin/smbd -D 4571 pts/0 S+ 0:00 grep nmbd\|smbd -
Nothing to do...I can't mount the shared folders, I also tried using the field "Connect using different credential"...I don't understand whats happen.
Thanks for your support and patience. -
Both, windows and linux machine. I always used without problems the SMB shared folders.
I don't know if can is a problem, but when I upgraded OMV, I forgot to remove the RAID disks but seem haven't reported problems. I have a RAID5. -
subzero79 thanks for your response but I don't understood very well what you told.
Under "service discovery" SMB is active. I tried to re-save the configuration with no result.
Thanks for your support. -
Hi guys,
after update OMV from version 0.5.X to 1.0.X, I had a lot of problem I resolved following the threads are reported in the section Problems while Upgrading in the guide Upgrade from latest OMV 0.5.X to OMV 1.0. Now OMV works perfectly, but when I open with explorer or other file manager the remote server, I don't found anything, my shared folders are not showed. I done a check under OMV, RAID is clear and filesystem is mounted and online. If I browse the system with the command line, I see all my data and the permissions seem to be right. Someone have a idea about what happened?Thanks in advanced.
-
Present, nice to meet you Roberto.
To be correct, I written in english. -
Recovering in progress...many many thanks for all again.
But very early I want to build a new system with most recent components. If you have some good advice, is something pleasing.
See you around the blog . -
I think you are right, is mounted, I have this output:
Code... /dev/md0 on /media/e8cc0bab-................. type ext4 ...Do you think I can use
Codeumount /dev/md0or with the RAID we must to be more carefully?
-
I restarted the system in recovery mode but when I executed the first command I received this error:
Codemd: md0 still in use. mdadm: failed to stop array /dev/md0: Device or resource busy Parhaps a running process, mounted filesystem or active volume groups?I'm searching a way to solve.
-
Ok clear. The output of the command is:
Code
Display Moreroot@openmediavaultNAS:~# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 : active raid5 sdc[1] sdd[3] sdb[4] 468868608 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU] unused devices: <none> root@openmediavaultNAS:~# fdisk -l | grep Disk WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Warning: invalid flag 0x0000 of partition table 5 will be corrected by w(rite) Disk /dev/md0 doesn't contain a valid partition table Disk /dev/sda: 163.9 GB, 163927522816 bytes Disk identifier: 0x00000000 Disk /dev/sdc: 160.0 GB, 160041885696 bytes Disk identifier: 0x000ed6a0 Disk /dev/sde: 10.0 GB, 10005037056 bytes Disk identifier: 0x000b38b4 Disk /dev/sdb: 163.9 GB, 163928604672 bytes Disk identifier: 0x0002e97c Disk /dev/sdd: 163.9 GB, 163927522816 bytes Disk identifier: 0xc8a2cb9c Disk /dev/md0: 480.1 GB, 480121454592 bytes Disk identifier: 0x00000000What means?
-
Thanks, thanks, thanks, you saved my data.
There is only a small problem to solve. The RAID is working only with three driver (sdc,sdb, sdd) and for this RAID is degraded. I tried to add the last driver (sda) but is not displayed in the list when in "RAID Management" I have selected "Recover" option.
In addition to, before the driver with the OS inside was "sda", now this is signed with "sde", can give problem? I ask because in your command I used "sd[abcd]" and I want to be sure the the fourth driver isn't use because I have written something of wrong.Thank you again, I hope to help the community as you.
-
I'll try to do the steps starting the system in recovery mode. I'll know the good tool you reported, but the problem with my system is the MB is too old and doesn't support the boot from USB very well. I execute the commands and I give at you the feedback as soon as possible. Thanks.
-
Hi ryecoaaron,
at the moment the system is normally started and I can start in recovery mode also. Do you think it's better execute the command booting the system from the CD? Because at the moment my system don't have a CD reader but if need, I search one.Thanks a lot for your rapid support.
-
Hi ryecoaaron,
thanks for your reply. I think the response at your question is in the third block of code but I rewrite here to be more comprensible:Coderoot@openmediavaultNAS:~# cat /proc/mdstat Personalities : md0 : inactive sdc[1](S) sdd[3](S) sdb[4](S) sda[0](S) 636544279 blocks super 1.2 unused devices: <none>Thanks for your support.
-
Hi guys,
this morning I'm continue my study to found a solution at my problem and I read others four conversations:Codehttp://ubuntuforums.org/showthread.php?t=1854188 http://www.linuxquestions.org/questions/linux-general-1/raid5-with-mdadm-does-not-ron-or-rebuild-505361/ http://www.linuxquestions.org/questions/linux-general-1/failed-raid5-disk-array-questions-about-mdadm-and-recovery-761209/#post3715706 http://ubuntuforums.org/showthread.php?t=1101748&page=2I have always more confusion in my mind but I think to search a solution, we need to have more information about the status of the system. I report all I done.
Code
Display Moreroot@openmediavaultNAS:~# fdisk -l Disk /dev/sda: 10.0 GB, 10005037056 bytes 255 heads, 63 sectors/track, 1216 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000b38b4 Device Boot Start End Blocks Id System /dev/sda1 * 1 1161 9320448 83 Linux /dev/sda2 1161 1217 447489 5 Extended /dev/sda5 1161 1217 447488 82 Linux swap / Solaris WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 163.9 GB, 163927522816 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 19930 160085471 ee GPT Disk /dev/sdd: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ed6a0 Device Boot Start End Blocks Id System /dev/sdd1 1 19457 156288321 c W95 FAT32 (LBA) Disk /dev/sdc: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0002e97c Device Boot Start End Blocks Id System Warning: invalid flag 0x0000 of partition table 5 will be corrected by w(rite) Disk /dev/sde: 163.9 GB, 163927522816 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xc8a2cb9c Device Boot Start End Blocks Id System /dev/sde1 2 19929 160071660 f W95 Ext'd (LBA)Code
Display Moreroot@openmediavaultNAS:~# cat /proc/mdstat Personalities : md0 : inactive sdd[1](S) sde[3](S) sdc[4](S) sdb[0](S) 636544279 blocks super 1.2 unused devices: <none> root@openmediavaultNAS:~# cat /sys/block/md0/md/array_state inactive root@openmediavaultNAS:~# mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. root@openmediavaultNAS:~# mdadm --examine /dev/md0 mdadm: No md superblock detected on /dev/md0. root@openmediavaultNAS:~# cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays ARRAY /dev/md0 metadata=1.2 spares=1 name=openmediavaultNAS:DatiUtenti UUID=5da4403f:0dbfb47e:2999f06e:e7989f9aI checked all drivers and appears to be all ok:
Code
Display Moreroot@openmediavaultNAS:~# mdadm --examine /dev/sdb /dev/sdb: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 5da4403f:0dbfb47e:2999f06e:e7989f9a Name : openmediavaultNAS:DatiUtenti (local to host openmediavaultNAS) Creation Time : Sat Dec 24 15:56:05 2011 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 320168895 (152.67 GiB 163.93 GB) Array Size : 937737216 (447.15 GiB 480.12 GB) Used Dev Size : 312579072 (149.05 GiB 160.04 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : 00dec8dc:c296646a:91033c30:8d64308b Update Time : Sun Sep 14 22:48:05 2014 Checksum : 9998e53 - correct Events : 3522 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 0 Array State : AAAA ('A' == active, '.' == missing) root@openmediavaultNAS:~# mdadm --examine /dev/sdd /dev/sdd: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 5da4403f:0dbfb47e:2999f06e:e7989f9a Name : openmediavaultNAS:DatiUtenti (local to host openmediavaultNAS) Creation Time : Sat Dec 24 15:56:05 2011 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 312579760 (149.05 GiB 160.04 GB) Array Size : 937737216 (447.15 GiB 480.12 GB) Used Dev Size : 312579072 (149.05 GiB 160.04 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : ec47da01:cdb4e1a5:80bc81d6:04815aea Update Time : Wed Sep 17 22:23:59 2014 Checksum : 6f2a0db6 - correct Events : 3586 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 1 Array State : .A.A ('A' == active, '.' == missing) root@openmediavaultNAS:~# mdadm --examine /dev/sde /dev/sde: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 5da4403f:0dbfb47e:2999f06e:e7989f9a Name : openmediavaultNAS:DatiUtenti (local to host openmediavaultNAS) Creation Time : Sat Dec 24 15:56:05 2011 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 320168895 (152.67 GiB 163.93 GB) Array Size : 937737216 (447.15 GiB 480.12 GB) Used Dev Size : 312579072 (149.05 GiB 160.04 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : dff33caf:69e10cec:4c909bd1:08d57254 Update Time : Wed Sep 17 22:23:59 2014 Checksum : c85ddb26 - correct Events : 3586 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 3 Array State : .A.A ('A' == active, '.' == missing) root@openmediavaultNAS:~# mdadm --examine /dev/sdc /dev/sdc: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 5da4403f:0dbfb47e:2999f06e:e7989f9a Name : openmediavaultNAS:DatiUtenti (local to host openmediavaultNAS) Creation Time : Sat Dec 24 15:56:05 2011 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 320171008 (152.67 GiB 163.93 GB) Array Size : 937737216 (447.15 GiB 480.12 GB) Used Dev Size : 312579072 (149.05 GiB 160.04 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : c74e4972:c20f6c30:82e5fb81:0ff88de5 Update Time : Wed Sep 17 22:19:56 2014 Checksum : 1143e3df - correct Events : 3562 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 2 Array State : .AAA ('A' == active, '.' == missing)and the last one:
Code
Display Moreroot@openmediavaultNAS:~# fsck -fn /dev/md0 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) fsck.ext2: Invalid argument durante l'apertura di /dev/md0 Il superblocco è illeggibile, o non descrive un corretto filesystem ext2 Se il device è valido e contiene realmente un filesystem ext2 (e non swap, ufs o altro), allora il superblocco è corrotto, e si potrebbe provare ad eseguire e2fsck con un superblocco alternativo: e2fsck -b 8193 <device>I don't know why the command spoken of ext2, my partition was ext4.
I am hoping someone with more knowledge than myself can help me because I am sure the data is still there, I need only to rebuild the array.
Have a nice day at all.