Triglia118
-
Posts
12 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Triglia118
-
-
RobJ, thank you for your deep analysis of my log. I'll try to answer to your questions...
...
Those lines by the way are REALLY old, were in syslogs from the very first unRAID versions I ever saw, so could probably use some cleanup, to avoid this confusion. Your flash drive was fine, no issues that I could see.
What do you mean with "REALLY old"? I took the last available log file and those lines are from the day I upgraded the server.
...
Triglia118, can you recall if the corrections were all at the beginning? You quickly started another parity check, with no corrections showing. It ran less than a minute quicker than the first run, so there could not have been too many corrections in the first run.
Sorry I cannot remember the exact number of corrections. There were many of them, not only at the beginning of the process. Is there any other log file that records these events?
...
The one thing that is a possible concern is that you are running the S3 sleep plugin. Is there any chance it kicked in during this session?
No this is not the case, while the process was running I was at work, supervising the process now and then. I was able to access every time so I don't think the server went to sleep.
There is also another thing about S3 sleep: I had some problems, described here:
http://lime-technology.com/forum/index.php?topic=36543.msg411213#msg411213 http://lime-technology.com/forum/index.php?topic=36543.msg413486#msg413486
Don't know if this is relevant.
...
A side note, you are running the Mover every hour on the hour, which is a little unusual, but fine if that's the way you want it.
My server is not usually ON, I switch it ON when I need it and leave it ON for the time needed. This is why I run the Mover every hour: to avoid to switch it off before the Mover has done its job. A frequent call avoid this problem
-
Perhaps a "sleep XX" (XX is number of seconds to wait) command in the post wake-up box may help ?
Thank you for your suggestion. I found out that I had problems with my USB boot stick. After replacement and licence migration all is OK. I still have a minor issue after wake up: the server monitor console doesn't work any more (switched off), but everything else works correctly. I don't know why, but I hardly ever use the console, so this isn't a real problem.
-
Dear friends, thank you for your help. After USB stick replacement and licence migration, all is OK. So I think that all issues I experienced during server hardware upgrade, were due to reading problems of USB boot stick. I didn't understand why this would affect parity errors, but anyway I could live with this mystery.
-
First of all thank you for your help and for patience reading my poor English. I followed your suggestion and performed another parity check: success, no error. During the previous parity check a got a lot of corrections on parity disk, but no errors in error column at all.
This morning I downloaded the syslog, and found out some strange things. It seems that I have some problems reading the usb flash stick some lines like:
Sep 25 09:53:13 Unraid101 kernel: read_file: error 2 opening /boot/config/super.dat Sep 25 09:53:13 Unraid101 kernel: md: could not read superblock from /boot/config/super.dat Sep 25 09:53:13 Unraid101 kernel: md: initializing superblock
and
Sep 25 09:53:23 Unraid101 emhttp: Start OK! Sep 25 09:53:24 Unraid101 emhttp: unclean shutdown detected Sep 25 09:53:24 Unraid101 kernel: mdcmd (46): check CORRECT Sep 25 09:53:24 Unraid101 kernel: md: recovery thread woken up ... Sep 25 09:53:24 Unraid101 kernel: md: recovery thread checking parity... Sep 25 09:53:25 Unraid101 kernel: md: using 1536k window, over a total of 976762552 blocks. Sep 25 09:53:25 Unraid101 kernel: md: correcting parity, sector=21048 Sep 25 09:53:25 Unraid101 kernel: md: correcting parity, sector=21056 Sep 25 09:53:25 Unraid101 kernel: md: correcting parity, sector=21064 Sep 25 09:53:25 Unraid101 kernel: md: correcting parity, sector=21072
anyway I attach the complete syslog, if you have some spare time, you could suggest me what to check, to avoid future problems.
Thank you
-
I'm sure that I assigned the parity disk in the correct slot. And I did check "parity already valid". The odd thing is that during parity check a lot of errors have been found. I didn't expect that. Before swapping the two data disks I did a previous parity check without any errors. Anyway, no data loss and a new created parity disk... I just didn't understand why...
-
@ garycase
Thank you, all done. Unraid server up and running, all data preserved. Just a question, now Unraid is doing the new parity check, and it is correcting all the parity disk (parity disk correctly assigned as before), as it was all wrong.... but before proceeding I checked the parity and it was Ok. So: why now it seems that is all wrong? is this normal? I've just switched the slot position of 2 data drives, so I was expecting that the parity would be OK...
Just to know: all disks are green, no errors, just rebuilding parity disk
-
Maybe I could take the second option... is it safe? I don't want to lose data. Could you suggest me the right procedure or point me where I can read the procedure? Thank you.
-
Sure, here you are:
http://lime-technology.com/wiki/index.php/FAQ#What_is_the_safe_way_to_rearrange_disk_numbers.2C_assignments.2C_slots.2C_etc.3F
I know that these instructions are for ver. 5.x, but I wasn't able to find anything else for the 6.x release.
-
Dear friends, I set up the S3 sleep plugin, My Unraid server goes gracefully to sleep and wake up with the magic packet.... but after the wake up it seems that Unraid cannot read the usb flash stick correctly: the log reports some errors, reading blocks from the usb stick. This happens only after S3 sleep, so the usb stick is OK. I think this is due to a delay in the USB power up. Any suggestion to solve this problem? With this issue I cannot use S3 sleep because, after the reading failure, I cannot use some functions (like Unmenu and others) and Unraid starts a parity check....
-
Dear friends, I recently upgraded to Unraid 6.1.3: everything is OK. After some testing I decided to improve my server, adding some disks and installing Serviio plugin. Everything work as expected, but every time I boot up the Unraid server, I receive this error message on the console:
Unraid101 login: /usr/local/emhttp/plugins/Serviio/scripts/rc.Serviio: line 670: [: missing ']'
there is just this error, but Serviio works well!
Any ideas?
@PhAze: thank you for your work, and greetings from Italy
-
Dear friends, I recently upgraded to Unraid 6.1.3: everything is OK. After some testing I decided to improve my server, adding some disks and setting them up better. All done, all OK.
Yesterday I decided to swap DISK 5 slot and DISK 6 slot, to mirror the hardware real position in the server. I followed the instructions, found somewhere in the documentation:
1) Stop the server: OK
2) Unassign DISK 5 and DISK 6: ERROR disks missing, as expected
3) Swap assign disk 5 in disk 6 slot and the other way round: ERROR, different assignment then before, as expected
4) Start the server: OK all slots with green light .... BUT
disk 5 and disk 6 unmountable (or something like that) and the server requested to format them ?!!!!
What? they are full of data!
Of course I reverted everything as it was before, and all was Ok again. What I did wrong?
Thank you for your help and sorry for my poor English.
USB document scanner
in Docker Engine
Posted
Dear friends, I'd like to connect an USB scanner to my Unraid server to use it in my home network. I'm just a user so, I'm not able to develop a docker myself. Maybe something that use "SANE - Scanner Access Now Easy". What do you suggest? should I try an Arch Linux KVM with sane or something like that? or maybe there is a ready docker for this use? Thank you for your time.