nbpanda Posted March 3, 2014 Share #1 Posted March 3, 2014 gnoboot is a great tool,i install and run well.but i find a issue,if i create a storage space, then i delete it ,i find the system will no response,it is a bug ,or i have not install current. Link to comment Share on other sites More sharing options...
nbpanda Posted March 3, 2014 Author Share #2 Posted March 3, 2014 my gnoboot version is alaph10,and test it in VM and my pc. Link to comment Share on other sites More sharing options...
gnoboot Posted March 3, 2014 Share #3 Posted March 3, 2014 Are you sure its alpha10? My guess is your using iSCSI lun, and then you're trying to delete it that makes your system unresponsive, right? Link to comment Share on other sites More sharing options...
nbpanda Posted March 3, 2014 Author Share #4 Posted March 3, 2014 Thank gnoboot,because i use chinese language,i not sure express so clear. i'm not use iscsi lun , i use PVSCSI in VM and use SATA disk in my old lenovo pc (intel chip ,motherboard specific model is not clear). i create the storage space (in console is volume),then delete it ,the system is not response. i power off the system in web console,the system did't power off. I type shutdown -h now in console ,system did't power off yet. I only pull out the power wire ,and restart the system ,then i can delete the volume. bye the way ,in this happen,i type 'lvdisplay' in console,the command has not show,and hang in there. I check the log file ,seem say can't lock the volume. I test alpha8 to alpha 10 , It's same. Thank! Link to comment Share on other sites More sharing options...
gnoboot Posted March 3, 2014 Share #5 Posted March 3, 2014 Thank gnoboot,because i use chinese language,i not sure express so clear. i'm not use iscsi lun , i use PVSCSI in VM and use SATA disk in my old lenovo pc (intel chip ,motherboard specific model is not clear). i create the storage space (in console is volume),then delete it ,the system is not response. i power off the system in web console,the system did't power off. I type shutdown -h now in console ,system did't power off yet. I only pull out the power wire ,and restart the system ,then i can delete the volume. bye the way ,in this happen,i type 'lvdisplay' in console,the command has not show,and hang in there. I check the log file ,seem say can't lock the volume. I test alpha8 to alpha 10 , It's same. Thank! How big is your vmdk? Can you post a screenshot when it happens or dmesg? You won't be able to poweroff the system while its deleting the volume. The same goes for creating a new volume, you can verify it's still working by runnning `cat /proc/mdstat`. To force power/reboot your system use `poweroff -f` or `reboot -f`, but these commands are dangerous. I have had experienced the same behavior as yours because of improper shutdown. Link to comment Share on other sites More sharing options...
nbpanda Posted March 3, 2014 Author Share #6 Posted March 3, 2014 I'm sorry,i'm use alpha9 not alpha10.Now i install a new system,in installaion i'm not create a storage space.After installation,i create a storespace, My VMDK is 20G. First i create a volume (I change the language , storage space is volme in english language) loop: module loaded [ 56.357728] findhostd uses obsolete (PF_INET,SOCK_PACKET) [ 67.479384] netlink: 12 bytes leftover after parsing attributes. [ 76.979285] Can't get Core 2 temperature data [ 107.037849] Can't get Core 2 temperature data [ 137.098065] Can't get Core 2 temperature data [ 167.155063] Can't get Core 2 temperature data [ 171.747188] Can't get Core 2 temperature data [ 197.001030] Can't get Core 2 temperature data [ 202.849454] md: bind [ 202.855885] md/raid1:md2: active with 1 out of 1 mirrors [ 202.855918] md2: detected capacity change from 0 to 16630349824 [ 202.966646] md2: unknown partition table [ 205.596804] EXT4-fs (dm-1): barriers disabled [ 205.598287] EXT4-fs (dm-1): mounted filesystem with writeback data mode. Opts : usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writebac k,oldalloc [ 205.618163] EXT4-fs (dm-1): re-mounted. Opts: usrjquota=aquota.user,grpjquota =aquota.group,jqfmt=vfsv0,synoacl [ 205.917750] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 205.921664] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 227.079423] Can't get Core 2 temperature data [ 232.197403] Can't get Core 2 temperature data [ 257.155839] Can't get Core 2 temperature data [ 262.740661] Can't get Core 2 temperature data [ 287.230375] Can't get Core 2 temperature data [ 317.304495] Can't get Core 2 temperature data [ 323.052839] Can't get Core 2 temperature data [ 347.379530] Can't get Core 2 temperature data DiskStation> cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid1 sdc5[0] 16240576 blocks super 1.2 [1/1] md1 : active raid1 sdc2[0] 2097088 blocks [12/1] [u___________] md0 : active raid1 sdc1[0] 2490176 blocks [12/1] [u___________] unused devices: Thank you! Link to comment Share on other sites More sharing options...
nbpanda Posted March 3, 2014 Author Share #7 Posted March 3, 2014 gnoboot alpha9+4.3 3827 pat in VM Link to comment Share on other sites More sharing options...
gnoboot Posted March 3, 2014 Share #8 Posted March 3, 2014 I haven't fully tested/tried disk group, can you create a normal volume instead? Using the latest version (alpha10) might have the same issue because nothing's change in the kernel except the new drivers which has been compiled outside the kernel tree. Link to comment Share on other sites More sharing options...
nbpanda Posted March 3, 2014 Author Share #9 Posted March 3, 2014 what's means a normal volume,i try may be must create a disk group. Link to comment Share on other sites More sharing options...
nbpanda Posted March 3, 2014 Author Share #10 Posted March 3, 2014 I have create a normal volume , i delete it and it's ok ! I think work on disk group may have some bug. I test in 'XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0)' , delete disk group is ok. Link to comment Share on other sites More sharing options...
gnoboot Posted March 4, 2014 Share #11 Posted March 4, 2014 You're right! This is issue also present in alpha10. EDIT: I think changing max CPU other than 8/4 is the culprit, compiling a new kernel and probably upload alpha10.1 later. PM me your email Link to comment Share on other sites More sharing options...
nbpanda Posted March 4, 2014 Author Share #12 Posted March 4, 2014 Tanks! i have pm you! Link to comment Share on other sites More sharing options...
gnoboot Posted March 5, 2014 Share #13 Posted March 5, 2014 This should be fixed in the next release, removed the offending patch. Link to comment Share on other sites More sharing options...
Recommended Posts