Not booting anymore & fvdw-sl-16.1: telnet timeout

[Jocko]

Hi tenhouse,

About the checking on the other raids, do these command:
- check if the md1 dev node exists

Code: Select all

ls -l /dev/md1

if not you need first to create it

Code: Select all

mknod /dev/md1 b 9 1

Code: Select all

mdadm --assemble /dev/md1 /dev/sd[abcde]8

same sequence for the partitions 9 which are used to create the device md2:

Code: Select all

ls -l /dev/md2

if not you need first to create it

Code: Select all

mknod /dev/md2 b 9 2

Code: Select all

mdadm --assemble /dev/md2 /dev/sd[abcde]9

check also raid assembled with partitions 5 which are used to create the device md3:

Code: Select all

ls -l /dev/md3

if not you need first to create it

Code: Select all

mknod /dev/md3 b 9 3

Code: Select all

mdadm --assemble /dev/md3 /dev/sd[abcde]5

for partitions 7, as md0 is currently used to build a raid with partitions 2 (on Lacie firmware, partitions 2 is used under normal operating to build md4), do :

Code: Select all

ls -l /dev/md4

if not you need first to create it

Code: Select all

mknod /dev/md4 b 9 4

Code: Select all

mdadm --assemble /dev/md4 /dev/sd[abcde]7

Then post these outputs

Code: Select all

cat /proc/mdstat

and

Code: Select all

mdadm --detail /dev/md[1234]

Now, we can check the file system on these raids by trying to mount the raid devices as the file system is ext3 on them (except for md3 which is the swap partition)
so try to do

Code: Select all

mdkir /md1 /md2 /md4
mount /dev/md1 /md1
mount /dev/md2 /md2
mount /dev/md4 /md4

Then post this output

Code: Select all

mount

[tenhouse]

Usb driver and mass storage driver for usb are included in the kernel, what does dmesg tells you after inserting the usb stick?

This happens after I plug it out and back in. looks like it's detected, however I don't see it in fdisk -l.

Code: Select all

[88416.664029] usb 1-1.1: USB disconnect, device number 4
[88423.553525] usb 1-1.2: new high-speed USB device number 5 using orion-ehci
[88423.684398] usb 1-1.2: New USB device found, idVendor=0204, idProduct=6025
[88423.691264] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[88423.698586] usb 1-1.2: Product: Flash Disk     
[88423.703200] usb 1-1.2: Manufacturer: CBM     
[88423.707572] usb 1-1.2: SerialNumber: 041105903753
[88423.713195] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[88423.719721] scsi4 : usb-storage 1-1.2:1.0
[88428.734111] scsi 4:0:0:0: Direct-Access     CBM      Flash Disk       4.00 PQ: 0 ANSI: 2
[88428.742694] fvdw1 disk index before get_sd_name = 5
[88428.747639] device-name= usb-storage
[88428.751213] external disk assign prefix letter e
[88428.755866] fvdw2 disk index after get_sd_name = 10
[88428.760733] fvdw3 prefix[0]=s  prefix[1]=e
[88428.764880] fvdw4 diskname = sek
[88428.769054] sd 4:0:0:0: Attached scsi generic sg5 type 0
[88428.774472] sd 4:0:0:0: [sek] 1020671 512-byte logical blocks: (522 MB/498 MiB)
[88428.782321] sd 4:0:0:0: [sek] Write Protect is off
[88428.787173] sd 4:0:0:0: [sek] Mode Sense: 00 00 00 00
[88428.787669] sd 4:0:0:0: [sek] Asking for cache data failed
[88428.793147] sd 4:0:0:0: [sek] Assuming drive cache: write through
[88428.801541] sd 4:0:0:0: [sek] Asking for cache data failed
[88428.807086] sd 4:0:0:0: [sek] Assuming drive cache: write through
[88428.816347]  sek: sek1
[88428.821292] sd 4:0:0:0: [sek] Asking for cache data failed
[88428.826826] sd 4:0:0:0: [sek] Assuming drive cache: write through
[88428.832919] sd 4:0:0:0: [sek] Attached SCSI removable disk


