Problem finding Nas after upgrading to new firmware version

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Mon Sep 12, 2022 12:24 pm

it is now finding some errors reading some blocks (most of from 98344 to 98384 ) and it is forcing rewriting them automatically.
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Mon Sep 12, 2022 2:23 pm

2.jpg

I think it ended...??
now this is actual situation.
You do not have the required permissions to view the files attached to this post.
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Mon Sep 12, 2022 3:54 pm

Now reboot your nad and see if it works again
fvdw
Site Admin - expert
 
Posts: 13474
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Mon Sep 12, 2022 4:14 pm

i just need to unplug power and reconnect it or i need to reboot it with telnet command?
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Tue Sep 13, 2022 10:45 am

No telnet this time, normal boot
fvdw
Site Admin - expert
 
Posts: 13474
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Tue Sep 13, 2022 11:34 am

it is blinking red and blue continusly....I had to switch off nas after long time....
....it is again not seen from router and from your assistant program....
and i now disconnected also power cable because didn't want to stress hd working and nas started to be warm enough.
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Tue Sep 13, 2022 4:30 pm

So stil a problem
What did for sda2:with e2fsck using the standalone kernel do the same for /dev/sda1, /dev/sda5 and /dev/sda7

After that try again if nas boots normally
fvdw
Site Admin - expert
 
Posts: 13474
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Tue Sep 13, 2022 7:05 pm

i did it and program corrected many errors on the other sda u asked me to fix.
i used command reboot -f to reboot it
router still doesn't see nas also with your assistant program
but now it doesn't start blinking blue and red but seems hd is working but light doesn t blink is just blue permanently.

i send u also what shows after dmseg command (if can help):

