Vodka2014
-
Posts
339 -
Joined
-
Last visited
-
Days Won
5
Posts posted by Vodka2014
-
-
Hi @Peter Suh
Please see the attached. I removed the MAC Addresses from the files.
Thanks for the help and I really hope you find what has gone wrong here. Let me know if anything else is needed.
-
7 minutes ago, Peter Suh said:
Is this the correct window status for the M SHELL TCRP loader build?
It is correct to connect to SFTP port 22.
Do you have the settings below?
No logs/jr path?
I am there now what is the password for this please ?
-
1 minute ago, Peter Suh said:
Do you have a total of 4 SAS disks?
Doesn't any of the 4 disks appear in DSM's Storage Manager?I cannot log into DSM at all via the WebUI it keeps on stating it is Busy and try again later. Before i rebooted There was only 1 SAS and 3 SATA the Array was all ok. Data was all there no issues at all.
-
UPDATE NOTES:
I SSH'd Into my NAS and tried to see what is going on and this is what i found. Not sure i am looking in the right spot. Seems after the Reboot i did is when all the issues started as i mentioned. It seems the disks are getting seen but that is about it.
lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdc -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:0/end_device-2:0/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdd -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:1/end_device-2:1/target2:0:1/2:0:1:0/block/sdd
lrwxrwxrwx 1 root root 0 Sep 12 10:30 sde -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:2/end_device-2:2/target2:0:2/2:0:2:0/block/sde
lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdf -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:3/end_device-2:3/target2:0:3/2:0:3:0/block/sdf
lrwxrwxrwx 1 root root 0 Sep 12 10:30 synoboot -> ../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3.1/2-1.3.1:1.0/host1/target1:0:0/1:0:0:0/block/synoboot
systemctl status synostoraged.service
● synostoraged.service - Synology daemon for monitoring space/disk/cache status
Loaded: loaded (/usr/lib/systemd/system/synostoraged.service; static; vendor preset: disabled)
Active: inactive (dead)find . -name proc_name
ps
PID TTY TIME CMD
11791 pts/0 00:00:00 sudo
11792 pts/0 00:00:00 ash
11855 pts/0 00:00:00 ps
df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 2385528 1430224 836520 64% /
devtmpfs 2994244 0 2994244 0% /dev
tmpfs 3048436 4 3048432 1% /dev/shm
tmpfs 3048436 8016 3040420 1% /run
tmpfs 3048436 0 3048436 0% /sys/fs/cgroup
tmpfs 3048436 280 3048156 1% /tmpsystemctl status ● NAS State: degraded Jobs: 0 queued Failed: 2 units Since: Tue 2023-09-12 10:30:47 CAT; 2h 4min ago CGroup: / ├─ 1 /sbin/init ├─5980 ./ttyd login ├─sshd.slice │ └─sshd.service │ ├─10010 sshd: /usr/bin/sshd -D [listener] 0 of 10-100 startup │ ├─12661 sshd: Synology [priv │ ├─12665 sshd: Synology@pts/ │ ├─12666 -sh │ ├─12723 systemctl status │ └─12724 systemctl status ├─system.slice │ ├─avahi.service │ │ └─10849 avahi-daemon: running [NAS.local │ ├─synoneteventd.service │ │ └─7800 /usr/syno/sbin/synoneteventd │ ├─systemd-journald.service │ │ └─7593 /usr/lib/systemd/systemd-journald │ ├─pkg-synobrm-agentd.service │ │ └─11044 /usr/local/bin/synology-backupd │ ├─systemd-udevd.service │ │ └─8434 /usr/lib/systemd/systemd-udevd │ ├─mcelog.service │ │ └─7558 /usr/sbin/mcelog --daemon --foreground │ ├─synonetd.service │ │ └─7783 /usr/syno/sbin/synonetd │ └─ip-conflict-detect.service │ └─10817 /usr/syno/sbin/syno_ip_conflict_detect --start ├─syno_dsm_internal.slice │ ├─nginx.service │ │ ├─10603 nginx: master process /usr/bin/nginx -c /etc/nginx/nginx.conf.run -g pid /run/nginx.pid; daemon on; master_process on │ │ ├─10604 nginx: worker process │ │ ├─10605 nginx: worker process │ │ ├─10606 nginx: worker process │ │ ├─10607 nginx: worker process │ │ ├─10608 nginx: worker process │ │ ├─10609 nginx: worker process │ │ ├─10610 nginx: worker process │ │ └─10611 nginx: worker process │ ├─synocgid.service │ │ └─10008 /usr/syno/sbin/synocgid -D │ ├─synoplugind.service │ │ └─7635 /usr/syno/sbin/synoplugind │ ├─dbus-system.service │ │ └─7728 /sbin/dbus-daemon --system --nopidfile │ ├─hotplugd.service │ │ └─10034 /usr/syno/sbin/hotplugd │ ├─dbus-session.service │ │ └─7690 /sbin/dbus-daemon --session --fork --print-address │ └─syslog-ng.service │ └─7985 /usr/bin/syslog-ng -Fe --worker-threads=24 -u system -g log └─syno_dsm_desktop.slice ├─synoscgi.service │ ├─ 9903 synoscgi │ ├─10899 synoscgi │ ├─10900 synoscgi │ ├─10901 synoscgi │ ├─10902 synoscgi │ ├─10903 synoscgi │ ├─10904 synoscgi │ ├─10905 synoscgi │ ├─10906 synoscgi │ ├─11570 synoscgi │ ├─11571 synoscgi │ ├─12720 synoscgi │ └─12722 synoscgi └─synoscgi-socket.service └─10186 /usr/bin/synonode /usr/syno/sbin/synoscgi_socket.js -
23 minutes ago, Peter Suh said:
In my case, I use portx, which makes it easy to use sftp.
This is free software that can be downloaded from the link below.
It is simple and good to use only ssh / sftp.
https://portx.online/ru/winscp seems to be possible, but I'm not sure.
The loader does not require a reboot.Ok then how do i connect to what Port etc... please
as if i connect to the IP there is now on 22 then i do not see anything.
-
4 minutes ago, Peter Suh said:
Can I access that path shown in the bottom using sftp?
Please download the two files dmesg and linuxrs.syno.log using sftp and attach them to a new post.
right now i am on the Loader screen. I take it can load winscp or must i reboot into the loader and then try and log in ?
-
Hi All,
My setup has crashed. I cannot log into my NAS and blelow are the specs:
DS3622xs+ / HP Microserver GEN8 / Latest IMG / Latest Friend / RAID 5 / EXT4 / LSI 9211-4i / DSM 7.2.0-64570 Update 3
I checked some things based on the commands above to see what is going on. It seems the system recovered BUT the Storage Pool and Disks seems to have issues,
systemctl status synostoraged.service
● synostoraged.service - Synology daemon for monitoring space/disk/cache status
Loaded: loaded (/usr/lib/systemd/system/synostoraged.service; static; vendor preset: disabled)
Active: inactive (dead)find . -name proc_name
ps
PID TTY TIME CMD
11791 pts/0 00:00:00 sudo
11792 pts/0 00:00:00 ash
11855 pts/0 00:00:00 ps
df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 2385528 1430224 836520 64% /
devtmpfs 2994244 0 2994244 0% /dev
tmpfs 3048436 4 3048432 1% /dev/shm
tmpfs 3048436 8016 3040420 1% /run
tmpfs 3048436 0 3048436 0% /sys/fs/cgroup
tmpfs 3048436 280 3048156 1% /tmp
I really need some help to get my system up and running or downgrade, restore, remove the HBA and add back to the onboard etc...Thanks in advanced.
-
Hi @Peter Suh
Anything else I can do or anything. I have the old USB on v7.1.1 that does not have the HBA should i add this back, add back the other SATA Drive and remove the SAS disks or how do i see if the controller has dropped the disks etc.. as you mentioned above.
Thanks
EDIT: Or how can i downgrade to Update 1 via SSH.
Will it help if i move the Disks to another setup of mine or will there be an issue ? If i can how do i do all of this etc please
-
-
1 minute ago, Peter Suh said:
I checked your last post.
I also have a 9211-4i with 4 ports supported.
The specifications of this HBA are known to be 6GB/s.
I think I flashed the LSI 9211-8i to use a 12GB/s SAS disk.
Is this method proven?I got the card as LSI 9211-8i and then had to re-flash it and flashed it back to LSI 9211-8i. I checked all the info as per all the guides and it flashed 100% if there was an issue it would not boot and the card would be bricked
Yes 12GB/s SAS Drives work on this card but at 6gb/s as i had it running on my other system for over a few weeks tons of reboots and never an issue with the same disks
-
DS3622xs+ / HP Microserver GEN8 / Latest IMG / Latest Friend / RAID 5 / EXT4
LSI 9211-4i
DSM 7.2.0-64570 Update 3
-
Just now, Peter Suh said:
Wasn't the problem of disks being mixed up in the last HBA still ongoing?
The phenomenon of only some disks being identified in RAID can be fatal.
Did you just rebuild the loader to fix this issue?All my disks was found on the HBA and they all showed in DSM no issues with this. It was just the Order in DSM So if it was Drive 9 in DSM it was Port 4 on the server that was the issue but i could live with that for now.
When i login via SSH i look for the Partions it seems the Storage Pool is no longer there and the disks are no long there as well. Looks like this all dropped out
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 2385528 1430156 836588 64% /
devtmpfs 2994244 0 2994244 0% /dev
tmpfs 3048436 4 3048432 1% /dev/shm
tmpfs 3048436 8120 3040316 1% /run
tmpfs 3048436 0 3048436 0% /sys/fs/cgroup
tmpfs 3048436 280 3048156 1% /tmpIf this is the case then the only option is to rebuild again remove the new disk leave the 3 in the RAID 5 as Degraded. remove the HBA and add the disks back to the onboard and hope and pray.
Would you agree ?
-
1 minute ago, Peter Suh said:
Usually in these cases a few minutes of waiting time is really necessary.
Have you tried re-entering port 5000 after about 5 minutes?
Are the phenomena the same?Yes i get re-directed to 5001 and the same thing. I do hear the disks. When i log in via Putty that works and i look at my volumes everything is blank. Seems like all the services are just dead.
-
Hi @Peter Suh
My system had a issues now I think there was an issue with the loader so I rebuilt it / USB issue or something, selected recover and now again my system is stating.
System getting ready please log in later.
Any help here please
EDIT: When i try and connect to 7681 i get connection closed
Since i am using an HBA now and if i want to roll back to 7.1 will this break anything if i remove the HBA and add the disks back to the onboard. I did do an Disk replacement as well and once done all was working 100%. I rebooted and this is when all the issues started.
-
Bad news right now my system has done something odd and in recovery. Do not know the cause busy with it now to see what has broken.
-
1
-
-
8 hours ago, asaf said:
Is that a sure thing?
I have read not one explanation, that in case of an HDD failure the newly added HDD will show up on the last DSM "bay".
Hence the complaint that the recovery and the rebiuld of the Volume for that matter will be a mess and hard to achieve.
I removed my 1 disk and added a new one and it showed up in the same spot that it was showing in DSM
-
1
-
-
13 minutes ago, IG-88 said:
as long as you can see the SN of the disks it will be ok and when doing recovery you should never expect to know the order of the disks, check after reboot as adding or removing disks might change things but as long as checking the Sn of the disks it should work
thats the case with the lsi hba, i never had a hp hba with it mode so i could not check if its the case with sas controllers in general or just lsi
in general dsm (that is using mdadm) can handle the change of disk positions as mdadm can keep track of that by itself
Thanks mine is an LSI 9211-4I my HP one is on the way and will test this out as well. there is an fix for this that Peter-Suh mentioned i just need to know how it should be added and will give it a try.
Checking the SN yes i am making notes of what disk is in what slot
-
1 hour ago, asaf said:
Was the process straightforward or you needed some tricks and magic to make it work?
Yes. Moved the cable to the HBA - IT Mode. Removed disks and built the loader. Once done shutdown the server, added the disks and did the migration.
Just the disk order is wrong but i can live with that for now.
-
1
-
-
On 9/9/2023 at 5:54 PM, Peter Suh said:
Both are possible.
Sent from my iPhone using TapatalkHi @Peter Suh I have tried to find a way to add this but i am not sure where to add this as i have the Disk Shuffle issue as mentioned above.
Do i need to reboot and load the loader again and make changes or can i just make changes and save and reboot will it work. If so where do i do this please.
I am a Noob with all of this via CLI etc... so please just bear with me.
-
-
Hi @asaf
I got it working
my LSI 9211-4i that is flashed as an LSI 9211-8i with and 16TB SAS Seagate 12GB/s Disk is working.
I pulled out my 6TB WD Drive and added the 16TB and the system found it and started the Auto Repiar on my RAID 5 setup. so yes this works
-
1
-
-
40 minutes ago, Peter Suh said:
S.M.A.R.T is used to measure the temperature of the disk,
but this is the first time I have heard of measuring the temperature of the SCSI controller itself.
Have you ever experienced a similar solution?I am just asking since the LSI gets a bit warm. Might need to just add small fan
-
51 minutes ago, Peter Suh said:
Rebooting is required at least once.
No change after reboot?Let me update to Update 4 and then will check to see what is going on if Update 4 is supported
-
TinyCore RedPill Loader Build Support Tool ( M-Shell )
in Software Modding
Posted · Edited by Vodka2014
Thanks alot. So i will rebuild it the same way as i did with TCRP With Friend and the same settings for the HBA. Same Model as well etc..
Keep you posted once done thanks alot