HP ProLiant Microserver N40L
1 x AMD Turion II N
16Gb Ram
2 x Seagate Barracuda 3Tb (1 of these since replaced with a WD Blue 3Tb drive)
2 x WD Blue 3Tb
RaidZ-1 (I think) it has been running since 2012 or 2013
Ok so you have heard this kind of problem before but ....
I have recently suffered a ELK event (kind of like a black swan event but caused by my Evil Little Kitty)
and yes that is her real name.
I went away for a week and during that period Elk managed to knock a door over onto my computer table
(picture attached) The NAS is under the door. This caused damage to my NAS Server and destroyed my backup Lacie drive as well, the black thing partially under the door.
The NAS was still powered on when I returned.
The actions I have taken are as follows.
removed all 4 drives, inserted a diagnostic cd to run memory and cpu tests on
the micro server chassis, this passed 2 days of testing.
Ada0 (Seagate) attached drive to secondary system ran SeaTools(DOS), found approx. 110 sector errors corrected.
Ada1 (Seagate) attached drive to secondary system ran SeaTools(DOS), drive not recognized in bios, drive powered up briefly before
making horrible grinding noise and powered down hasn't powered up since.
Ada2 ( WD ) attached drive to secondary system ran SeaTools(DOS), no errors found
Ada3 ( WD ) attached drive to secondary system ran SeaTools(DOS), no errors found
I attempted to boot the NAS but got the same diagnostic as below minus the newly added WD drive in Ada1
and that is basically it, I have tried not to do anything which reduces my chance of recovery since my NAS backup
was literally crushed by the door as well.
I still have my original boot sdc card, although the card reader was smashed the sdc card survived.
[root@ ~]# zpool import
[root@ ~]# camcontrol devlist
[root@ ~]# gpart show
[root@ ~]# glabel status
That is pretty much it I have booted (on a separate sdc card) to 9.3 but other than that
I have been too cautious to do anything else.
Should I post this elsewhere or just give up now? :D
1 x AMD Turion II N
16Gb Ram
2 x Seagate Barracuda 3Tb (1 of these since replaced with a WD Blue 3Tb drive)
2 x WD Blue 3Tb
RaidZ-1 (I think) it has been running since 2012 or 2013
Ok so you have heard this kind of problem before but ....
I have recently suffered a ELK event (kind of like a black swan event but caused by my Evil Little Kitty)
and yes that is her real name.
I went away for a week and during that period Elk managed to knock a door over onto my computer table
(picture attached) The NAS is under the door. This caused damage to my NAS Server and destroyed my backup Lacie drive as well, the black thing partially under the door.
The NAS was still powered on when I returned.
The actions I have taken are as follows.
removed all 4 drives, inserted a diagnostic cd to run memory and cpu tests on
the micro server chassis, this passed 2 days of testing.
Ada0 (Seagate) attached drive to secondary system ran SeaTools(DOS), found approx. 110 sector errors corrected.
Ada1 (Seagate) attached drive to secondary system ran SeaTools(DOS), drive not recognized in bios, drive powered up briefly before
making horrible grinding noise and powered down hasn't powered up since.
Ada2 ( WD ) attached drive to secondary system ran SeaTools(DOS), no errors found
Ada3 ( WD ) attached drive to secondary system ran SeaTools(DOS), no errors found
I attempted to boot the NAS but got the same diagnostic as below minus the newly added WD drive in Ada1
and that is basically it, I have tried not to do anything which reduces my chance of recovery since my NAS backup
was literally crushed by the door as well.
I still have my original boot sdc card, although the card reader was smashed the sdc card survived.
[root@ ~]# zpool import
Code:
pool: vol1 id: 4880409234482636973 state: UNAVAIL status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: http://illumos.org/msg/ZFS-8000-6X config: vol1 UNAVAIL missing device gptid/428ac436-c084-11e6-a318-e839352df633 ONLINE gptid/43e80dfd-c084-11e6-a318-e839352df633 ONLINE gptid/4a0f9062-c084-11e6-a318-e839352df633 ONLINE Additional devices are known to be part of this pool, though their exact configuration cannot be determined.
[root@ ~]# camcontrol devlist
Code:
<ST3000DM001-9YN166 CC4H> at scbus0 target 0 lun 0 (pass0,ada0) <WDC WD30EZRZ-00Z5HB0 80.00A80> at scbus1 target 0 lun 0 (pass1,ada1) <WDC WD30EZRZ-00Z5HB0 80.00A80> at scbus2 target 0 lun 0 (pass2,ada2) <WDC WD30EZRZ-00Z5HB0 80.00A80> at scbus3 target 0 lun 0 (pass3,ada3) <Genesys CF USB3 Reader 1206> at scbus7 target 0 lun 0 (pass4,da0) <Genesys xD USB3 Reader 1206> at scbus7 target 0 lun 1 (pass5,da1) <Genesys SD USB3 Reader 1206> at scbus7 target 0 lun 2 (pass6,da2)
[root@ ~]# gpart show
Code:
=> 34 5860533101 ada0 GPT (2.7T) 34 94 - free - (47K) 128 4194304 1 freebsd-swap (2.0G) 4194432 5856338696 2 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5K) => 34 5860533101 ada2 GPT (2.7T) 34 94 - free - (47K) 128 4194304 1 freebsd-swap (2.0G) 4194432 5856338696 2 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5K) => 34 5860533101 ada3 GPT (2.7T) 34 94 - free - (47K) 128 4194304 1 freebsd-swap (2.0G) 4194432 5856338696 2 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5K) => 34 31116221 da0 GPT (15G) 34 1024 1 bios-boot (512K) 1058 6 - free - (3.0K) 1064 31115184 2 freebsd-zfs (15G) 31116248 7 - free - (3.5K)
[root@ ~]# glabel status
Code:
Name Status Components gptid/49f13e80-c084-11e6-a318-e839352df633 N/A ada0p1 gptid/4a0f9062-c084-11e6-a318-e839352df633 N/A ada0p2 gptid/427107ff-c084-11e6-a318-e839352df633 N/A ada2p1 gptid/428ac436-c084-11e6-a318-e839352df633 N/A ada2p2 gptid/43d0e91e-c084-11e6-a318-e839352df633 N/A ada3p1 gptid/43e80dfd-c084-11e6-a318-e839352df633 N/A ada3p2 gptid/cefb5ac4-b978-11e0-a2d0-e839352df633 N/A da0p1
That is pretty much it I have booted (on a separate sdc card) to 9.3 but other than that
I have been too cautious to do anything else.
Should I post this elsewhere or just give up now? :D