[ 7.940581] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 7.940809] fuse init (API version 7.22)
[ 7.941651] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 7.942236] msgmni has been set to 234
[ 7.943807] async_tx: api initialized (async)
[ 7.944065] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 7.944082] io scheduler noop registered
[ 7.944095] io scheduler deadline registered
[ 7.944123] io scheduler cfq registered (default)
[ 7.944718] mv_xor mv_xor.0: Marvell shared XOR driver
[ 7.984604] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 8.024596] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 8.024947] mv_xor mv_xor.1: Marvell shared XOR driver
[ 8.064596] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 8.104595] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 8.112893] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 8.134452] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 10416666) is a 16550A
[ 8.760066] console [ttyS0] enabled
[ 8.777256] brd: module loaded
[ 8.787045] loop: module loaded
[ 8.790603] Uniform Multi-Platform E-IDE driver
[ 8.795988] ide-gd driver 1.18
[ 8.801194] sata_mv sata_mv.0: version 1.28
[ 8.801299] sata_mv sata_mv.0: cannot get optional clkdev
[ 8.807036] sata_mv sata_mv.0: slots 32 ports 2
[ 8.816014] scsi0 : sata_mv
[ 8.819602] scsi1 : sata_mv
[ 8.822973] ata1: SATA max UDMA/133 irq 21
[ 8.827145] ata2: SATA max UDMA/133 irq 21
[ 8.834881] m25p80 spi0.0: mx25l4005a (512 Kbytes)
[ 8.839916] Creating 2 MTD partitions on "spi_flash":
[ 8.845184] 0x000000000000-0x00000007d000 : "u-boot"
[ 8.851818] 0x00000007e000-0x00000007f000 : "u-boot-env"
[ 8.861099] tun: Universal TUN/TAP device driver, 1.6
[ 8.866270] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 8.872673] ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[ 8.881365] ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[ 8.897740] libphy: orion_mdio_bus: probed
[ 8.902055] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 8.912762] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:4b:91:de:93
[ 8.921695] PPP generic driver version 2.4.2
[ 8.926442] PPP Deflate Compression module registered
[ 8.931490] PPP MPPE Compression module registered
[ 8.936390] NET: Registered protocol family 24
[ 8.941071] usbcore: registered new interface driver rtl8187
[ 8.946819] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 8.954388] usbcore: registered new interface driver pegasus
[ 8.960320] usbcore: registered new interface driver asix
[ 8.965953] usbcore: registered new interface driver ax88179_178a
[ 8.972262] usbcore: registered new interface driver cdc_ether
[ 8.978305] usbcore: registered new interface driver net1080
[ 8.984179] usbcore: registered new interface driver cdc_subset
[ 8.990355] usbcore: registered new interface driver zaurus
[ 8.996246] usbcore: registered new interface driver ipheth
[ 9.002077] usbcore: registered new interface driver cdc_ncm
[ 9.009079] aoe: cannot create debugfs directory
[ 9.013880] aoe: AoE v85 initialised.
[ 9.018627] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[ 9.024748] i2c /dev entries driver
[ 9.029624] at24 0-0050: 512 byte 24c04 EEPROM, writable, 16 bytes/write
[ 9.039365] md: linear personality registered for level -1
[ 9.044950] md: raid0 personality registered for level 0
[ 9.050241] md: raid1 personality registered for level 1
[ 9.055640] md: raid10 personality registered for level 10
[ 9.061327] md: raid6 personality registered for level 6
[ 9.066671] md: raid5 personality registered for level 5
[ 9.071962] md: raid4 personality registered for level 4
[ 9.077557] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[ 9.086299] device-mapper: multipath: version 1.6.0 loaded
[ 9.091767] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 9.098323] device-mapper: multipath queue-length: version 0.1.0 loaded
[ 9.104940] device-mapper: multipath service-time: version 0.2.0 loaded
[ 9.111615] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 9.117731] device-mapper: raid: Loading target version 1.5.2
[ 9.123731] orion_gpio_is_valid: invalid GPIO 12
[ 9.126801] ipip: IPv4 over IPv4 tunneling driver
[ 9.132593] TCP: cubic registered
[ 9.136069] NET: Registered protocol family 10
[ 9.141717] sit: IPv6 over IPv4 tunneling driver
[ 9.147630] NET: Registered protocol family 17
[ 9.152424] NET: Registered protocol family 5
[ 9.157096] 8021q: 802.1Q VLAN Support v1.8
[ 9.161315] NET: Registered protocol family 37
[ 9.165977] Key type dns_resolver registered
[ 9.171922] netpoll: netconsole: local port 6666
[ 9.176680] netpoll: netconsole: local IPv4 address 192.168.1.252
[ 9.182743] netpoll: netconsole: interface 'eth0'
[ 9.187467] netpoll: netconsole: remote port 6666
[ 9.192154] netpoll: netconsole: remote IPv4 address 192.168.1.2
[ 9.198227] netpoll: netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[ 9.205108] netpoll: netconsole: device eth0 not up yet, forcing it
[ 9.214569] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 11.907820] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 11.917675] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 11.928243] console [netcon0] enabled
[ 11.931905] netconsole: network logging started
[ 11.937375] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 11.944705] rtc-mv rtc-mv: setting system clock to 2016-11-13 03:37:54 UTC (1479008274)
[ 14.374544] ata1: link is slow to respond, please be patient (ready=0)
[ 18.874542] ata1: SRST failed (errno=-16)
[ 24.424542] ata1: link is slow to respond, please be patient (ready=0)
[ 28.924544] ata1: SRST failed (errno=-16)
[ 34.474546] ata1: link is slow to respond, please be patient (ready=0)
[ 36.814561] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 36.834682] ata1.00: ATA-10: ST6000VN0041-2EL11C, SC61, max UDMA/133
[ 36.841043] ata1.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 36.884669] ata1.00: configured for UDMA/133
[ 36.905028] scsi 0:0:0:0: Direct-Access ATA ST6000VN0041-2EL SC61 PQ: 0 ANSI: 5
[ 36.914036] fvdw1 disk index before get_sd_name = 0
[ 36.919005] No LaCie disk map available
[ 36.922852] fvdw2 disk index after get_sd_name = 0
[ 36.927699] fvdw3 prefix[0]=s prefix[1]=d
[ 36.931803] fvdw4 diskname = sda
[ 36.935809] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.45 TiB)
[ 36.943645] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 36.949497] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 36.955710] sd 0:0:0:0: [sda] Write Protect is off
[ 36.960523] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 36.960673] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 37.268927] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
[ 37.278418] sd 0:0:0:0: [sda] Attached SCSI disk
[ 37.304655] ata2: SATA link down (SStatus 0 SControl F300)
[ 37.332704] Freeing unused kernel memory: 1932K (c0767000 - c094a000)
[ 41.461980] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 41.474011] ehci-orion: EHCI orion driver
[ 41.478338] orion-ehci orion-ehci.0: EHCI Host Controller
[ 41.483786] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 41.491594] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 41.514574] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 41.520687] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 41.527513] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 41.534759] usb usb1: Product: EHCI Host Controller
[ 41.539640] usb usb1: Manufacturer: Linux 3.14.2 ehci_hcd
[ 41.545064] usb usb1: SerialNumber: orion-ehci.0
[ 41.550697] hub 1-0:1.0: USB hub found
[ 41.554561] hub 1-0:1.0: 1 port detected
[ 41.568411] usbcore: registered new interface driver usb-storage
root@fvdw-sta-kirkwood:/ #