@Jocko

Thanks for the detailed instructions.
Here are the results:

Note that all nodes already existed.

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md1 /dev/sd[abcde]8
mdadm: /dev/md1 has been started with 5 drives.

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md2 /dev/sd[abcde]9
mdadm: /dev/md2 has been started with 5 drives.

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md3 /dev/sd[abcde]5
mdadm: /dev/md3 has been started with 5 drives.

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md4 /dev/sd[abcde]7
mdadm: /dev/md4 has been started with 5 drives.


Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid1 sda7[0] sdc7[4] sdd7[3] sde7[2] sdb7[1]
      16000 blocks [5/5] [UUUUU]
     
md3 : active raid1 sda5[0] sde5[4] sdd5[3] sdc5[2] sdb5[1]
      255936 blocks [5/5] [UUUUU]
     
md2 : active raid1 sda9[0] sde9[4] sdd9[3] sdc9[2] sdb9[1]
      875456 blocks [5/5] [UUUUU]
     
md1 : active raid1 sda8[0] sde8[4] sdd8[3] sdc8[2] sdb8[1]
      843328 blocks [5/5] [UUUUU]
     
md0 : active raid5 sda2[0] sde2[4] sdd2[6] sdc2[7] sdb2[5]
      11712962560 blocks super 1.0 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
     
