Orphée Posted January 1 Share #926 Posted January 1 No ! My bad ! I will Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 1 Share #927 Posted January 1 (edited) FYI I just switched to RR 23.12.10 from Syno Community, and SAN manager is still broken. Looking further, pkg-iscsi fails to start : Jan 01 13:44:10 xxxxxx systemd[1]: Starting iSCSI Service... Jan 01 13:44:10 xxxxxx synocheckiscsitrg[5791]: iSCSI:iscsi_repair.cpp:80:SYNOiSCSIRepair Total 0 issue(s) are detected. Jan 01 13:44:10 xxxxxx S78iscsitrg.sh[5759]: :: Running lunbackup garbage collection ... [ OK ] Jan 01 13:44:10 xxxxxx synoiscsiep[5800]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:10 xxxxxx synoiscsiep[5800]: iSCSI:iscsi_start_all.cpp:22:SYNOiSCSIStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:10 xxxxxx synoiscsiep[5800]: iSCSI:iscsi_start_all.cpp:115:SYNOiSCSIStartAll SYNOiSCSIStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5805]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5805]: iSCSI:vhost_scsi_start_all.cpp:13:SYNOiSCSIVhostStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5805]: iSCSI:vhost_scsi_start_all.cpp:39:SYNOiSCSIVhostStartAll SYNOiSCSIVhostStartAllWithoutLock(), err=Failed to start service Jan 01 13:44:11 xxxxxx synoiscsiep[5810]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5810]: iSCSI:iscsi_lun_service_start_all.cpp:145:SYNOiSCSILunServiceStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5819]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5819]: iSCSI:iscsi_loopback_start_all.cpp:29:SYNOiSCSILoopbackStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5822]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5822]: iSCSI:fc_start_all.cpp:53:SYNOFCStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx systemd[1]: pkg-iscsi.service: main process exited, code=exited, status=221/CONFIRM Jan 01 13:44:11 xxxxxx systemd[1]: Failed to start iSCSI Service. Jan 01 13:44:11 xxxxxx systemd[1]: Unit pkg-iscsi.service entered failed state. Jan 01 13:44:11 xxxxxx systemd[1]: pkg-iscsi.service failed. Jan 01 13:44:12 xxxxxx systemd[1]: Stopped iSCSI Service. Jan 01 13:45:15 xxxxxx systemd[1]: Starting iSCSI Service... Jan 01 13:45:15 xxxxxx synocheckiscsitrg[12044]: iSCSI:iscsi_repair.cpp:80:SYNOiSCSIRepair Total 0 issue(s) are detected. Jan 01 13:45:15 xxxxxx S78iscsitrg.sh[12016]: :: Running lunbackup garbage collection ... [ OK ] Jan 01 13:45:15 xxxxxx synoiscsiep[12049]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12049]: iSCSI:iscsi_start_all.cpp:22:SYNOiSCSIStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12049]: iSCSI:iscsi_start_all.cpp:115:SYNOiSCSIStartAll SYNOiSCSIStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12053]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12053]: iSCSI:vhost_scsi_start_all.cpp:13:SYNOiSCSIVhostStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12053]: iSCSI:vhost_scsi_start_all.cpp:39:SYNOiSCSIVhostStartAll SYNOiSCSIVhostStartAllWithoutLock(), err=Failed to start service Jan 01 13:45:15 xxxxxx synoiscsiep[12060]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12060]: iSCSI:iscsi_lun_service_start_all.cpp:145:SYNOiSCSILunServiceStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12065]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12065]: iSCSI:iscsi_loopback_start_all.cpp:29:SYNOiSCSILoopbackStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12070]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12070]: iSCSI:fc_start_all.cpp:53:SYNOFCStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx systemd[1]: pkg-iscsi.service: main process exited, code=exited, status=221/CONFIRM Jan 01 13:45:15 xxxxxx systemd[1]: Failed to start iSCSI Service. Jan 01 13:45:15 xxxxxx systemd[1]: Unit pkg-iscsi.service entered failed state. Jan 01 13:45:15 xxxxxx systemd[1]: pkg-iscsi.service failed. Jan 01 13:45:16 xxxxxx systemd[1]: Stopped iSCSI Service. Comparing my 2 loaders : It seems some folders are missing on DVA3221 system... # ls -Rtl .: total 0 drwxr-xr-x 2 root root 0 Jan 1 13:56 pool drwxr-xr-x 6 root root 0 Jan 1 13:56 target drwxr-xr-x 2 root root 0 Dec 22 18:26 volume drwxr-xr-x 2 root root 0 Dec 22 18:26 vsys drwxr-xr-x 2 root root 0 Dec 22 18:26 rodsys ./pool: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 cache_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_cache_cnt -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_enable -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_path -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_suspend -r--r--r-- 1 root root 4096 Jan 1 13:56 help -rw-r--r-- 1 root root 4096 Jan 1 13:56 preread_control ./target: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 dbroot -r--r--r-- 1 root root 4096 Jan 1 13:56 dump_qos_lists -rw-r--r-- 1 root root 4096 Jan 1 13:56 io_delay_msec -rw-r--r-- 1 root root 4096 Jan 1 13:56 io_delay_per_io -r--r--r-- 1 root root 4096 Jan 1 13:56 lio_event -rw-r--r-- 1 root root 4096 Jan 1 13:56 target_iops -r--r--r-- 1 root root 4096 Jan 1 13:56 version drwxr-xr-x 3 root root 0 Dec 22 18:26 vhost drwxr-xr-x 3 root root 0 Dec 22 18:26 iscsi drwxr-xr-x 3 root root 0 Dec 22 18:26 loopback drwxr-xr-x 8 root root 0 Dec 22 18:26 core ./target/vhost: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 throttle_interval_msec -r--r--r-- 1 root root 4096 Jan 1 13:56 version drwxr-xr-x 2 root root 0 Dec 22 18:26 discovery_auth ./target/vhost/discovery_auth: total 0 ./target/iscsi: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 global_np_enable -r--r--r-- 1 root root 4096 Jan 1 13:56 lio_version drwxr-xr-x 2 root root 0 Dec 22 18:26 discovery_auth ./target/iscsi/discovery_auth: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 authenticate_target -rw-r--r-- 1 root root 4096 Jan 1 13:56 enforce_discovery_auth -rw-r--r-- 1 root root 4096 Jan 1 13:56 password -rw-r--r-- 1 root root 4096 Jan 1 13:56 password_mutual -rw-r--r-- 1 root root 4096 Jan 1 13:56 userid -rw-r--r-- 1 root root 4096 Jan 1 13:56 userid_mutual ./target/loopback: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 version drwxr-xr-x 2 root root 0 Dec 22 18:26 discovery_auth ./target/loopback/discovery_auth: total 0 ./target/core: total 0 drwxr-xr-x 2 root root 0 Dec 22 18:26 epio_0 drwxr-xr-x 2 root root 0 Dec 22 18:26 epio_1 drwxr-xr-x 2 root root 0 Dec 22 18:26 multifile_0 drwxr-xr-x 2 root root 0 Dec 22 18:26 fileio_0 drwxr-xr-x 2 root root 0 Dec 22 18:26 iblock_0 drwxr-xr-x 3 root root 0 Dec 22 18:26 alua ./target/core/epio_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/epio_1: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/multifile_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/fileio_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/iblock_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/alua: total 0 drwxr-xr-x 3 root root 0 Dec 22 18:26 lu_gps ./target/core/alua/lu_gps: total 0 drwxr-xr-x 2 root root 0 Dec 22 18:26 default_lu_gp ./target/core/alua/lu_gps/default_lu_gp: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 lu_gp_id -r--r--r-- 1 root root 4096 Jan 1 13:56 members ./volume: total 0 ./vsys: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 help ./rodsys: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 help -r--r--r-- 1 root root 4096 Jan 1 13:56 local_key -rw-r--r-- 1 root root 4096 Jan 1 13:56 throttle_interval_msec Edited January 1 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 1 Author Share #928 Posted January 1 (edited) 37 minutes ago, Orphée said: FYI I just switched to RR 23.12.10 from Syno Community, and SAN manager is still broken. Looking further, pkg-iscsi fails to start : Jan 01 13:44:10 xxxxxx systemd[1]: Starting iSCSI Service... Jan 01 13:44:10 xxxxxx synocheckiscsitrg[5791]: iSCSI:iscsi_repair.cpp:80:SYNOiSCSIRepair Total 0 issue(s) are detected. Jan 01 13:44:10 xxxxxx S78iscsitrg.sh[5759]: :: Running lunbackup garbage collection ... [ OK ] Jan 01 13:44:10 xxxxxx synoiscsiep[5800]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:10 xxxxxx synoiscsiep[5800]: iSCSI:iscsi_start_all.cpp:22:SYNOiSCSIStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:10 xxxxxx synoiscsiep[5800]: iSCSI:iscsi_start_all.cpp:115:SYNOiSCSIStartAll SYNOiSCSIStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5805]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5805]: iSCSI:vhost_scsi_start_all.cpp:13:SYNOiSCSIVhostStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5805]: iSCSI:vhost_scsi_start_all.cpp:39:SYNOiSCSIVhostStartAll SYNOiSCSIVhostStartAllWithoutLock(), err=Failed to start service Jan 01 13:44:11 xxxxxx synoiscsiep[5810]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5810]: iSCSI:iscsi_lun_service_start_all.cpp:145:SYNOiSCSILunServiceStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5819]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5819]: iSCSI:iscsi_loopback_start_all.cpp:29:SYNOiSCSILoopbackStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx synoiscsiep[5822]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:44:11 xxxxxx synoiscsiep[5822]: iSCSI:fc_start_all.cpp:53:SYNOFCStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:44:11 xxxxxx systemd[1]: pkg-iscsi.service: main process exited, code=exited, status=221/CONFIRM Jan 01 13:44:11 xxxxxx systemd[1]: Failed to start iSCSI Service. Jan 01 13:44:11 xxxxxx systemd[1]: Unit pkg-iscsi.service entered failed state. Jan 01 13:44:11 xxxxxx systemd[1]: pkg-iscsi.service failed. Jan 01 13:44:12 xxxxxx systemd[1]: Stopped iSCSI Service. Jan 01 13:45:15 xxxxxx systemd[1]: Starting iSCSI Service... Jan 01 13:45:15 xxxxxx synocheckiscsitrg[12044]: iSCSI:iscsi_repair.cpp:80:SYNOiSCSIRepair Total 0 issue(s) are detected. Jan 01 13:45:15 xxxxxx S78iscsitrg.sh[12016]: :: Running lunbackup garbage collection ... [ OK ] Jan 01 13:45:15 xxxxxx synoiscsiep[12049]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12049]: iSCSI:iscsi_start_all.cpp:22:SYNOiSCSIStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12049]: iSCSI:iscsi_start_all.cpp:115:SYNOiSCSIStartAll SYNOiSCSIStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12053]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12053]: iSCSI:vhost_scsi_start_all.cpp:13:SYNOiSCSIVhostStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12053]: iSCSI:vhost_scsi_start_all.cpp:39:SYNOiSCSIVhostStartAll SYNOiSCSIVhostStartAllWithoutLock(), err=Failed to start service Jan 01 13:45:15 xxxxxx synoiscsiep[12060]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12060]: iSCSI:iscsi_lun_service_start_all.cpp:145:SYNOiSCSILunServiceStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12065]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12065]: iSCSI:iscsi_loopback_start_all.cpp:29:SYNOiSCSILoopbackStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx synoiscsiep[12070]: iSCSI:iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory Jan 01 13:45:15 xxxxxx synoiscsiep[12070]: iSCSI:fc_start_all.cpp:53:SYNOFCStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory Jan 01 13:45:15 xxxxxx systemd[1]: pkg-iscsi.service: main process exited, code=exited, status=221/CONFIRM Jan 01 13:45:15 xxxxxx systemd[1]: Failed to start iSCSI Service. Jan 01 13:45:15 xxxxxx systemd[1]: Unit pkg-iscsi.service entered failed state. Jan 01 13:45:15 xxxxxx systemd[1]: pkg-iscsi.service failed. Jan 01 13:45:16 xxxxxx systemd[1]: Stopped iSCSI Service. Comparing my 2 loaders : It seems some folders are missing on DVA3221 system... # ls -Rtl .: total 0 drwxr-xr-x 2 root root 0 Jan 1 13:56 pool drwxr-xr-x 6 root root 0 Jan 1 13:56 target drwxr-xr-x 2 root root 0 Dec 22 18:26 volume drwxr-xr-x 2 root root 0 Dec 22 18:26 vsys drwxr-xr-x 2 root root 0 Dec 22 18:26 rodsys ./pool: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 cache_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_cache_cnt -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_enable -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_path -rw-r--r-- 1 root root 4096 Jan 1 13:56 ext_jnl_suspend -r--r--r-- 1 root root 4096 Jan 1 13:56 help -rw-r--r-- 1 root root 4096 Jan 1 13:56 preread_control ./target: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 dbroot -r--r--r-- 1 root root 4096 Jan 1 13:56 dump_qos_lists -rw-r--r-- 1 root root 4096 Jan 1 13:56 io_delay_msec -rw-r--r-- 1 root root 4096 Jan 1 13:56 io_delay_per_io -r--r--r-- 1 root root 4096 Jan 1 13:56 lio_event -rw-r--r-- 1 root root 4096 Jan 1 13:56 target_iops -r--r--r-- 1 root root 4096 Jan 1 13:56 version drwxr-xr-x 3 root root 0 Dec 22 18:26 vhost drwxr-xr-x 3 root root 0 Dec 22 18:26 iscsi drwxr-xr-x 3 root root 0 Dec 22 18:26 loopback drwxr-xr-x 8 root root 0 Dec 22 18:26 core ./target/vhost: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 throttle_interval_msec -r--r--r-- 1 root root 4096 Jan 1 13:56 version drwxr-xr-x 2 root root 0 Dec 22 18:26 discovery_auth ./target/vhost/discovery_auth: total 0 ./target/iscsi: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 global_np_enable -r--r--r-- 1 root root 4096 Jan 1 13:56 lio_version drwxr-xr-x 2 root root 0 Dec 22 18:26 discovery_auth ./target/iscsi/discovery_auth: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 authenticate_target -rw-r--r-- 1 root root 4096 Jan 1 13:56 enforce_discovery_auth -rw-r--r-- 1 root root 4096 Jan 1 13:56 password -rw-r--r-- 1 root root 4096 Jan 1 13:56 password_mutual -rw-r--r-- 1 root root 4096 Jan 1 13:56 userid -rw-r--r-- 1 root root 4096 Jan 1 13:56 userid_mutual ./target/loopback: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 version drwxr-xr-x 2 root root 0 Dec 22 18:26 discovery_auth ./target/loopback/discovery_auth: total 0 ./target/core: total 0 drwxr-xr-x 2 root root 0 Dec 22 18:26 epio_0 drwxr-xr-x 2 root root 0 Dec 22 18:26 epio_1 drwxr-xr-x 2 root root 0 Dec 22 18:26 multifile_0 drwxr-xr-x 2 root root 0 Dec 22 18:26 fileio_0 drwxr-xr-x 2 root root 0 Dec 22 18:26 iblock_0 drwxr-xr-x 3 root root 0 Dec 22 18:26 alua ./target/core/epio_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/epio_1: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/multifile_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/fileio_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/iblock_0: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 hba_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 hba_mode -r--r--r-- 1 root root 4096 Jan 1 13:56 odx_info -rw-r--r-- 1 root root 4096 Jan 1 13:56 odx_mode ./target/core/alua: total 0 drwxr-xr-x 3 root root 0 Dec 22 18:26 lu_gps ./target/core/alua/lu_gps: total 0 drwxr-xr-x 2 root root 0 Dec 22 18:26 default_lu_gp ./target/core/alua/lu_gps/default_lu_gp: total 0 -rw-r--r-- 1 root root 4096 Jan 1 13:56 lu_gp_id -r--r--r-- 1 root root 4096 Jan 1 13:56 members ./volume: total 0 ./vsys: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 help ./rodsys: total 0 -r--r--r-- 1 root root 4096 Jan 1 13:56 help -r--r--r-- 1 root root 4096 Jan 1 13:56 local_key -rw-r--r-- 1 root root 4096 Jan 1 13:56 throttle_interval_msec Modification and distribution of mac-spoof addon has been completed. Now, if it is a real MAC, no processing is done. If the same phenomenon occurs with rr, is it a bug in Synology? It's been a while since they updated to Update 3, so why did the SAN MANAGER package suddenly become unstable? Shouldn’t we also see the reaction of the genuine Synology user community? Edited January 1 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 1 Share #929 Posted January 1 (edited) 27 minutes ago, Peter Suh said: Modification and distribution of mac-spoof addon has been completed. Now, if it is a real MAC, no processing is done. If the same phenomenon occurs with rr, is it a bug in Synology? It's been a while since they updated to Update 3, so why did the SAN MANAGER package suddenly become unstable? Shouldn’t we also see the reaction of the genuine Synology user community? I don't know... Did TRCP broke something RR is not able to recover ? I don't recall having this issue until I switched from RR to TCRP M-shell. Edit : is it expected to still have : Setting MAC address from [Real MAC Address set in proxmox] to [Same MAC address] on eth0 (virtio_net) ? Edited January 1 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 1 Author Share #930 Posted January 1 8 minutes ago, Orphée said: I don't know... Did TRCP broke something RR is not able to recover ? I don't recall having this issue until I switched from RR to TCRP M-shell. Nothing has been confirmed yet. Unfortunately, TCRP-mshell may have been connected when the SAN MANAGER issue occurred. Maybe the Synology community needs to find out more? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #931 Posted January 2 10 hours ago, Orphée said: Edit : is it expected to still have : Setting MAC address from [Real MAC Address set in proxmox] to [Same MAC address] on eth0 (virtio_net)? In Proxmox, the MAC addresses of eths appearing in the nic added to each VM HOST should be considered real MAC addresses. Maintaining this MAC when building the loader corresponds to using the real MAC address. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #932 Posted January 2 [NOTICE] I found out what was causing the SAN MANAGER package repair. It has been confirmed that mac-spoof addon has a direct effect. Currently, the mac-spoof addon has been removed so that it cannot be used. https://github.com/PeterSuh-Q3/redpill-load/commit/0ed22a488cc2b9d7ec198ea4e3531875056ec35c This addon will not be removed until the TCRP-MSHELL loader is rebuilt. We will re-develop the mac-spoof addon to the extent that it does not affect SAN MANAGER and redistribute the stable state. I apologize for unintentionally making repairs to SAN MANAGER difficult. There seems to be a solution to the recovery method in the link below. https://community.synology.com/enu/forum/1/post/162743 If possible, I will also test this recovery solution and share my method. 1 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #933 Posted January 2 16 hours ago, Orphée said: FYI I just switched to RR 23.12.10 from Syno Community, and SAN manager is still broken. I tried following the SAN MANAGER commands in the link above, but recovery was not possible. Recovery was successful using another method, migrating between henology models. If possible, I recommend switching between the most similar models within the same platform. I successfully migrated from DS918+ (Apollo Lake) to DS1019+ (Apollo Lake). While reinstalling DSM migration internally, the packages below are reinstalled at the junior level. Although it is a new installation, the installation process is carried out through migration processing. syno-pkg-generator: Load info, spk=[ScsiTarget-x86_64-1.0.10-0314.spk] 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #934 Posted January 2 Hi, thanks for the update. Well I'll see what I can do, I'm using DVA3221 / Denverton for its Surveillance Station AI features, so I can't just switch like that. Maybe force recovery/reinstall DSM OS could fix it ? Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #935 Posted January 2 (edited) Ok, using RR loader, and using "Force DSM reinstall" at boot menu fixed it. I reinstalled using "keep configuration blabla". And after reboot, SAN is up & running (currently on RR loader). Edited January 2 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #936 Posted January 2 Ok, using RR loader, and using "Force DSM reinstall" at boot menu fixed it. I reinstalled using "keep configuration blabla". And after reboot, SAN is up & running (currently on RR loader). Yes, in the case of mshell, press the j key within 7 seconds of booting the friend kernel to enter junior mode. This is the same function as rr's Force DSM reinstall. I think it would be more user-friendly for users if the description of Force DSM reinstall is included, such as rr, rather than junior mode. I will adjust the wording changes in the friend kernel.Sent from my iPhone using Tapatalk 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #937 Posted January 2 In my case it is easier to have Force DSM Reinstall in Grub Menu than in console windows ("Press enter to start...") because I have no monitor/screen and I access it from serial console. I guess it should work to from serial console by entering console after grub and pressing "j" key from it. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #938 Posted January 2 (edited) 22 minutes ago, Orphée said: In my case it is easier to have Force DSM Reinstall in Grub Menu than in console windows ("Press enter to start...") because I have no monitor/screen and I access it from serial console. I guess it should work to from serial console by entering console after grub and pressing "j" key from it. Because of your request, I've been browsing the Tinycore Linux forums since a few hours. https://forum.tinycorelinux.net/index.php I'm looking for the keyword "serial console", but I'm confused because there's too much information. It's difficult to find accurate information. rr's grub.cfg must be set differently from cmdline. This part is not related to coding, but is something anyone can help with. Can you help me find out which cmdline to add to grub.cfg in Tinycore? If you look at the cmdline for kernel booting of Synology DSM, you can see the following. I think something similar to this could be applied to Tinycore Linux. console=ttyS0,115200n8 earlycon=uaart8250,io,0x3f8,115200n8 Edited January 2 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #939 Posted January 2 When I mean serial console I mean serial COM port console access. With Telnet access from Windows Putty on a baremetal system, or accessible with Serial Com over TCP with ESXi, or accessible from Proxmox adding a Serial port (Serial0) socket. Here is RR grub.cfg : # cat grub.cfg insmod search insmod echo insmod terminal insmod test insmod font insmod loadenv insmod serial insmod usb_keyboard insmod linux insmod gzio insmod fat insmod ext2 set default="boot" set timeout="5" set timeout_style="menu" set vesa_mode=1 if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ]; then set default="${next_entry}" unset next_entry save_env next_entry fi if [ "${vesa_mode}" ]; then set vesa_mode=${vesa_mode} fi function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } load_video if loadfont unicode; then set gfxmode=auto insmod gfxterm terminal_output gfxterm fi set menu_color_normal=light-green/blue set menu_color_highlight=black/green if serial --unit=0 --speed=115200; then terminal_input --append serial_com0 terminal_output --append serial_com0 fi function set_gfxpayload { if [ ${vesa_mode} -eq 1 ]; then set gfxpayload=keep else set gfxpayload=text fi } set TERM=tty2 set RR_CMDLINE="" search --set=root --label "RR3" if [ -s /zImage-dsm -a -s /initrd-dsm ]; then if [ "${default}" = "direct" ]; then set timeout="1" menuentry 'Boot DSM kernel directly' --id direct { set_gfxpayload echo "cmdline:" echo "${dsm_cmdline}" echo "Loading DSM kernel..." linux /zImage-dsm ${dsm_cmdline} echo "Loading DSM initramfs..." initrd /initrd-dsm echo "Booting..." echo "Access http://find.synology.com/ to connect the DSM via web." } fi menuentry 'Boot DSM' --id boot { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } menuentry 'Force re-install DSM' --id junior { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} force_junior echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } fi menuentry 'Configure loader' --id config { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} IWANTTOCHANGETHECONFIG echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } if [ ${vesa_mode} = 1 ]; then menuentry 'Change vesa to text video mode' --id videomode { set vesa_mode=0 save_env vesa_mode configfile ${prefix}/grub.cfg } else menuentry 'Change text to vesa video mode' --id videomode { set vesa_mode=1 save_env vesa_mode reboot configfile ${prefix}/grub.cfg } fi Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #940 Posted January 2 5 minutes ago, Orphée said: When I mean serial console I mean serial COM port console access. With Telnet access from Windows Putty on a baremetal system, or accessible with Serial Com over TCP with ESXi, or accessible from Proxmox adding a Serial port (Serial0) socket. Here is RR grub.cfg : # cat grub.cfg insmod search insmod echo insmod terminal insmod test insmod font insmod loadenv insmod serial insmod usb_keyboard insmod linux insmod gzio insmod fat insmod ext2 set default="boot" set timeout="5" set timeout_style="menu" set vesa_mode=1 if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ]; then set default="${next_entry}" unset next_entry save_env next_entry fi if [ "${vesa_mode}" ]; then set vesa_mode=${vesa_mode} fi function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } load_video if loadfont unicode; then set gfxmode=auto insmod gfxterm terminal_output gfxterm fi set menu_color_normal=light-green/blue set menu_color_highlight=black/green if serial --unit=0 --speed=115200; then terminal_input --append serial_com0 terminal_output --append serial_com0 fi function set_gfxpayload { if [ ${vesa_mode} -eq 1 ]; then set gfxpayload=keep else set gfxpayload=text fi } set TERM=tty2 set RR_CMDLINE="" search --set=root --label "RR3" if [ -s /zImage-dsm -a -s /initrd-dsm ]; then if [ "${default}" = "direct" ]; then set timeout="1" menuentry 'Boot DSM kernel directly' --id direct { set_gfxpayload echo "cmdline:" echo "${dsm_cmdline}" echo "Loading DSM kernel..." linux /zImage-dsm ${dsm_cmdline} echo "Loading DSM initramfs..." initrd /initrd-dsm echo "Booting..." echo "Access http://find.synology.com/ to connect the DSM via web." } fi menuentry 'Boot DSM' --id boot { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } menuentry 'Force re-install DSM' --id junior { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} force_junior echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } fi menuentry 'Configure loader' --id config { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} IWANTTOCHANGETHECONFIG echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } if [ ${vesa_mode} = 1 ]; then menuentry 'Change vesa to text video mode' --id videomode { set vesa_mode=0 save_env vesa_mode configfile ${prefix}/grub.cfg } else menuentry 'Change text to vesa video mode' --id videomode { set vesa_mode=1 save_env vesa_mode reboot configfile ${prefix}/grub.cfg } fi I looked at grub.cfg in rr earlier, Looking back now, there is something that catches my eye. insmod serial if serial --unit=0 --speed=115200; then terminal_input --append serial_com0 terminal_output --append serial_com0 fi However, it is questionable whether the serial com port will work with this alone. Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #941 Posted January 2 Currently, when I start my VM, both RR or TCRP shows me grub boot menu. Not sure to understand your message. From my understanding/memory, serial port access is available from redpill geunine loader ? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #942 Posted January 2 13 minutes ago, Orphée said: When I mean serial console I mean serial COM port console access. With Telnet access from Windows Putty on a baremetal system, or accessible with Serial Com over TCP with ESXi, or accessible from Proxmox adding a Serial port (Serial0) socket. Here is RR grub.cfg : # cat grub.cfg insmod search insmod echo insmod terminal insmod test insmod font insmod loadenv insmod serial insmod usb_keyboard insmod linux insmod gzio insmod fat insmod ext2 set default="boot" set timeout="5" set timeout_style="menu" set vesa_mode=1 if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ]; then set default="${next_entry}" unset next_entry save_env next_entry fi if [ "${vesa_mode}" ]; then set vesa_mode=${vesa_mode} fi function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } load_video if loadfont unicode; then set gfxmode=auto insmod gfxterm terminal_output gfxterm fi set menu_color_normal=light-green/blue set menu_color_highlight=black/green if serial --unit=0 --speed=115200; then terminal_input --append serial_com0 terminal_output --append serial_com0 fi function set_gfxpayload { if [ ${vesa_mode} -eq 1 ]; then set gfxpayload=keep else set gfxpayload=text fi } set TERM=tty2 set RR_CMDLINE="" search --set=root --label "RR3" if [ -s /zImage-dsm -a -s /initrd-dsm ]; then if [ "${default}" = "direct" ]; then set timeout="1" menuentry 'Boot DSM kernel directly' --id direct { set_gfxpayload echo "cmdline:" echo "${dsm_cmdline}" echo "Loading DSM kernel..." linux /zImage-dsm ${dsm_cmdline} echo "Loading DSM initramfs..." initrd /initrd-dsm echo "Booting..." echo "Access http://find.synology.com/ to connect the DSM via web." } fi menuentry 'Boot DSM' --id boot { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } menuentry 'Force re-install DSM' --id junior { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} force_junior echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } fi menuentry 'Configure loader' --id config { set_gfxpayload echo "Loading kernel..." linux /bzImage-rr console=${TERM} net.ifnames=0 ${RR_CMDLINE} IWANTTOCHANGETHECONFIG echo "Loading initramfs..." initrd /initrd-rr echo "Booting..." } if [ ${vesa_mode} = 1 ]; then menuentry 'Change vesa to text video mode' --id videomode { set vesa_mode=0 save_env vesa_mode configfile ${prefix}/grub.cfg } else menuentry 'Change text to vesa video mode' --id videomode { set vesa_mode=1 save_env vesa_mode reboot configfile ${prefix}/grub.cfg } fi TCRP already had the same settings. I just didn't have insmod serial. I added it to the top line and tested, but no change. "Booting Tinycore for loader creation" is the final console message. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #943 Posted January 2 3 minutes ago, Orphée said: Currently, when I start my VM, both RR or TCRP shows me grub boot menu. Not sure to understand your message. From my understanding/memory, serial port access is available from redpill geunine loader ? TCRP uses a total of three Linux kernels. I think this is something I've explained over and over again. 1. Tinycore Linux 2. Friend Linux 3. Syno DSM Linux Here, number 3 is the only one that can communicate with the Serial Port. This is what you know. Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #944 Posted January 2 (edited) I agree that on (virtual) monitor, nothing is shown after boot message. But on serial com port, you then have all boot logs from Xpenology, and access to DSM command line. Edited January 2 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #945 Posted January 2 2 minutes ago, Orphée said: I agree that on (virtual) monitor, nothing is shown after boot message. But on serial com port, you then have all boot logs from Xpenology, and access to DSM command line. There is no problem in outputting logs whether it is a virtual serial port or a bare metal real serial port. Actually I use Serial output in all my VM (vmware fusion, esxi, virtual box, prodmox) tests. What you want is the early stage of the first loader build stage. The stage where you need to view the log after the loader has already been built is the late stage. Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #946 Posted January 2 Here is what I have on another test VM : Behind, the (virtual) screen monitor. In Front the serial console. From there, yes, I can directly start in "force_junior" mode from Grub menu. I dont need to wait for "Please press enter for activate this console" So yes when you don't have a monitor plugged, access from grub is easier. But again, it is not a dealbreaker. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #947 Posted January 2 (edited) 5 minutes ago, Orphée said: Here is what I have on another test VM : Behind, the (virtual) screen monitor. In Front the serial console. From there, yes, I can directly start in "force_junior" mode from Grub menu. I dont need to wait for "Please press enter for activate this console" So yes when you don't have a monitor plugged, access from grub is easier. But again, it is not a dealbreaker. I also actually tried booting rr from a USB stick on COM1 SERIAL port on bare metal. Don't you want the third menu "Configure Loader" to also run on the Serial Port console? I don’t think rr can do this part either? Edited January 2 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #948 Posted January 2 (edited) 12 minutes ago, Orphée said: Here is what I have on another test VM : Behind, the (virtual) screen monitor. In Front the serial console. From there, yes, I can directly start in "force_junior" mode from Grub menu. I dont need to wait for "Please press enter for activate this console" So yes when you don't have a monitor plugged, access from grub is easier. But again, it is not a dealbreaker. I think it would be not bad idea to add force_junior to the grub menu like rr. This is possible within Friend, and we will also add the Force DSM re-install function to grub. Edited January 2 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #949 Posted January 2 With RR, to configure the loader I do it from http access 7681 usually as it starts menu.sh at load. I use ssh as a backup option. I agree that "configure loader" may not work from serial access. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #950 Posted January 2 4 minutes ago, Orphée said: With RR, to configure the loader I do it from http access 7681 usually as it starts menu.sh at load. I use ssh as a backup option. I agree that "configure loader" may not work from serial access. If so, I will no longer try to access the Tcrp loader build menu from the serial port console. Instead, I will finish implementing the DSM Force re-install function. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.