i also send u every check after corrections and i notice everytime could be problem just in sda1:

root@fvdw-sta-kirkwood:/ # e2fsck -fy /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
Superblock last mount time (Sat Nov 5 08:30:42 2016,
now = Mon Oct 31 23:48:08 2016) is in the future.
Fix? yes

Superblock last write time (Sun Nov 13 03:55:15 2016,
now = Mon Oct 31 23:48:08 2016) is in the future.
Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 1779, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 1779.
Fix? yes

Setting filetype for entry '.' in ??? (1779) to 2.
Missing '..' in directory inode 1779.
Fix? yes

Setting filetype for entry '..' in ??? (1779) to 2.
Pass 3: Checking directory connectivity
'..' in /usr/icons/small (1779) is <The NULL inode> (0), should be /usr/icons (1641).
Fix? yes

Pass 4: Checking reference counts
Inode 2 ref count is 22, should be 23. Fix? yes

Inode 1641 ref count is 4, should be 3. Fix? yes

Pass 5: Checking group summary information

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 5320/64000 files (6.4% non-contiguous), 40357/64000 blocks
root@fvdw-sta-kirkwood:/ # e2fsck -fy /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda2: recovering journal
Superblock last mount time (Sun Nov 13 04:05:47 2016,
now = Mon Oct 31 23:50:04 2016) is in the future.
Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 5491/32768 files (7.3% non-contiguous), 42950/131072 blocks
root@fvdw-sta-kirkwood:/ # e2fsck -fy /dev/sda5
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda5: recovering journal
Error reading block 66081 (Attempt to read block from filesystem resulted in short read). Ignore error? yes

Force rewrite? yes

Superblock last mount time (Mon Jan 1 11:00:00 2018,
now = Mon Oct 31 23:50:56 2016) is in the future.
Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 32795, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 32795.
Fix? yes

Setting filetype for entry '.' in ??? (32795) to 2.
Missing '..' in directory inode 32795.
Fix? yes

Setting filetype for entry '..' in ??? (32795) to 2.
Pass 3: Checking directory connectivity
'..' in /tmp/var/spool/cups (32795) is <The NULL inode> (0), should be /tmp/var/spool (32794).
Fix? yes

Unconnected directory inode 32796 (/tmp/var/spool/cups/???)
Connect to /lost+found? yes

Pass 4: Checking reference counts
Inode 2 ref count is 8, should be 9. Fix? yes

Inode 32794 ref count is 5, should be 4. Fix? yes

Inode 32796 ref count is 3, should be 2. Fix? yes

Pass 5: Checking group summary information