unused devices: <none>


Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm --detail /dev/md[1234]
/dev/md1:
        Version : 0.90
  Creation Time : Wed May 15 15:45:18 2013
     Raid Level : raid1
     Array Size : 843328 (823.70 MiB 863.57 MB)
  Used Dev Size : 843328 (823.70 MiB 863.57 MB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Thu May 26 19:30:23 2016
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

           UUID : e279ce69:0a1f4254:3d186b3c:53958f34
         Events : 0.694

    Number   Major   Minor   RaidDevice State
       0       8       40        0      active sync   /dev/sda8
       1       8       24        1      active sync   /dev/sdb8
       2       8        8        2      active sync   /dev/sdc8
       3       8       72        3      active sync   /dev/sdd8
       4       8       56        4      active sync   /dev/sde8
/dev/md2:
        Version : 0.90
  Creation Time : Wed May 15 15:45:32 2013
     Raid Level : raid1
     Array Size : 875456 (855.08 MiB 896.47 MB)
  Used Dev Size : 875456 (855.08 MiB 896.47 MB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Wed Jun  1 17:01:59 2016
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

           UUID : 0523259d:dfcd08d3:3d186b3c:53958f34
         Events : 0.49074

    Number   Major   Minor   RaidDevice State
       0       8       41        0      active sync   /dev/sda9
       1       8       25        1      active sync   /dev/sdb9
       2       8        9        2      active sync   /dev/sdc9
       3       8       73        3      active sync   /dev/sdd9
       4       8       57        4      active sync   /dev/sde9
/dev/md3:
        Version : 0.90
  Creation Time : Wed May 15 15:45:47 2013
     Raid Level : raid1
     Array Size : 255936 (249.98 MiB 262.08 MB)
  Used Dev Size : 255936 (249.98 MiB 262.08 MB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 3
    Persistence : Superblock is persistent

    Update Time : Thu May 26 19:30:25 2016
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

           UUID : 05e91717:bd9f5d0e:3d186b3c:53958f34
         Events : 0.18627

    Number   Major   Minor   RaidDevice State
       0       8       37        0      active sync   /dev/sda5
       1       8       21        1      active sync   /dev/sdb5
       2       8        5        2      active sync   /dev/sdc5
       3       8       69        3      active sync   /dev/sdd5
       4       8       53        4      active sync   /dev/sde5
/dev/md4:
        Version : 0.90
  Creation Time : Wed May 15 15:44:52 2013
     Raid Level : raid1
     Array Size : 16000 (15.63 MiB 16.38 MB)
  Used Dev Size : 16000 (15.63 MiB 16.38 MB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 4
    Persistence : Superblock is persistent

    Update Time : Thu May 26 19:30:22 2016
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

           UUID : 7ad50932:0faa8e7d:3d186b3c:53958f34
         Events : 0.12379

    Number   Major   Minor   RaidDevice State
       0       8       39        0      active sync   /dev/sda7
       1       8       23        1      active sync   /dev/sdb7
       2       8       55        2      active sync   /dev/sde7
       3       8       71        3      active sync   /dev/sdd7
       4       8        7        4      active sync   /dev/sdc7


Code: Select all

root@fvdw-sta-kirkwood:/ # mkdir /md1 /md2 /md4
root@fvdw-sta-kirkwood:/ # mount /dev/md1 /md1
root@fvdw-sta-kirkwood:/ # mount /dev/md2 /md2
root@fvdw-sta-kirkwood:/ # mount /dev/md4 /md4
root@fvdw-sta-kirkwood:/ # mount
rootfs on / type rootfs (rw,size=254924k,nr_inodes=63731)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/md0 on /mountpoint type xfs (ro,relatime,attr2,inode64,sunit=1024,swidth=4096,noquota)
/dev/md1 on /md1 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/md2 on /md2 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/md4 on /md4 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)


[Jocko]

Hi tenhouse,

About your usb stick, do you have at least one partition formatted ? Please to post the outputs

Code: Select all

ls -l /dev/se*
cat /proc/partitions
fdisk -l /dev/sek
gdisk -l /dev/sek

Otherwise, all your raid devices seems ok. So your NAS should boot normally or it has a hardware issue (and maybe the fan issue was related with it)

[tenhouse]

I formatted the stick with FAT.

Output:

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -l /dev/se*
ls: /dev/se*: No such file or directory
root@fvdw-sta-kirkwood:/ # cat /proc/partitions
major minor  #blocks  name

  31        0       1024 mtdblock0
  31        1      16384 mtdblock1
  31        2     244736 mtdblock2
   8        0 2930266584 sdc
   8        1       1024 sdc1
   8        2 2928240776 sdc2
   8        3        934 sdc3
   8        4       1024 sdc4
   8        5     256000 sdc5
   8        6       8033 sdc6
   8        7      16065 sdc7
   8        8     843413 sdc8
   8        9     875543 sdc9
   8       10       8033 sdc10
   8       16 2930266584 sdb
   8       17       1024 sdb1
   8       18 2928240776 sdb2
   8       19        934 sdb3
   8       20       1024 sdb4
   8       21     256000 sdb5
   8       22       8033 sdb6
   8       23      16065 sdb7
   8       24     843413 sdb8
   8       25     875543 sdb9
   8       26       8033 sdb10
   8       32 2930266584 sda
   8       33       1024 sda1
   8       34 2928240776 sda2
   8       35        934 sda3
   8       36       1024 sda4
   8       37     256000 sda5
   8       38       8033 sda6
   8       39      16065 sda7
   8       40     843413 sda8
   8       41     875543 sda9
   8       42       8033 sda10
   8       48 2930266584 sde
   8       49       1024 sde1
   8       50 2928240776 sde2
   8       51        934 sde3
   8       52       1024 sde4
   8       53     256000 sde5
   8       54       8033 sde6
   8       55      16065 sde7
   8       56     843413 sde8
   8       57     875543 sde9
   8       58       8033 sde10
   8       64 2930266584 sdd
   8       65       1024 sdd1
   8       66 2928240776 sdd2
   8       67        934 sdd3
   8       68       1024 sdd4
   8       69     256000 sdd5
   8       70       8033 sdd6
   8       71      16065 sdd7
   8       72     843413 sdd8
   8       73     875543 sdd9
   8       74       8033 sdd10
   9        0 11712962560 md0
   8       80     510335 sek
   8       81     510304 sek1
   9        1     843328 md1
   9        2     875456 md2
   9        3     255936 md3
   9        4      16000 md4
root@fvdw-sta-kirkwood:/ # fdisk -l /dev/sek
fdisk: can't open '/dev/sek': No such file or directory


Now I formatted a second stick with FAT32:

Code: Select all


[91805.336030] usb 1-1.2: USB disconnect, device number 5
[91810.694150] usb 1-1.1: new high-speed USB device number 6 using orion-ehci
[91810.825773] usb 1-1.1: New USB device found, idVendor=090c, idProduct=1000
[91810.832640] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[91810.839956] usb 1-1.1: Product: USB Flash Disk
[91810.844415] usb 1-1.1: Manufacturer: General
[91810.848681] usb 1-1.1: SerialNumber: 0343313010034234
[91810.854571] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[91810.861057] scsi5 : usb-storage 1-1.1:1.0
[91816.014001] scsi 5:0:0:0: Direct-Access     General  USB Flash Disk   1100 PQ: 0 ANSI: 4
[91816.022653] fvdw1 disk index before get_sd_name = 5
[91816.027603] device-name= usb-storage
[91816.031193] external disk assign prefix letter e
[91816.035848] fvdw2 disk index after get_sd_name = 10
[91816.040722] fvdw3 prefix[0]=s  prefix[1]=e
[91816.044868] fvdw4 diskname = sek
[91816.049030] sd 5:0:0:0: Attached scsi generic sg5 type 0
[91816.054564] sd 5:0:0:0: [sek] 7864320 512-byte logical blocks: (4.02 GB/3.75 GiB)
[91816.062609] sd 5:0:0:0: [sek] Write Protect is off
[91816.067453] sd 5:0:0:0: [sek] Mode Sense: 43 00 00 00
[91816.067921] sd 5:0:0:0: [sek] No Caching mode page found
[91816.073232] sd 5:0:0:0: [sek] Assuming drive cache: write through
[91816.082293] sd 5:0:0:0: [sek] No Caching mode page found
[91816.087660] sd 5:0:0:0: [sek] Assuming drive cache: write through
[91816.094604]  sek: sek1
[91816.099544] sd 5:0:0:0: [sek] No Caching mode page found
[91816.104904] sd 5:0:0:0: [sek] Assuming drive cache: write through
[91816.110989] sd 5:0:0:0: [sek] Attached SCSI removable disk
[91829.100661] __nand_correct_data: uncorrectable ECC error
[91829.105860] end_request: I/O error, dev mtdblock0, sector 0
[91829.111600] Buffer I/O error on device mtdblock0, logical block 0
[91829.117898] __nand_correct_data: uncorrectable ECC error
[91829.123038] end_request: I/O error, dev mtdblock0, sector 8
[91829.128774] Buffer I/O error on device mtdblock0, logical block 1
[91829.135019] end_request: I/O error, dev mtdblock0, sector 16
[91829.140657] Buffer I/O error on device mtdblock0, logical block 2
[91829.146898] __nand_correct_data: uncorrectable ECC error
[91829.152029] end_request: I/O error, dev mtdblock0, sector 24
[91829.157857] Buffer I/O error on device mtdblock0, logical block 3
[91829.164124] __nand_correct_data: uncorrectable ECC error
[91829.169299] end_request: I/O error, dev mtdblock0, sector 0


Code: Select all

root@fvdw-sta-kirkwood:/ # ls -l /dev/se*
ls: /dev/se*: No such file or directory
root@fvdw-sta-kirkwood:/ # cat /proc/partitions
major minor  #blocks  name

  31        0       1024 mtdblock0
  31        1      16384 mtdblock1
  31        2     244736 mtdblock2
   8        0 2930266584 sdc
   8        1       1024 sdc1
   8        2 2928240776 sdc2
   8        3        934 sdc3
   8        4       1024 sdc4
   8        5     256000 sdc5
   8        6       8033 sdc6
   8        7      16065 sdc7
   8        8     843413 sdc8
   8        9     875543 sdc9
   8       10       8033 sdc10
   8       16 2930266584 sdb
   8       17       1024 sdb1
   8       18 2928240776 sdb2
   8       19        934 sdb3
   8       20       1024 sdb4
   8       21     256000 sdb5
   8       22       8033 sdb6
   8       23      16065 sdb7
   8       24     843413 sdb8
   8       25     875543 sdb9
   8       26       8033 sdb10
   8       32 2930266584 sda
   8       33       1024 sda1
   8       34 2928240776 sda2
   8       35        934 sda3
   8       36       1024 sda4
   8       37     256000 sda5
   8       38       8033 sda6
   8       39      16065 sda7
   8       40     843413 sda8
   8       41     875543 sda9
   8       42       8033 sda10
   8       48 2930266584 sde
   8       49       1024 sde1
   8       50 2928240776 sde2
   8       51        934 sde3
   8       52       1024 sde4
   8       53     256000 sde5
   8       54       8033 sde6
   8       55      16065 sde7
   8       56     843413 sde8
   8       57     875543 sde9
   8       58       8033 sde10
   8       64 2930266584 sdd
   8       65       1024 sdd1
   8       66 2928240776 sdd2
   8       67        934 sdd3
   8       68       1024 sdd4
   8       69     256000 sdd5
   8       70       8033 sdd6
   8       71      16065 sdd7
   8       72     843413 sdd8
   8       73     875543 sdd9
   8       74       8033 sdd10
   9        0 11712962560 md0
   9        1     843328 md1
   9        2     875456 md2
   9        3     255936 md3
   9        4      16000 md4
   8       80    3932160 sek
   8       81    3932096 sek1
root@fvdw-sta-kirkwood:/ # fdisk -l /dev/sek
fdisk: can't open '/dev/sek': No such file or directory
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sek
GPT fdisk (gdisk) version 0.8.5

Problem opening /dev/sek for reading! Error is 2.
The specified file does not exist!
root@fvdw-sta-kirkwood:/ #


Hmm but if I can run this kernel (I didn't even power off overnight) - can it really be a hardware problem?

Also just as a site note (omitted this in the initial post, because I think it has no relevance):
I opened my NAS after ther fan e-mails (to check if the FAN is clean), while doing that I managed to break 2 "plastic screws" of the fan + I couldn't get a screw out (somewhere on the side) and the screw is now probably not so easy to get out since the thread is broken. I hope I didn't void my guarantee with this... my gurantee is finished on Jul 20. anyway...so I hope until then I can get one new, clean & working NAS...

[Jocko]

Ouups, we forgot a step when you plug an usb device : you need to update the device nodes in /dev.

So do

Code: Select all

udevstart

then you should have sek? nodes in /dev and then fdisk should now work

[tenhouse]

Ah yes, this did the trick, I could mount the /dev/sek1 now.

Ok so now I only need to get big enough disks....hmm I only have windows PCs in my home...but FAT is probably not a good choice because it can't handle big files (and I have movies on there)...I wonder if I should format it with ext3 and then somehow copy them to windows later.

[Jocko]

This should be useful : http://www.webupd8.org/2011/08/access-e ... ns-in.html

Note: maybe you can try again to reboot your NAS to see what happens.

[tenhouse]

Thanks.

Just tried to reboot - won't boot, same behavior as before, but now it even sends me Fan warning mails again....

Maybe I'm really better off sending it back when I backuped my data...maybe when the NAS comes back I can install fvdw for real :)

[fvdw]

If you have backed up your data you can install fvdw, no need to send it to lacie. Second option, take out all disks and if you have one spare disk put that in and install fvdw-sl on that disk to see if the hardware is ok.

[tenhouse]

Well my thoughts were just that I could get a "repaired" or even new device at my "last chance", since my guarantee only lasts until mid of july... but I'll see what I'll actually do...

Thanks a bunch to you guys for the moment :)