/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 88/49152 files (0.0% non-contiguous), 7453/196608 blocks
root@fvdw-sta-kirkwood:/ # e2fsck -fy /dev/sda7
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda7: recovering journal
Superblock last mount time (Sun Nov 13 04:05:46 2016,
now = Mon Oct 31 23:52:10 2016) is in the future.
Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda7: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda7: 5297/64000 files (0.2% non-contiguous), 42373/64000 blocks
root@fvdw-sta-kirkwood:/ #

everytime seems hd is working without led blinking continously reading something..... but i think is stressing hardware so i need to unplug power for long
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Wed Sep 14, 2022 12:59 pm

From dmesg output I do not see a problem.
So now lets check the boot.log on sda7
Code: Select all
]root@fvdw-sta-kirkwood:/ # mkdir /sda7 /sda1 /sda2
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log

Post the output of the cat command

Look in the boot.log if sda1 or sda2;is used for boot.
Then look into the boot.log on sda1 or sda2 in same way as you did for sda7 (replace sda7 in the commands by sda1 or sda2)


Ps when harddisk boots, does the blue led flickers for some time before coming solid?
fvdw
Site Admin - expert
 
Posts: 13474
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Wed Sep 14, 2022 5:06 pm

These are results of wht u asked me fvdw:

root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
start boot log
detect and set platform
nwsp2
kirkwood
UIMAGE-3142-NWSP2CL-14
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
nwsp2
mount dev/pts
update dev nodes
booting using sda2 file system...
else loop1 finished
rcS finished
root@fvdw-sta-kirkwood:/ #



root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
root@fvdw-sta-kirkwood:/ # cat /sda2/boot.log
start boot log
is a physical machine
detect and set platform
nwsp2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
nwsp2
kirkwood
mount dev/pts
update dev nodes
booting using sda2 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan 1 12:00:00 CET 2018
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
nwsp2
rebootd-nwsp2
nwsp2
standbyd-nwsp2
starting php based setup routines step 1

Warning: require_once(/etc/inc/global_defs.inc): failed to open stream: No such file or directory in /etc/init.d/rc.bootup1 on line 36

Fatal error: require_once(): Failed opening required '/etc/inc/global_defs.inc' (include_path='.:/usr/htdocs/php:/usr/htdocs:/usr/htdocs/inc:/usr/htdocs/status') in /etc/init.d/rc.bootup1 on line 36
start rpcbind service
starting php based setup routines step 2

Warning: require_once(/etc/inc/global_defs.inc): failed to open stream: No such file or directory in /etc/api/nasapi.inc on line 5

Fatal error: require_once(): Failed opening required '/etc/inc/global_defs.inc' (include_path='.:/usr/htdocs/php:/usr/htdocs:/usr/htdocs/inc:/usr/htdocs/status') in /etc/api/nasapi.inc on line 5
starting php based setup routines step 3

Warning: require_once(/etc/inc/global_defs.inc): failed to open stream: No such file or directory in /etc/init.d/rc.bootup3 on line 9

Fatal error: require_once(): Failed opening required '/etc/inc/global_defs.inc' (include_path='.:/usr/htdocs/php:/usr/htdocs:/usr/htdocs/inc:/usr/htdocs/status') in /etc/init.d/rc.bootup3 on line 9
starting php based setup routines step banner

Warning: require_once(/etc/inc/global_defs.inc): failed to open stream: No such file or directory in /etc/api/nasapi.inc on line 5

Fatal error: require_once(): Failed opening required '/etc/inc/global_defs.inc' (include_path='.:/usr/htdocs/php:/usr/htdocs:/usr/htdocs/inc:/usr/htdocs/status') in /etc/api/nasapi.inc on line 5
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings
else loop1 finished
rcS finished
root@fvdw-sta-kirkwood:/ #

i first tried sda7 as u asked me and aftert that trough the boot.log i noticed was sda2 to be explored as u suggested.

Infact seems to be many errors in sda2 boot.log

for your last question ..when it boots it blinks for few seconds and after is always blue (not blinks) but i listen the hd is working repetitivily in the sam,e way......so not to stress it i switch the nas off.
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

PreviousNext

Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: Google [Bot] and 11 guests